Missing daily game-pass rewards: purchase eligibility, reward calendars and safe catch-up

For owned or authorized games, one pass payment may purchase daily benefits over a period. Payment success does not prove that every reward was delivered; one missed day should not trigger a replay that creates another pass. Separate purchase eligibility from daily execution records and identify the specific missing date. WenFuPay integration eligibility and actual product conditions require confirmation with the team.

Continue by topic

Freeze eligibility and date rules at purchase

The order retains stable account, character and server, pass version, start and end, business timezone and daily eligibility. Disclose login-day versus calendar-day rules, manual claim versus automatic grant, and catch-up windows before purchase.

A monthly pass does not automatically mean 30 days or a calendar month; the server’s location must not silently choose the boundary. Payment confirmation and actual activation may differ. Follow the original terms rather than counting system waiting time as consumed benefits.

Give each reward day its own state and evidence

The merchant may track eligibility, target character and business date per grant, separating future, claimable, processing, confirmed and unknown states. A missing row does not itself prove eligibility; check the conditions and original rules.

Example CARD-A covers three illustrative reward days: day one is delivered, day two unknown and day three not due. Handle them separately rather than failing or rerunning the entire pass. Catch-up references the original business date, not the date a job restarts.

Query original external grants after a timeout

A timeout can occur after the game server adds an item but before the response returns. Check the original execution reference, actual character changes and grant evidence. Do not issue another reward or ask the user to recharge while the outcome is unknown.

A local unique constraint can govern records for one entitlement, character and date, but cannot prove the external server did not execute. Catch up only confirmed missing, eligible portions under an authorized procedure; retain original day, reason, operator and final outcome. Unknown results remain for investigation.

Accept payment and benefit jobs separately

Integrate payment confirmation and callbacks with WenFuPay’s formal documentation to create one purchased-pass eligibility. The merchant’s game system handles daily benefits, character permissions and catch-up. Repeated payment notices must not create another whole pass or resend all historical rewards.

Use simulated records for day boundaries, server transfers, interrupted jobs, repeated same-day claims, lost grant responses and pass after-sales changes. Closure should explain payment, eligibility period, daily grants and unresolved items. Merchant USDT settlement is recorded separately and is not delivery evidence.

Frequently asked questions

Can catch-up replay the original payment callback?

Do not recreate a pass by replaying payment. Find original eligibility and missing dates, then handle only eligible, confirmed incomplete grants with evidence.

Does one database grant row guarantee no duplicate delivery?

It constrains local records only. The game server may have executed before a lost response; check the original operation or character changes before repeating an unknown grant.

References