Game-server cumulative top-up rewards after a refund: eligibility, claims and adjustments

An owned or authorized game server may award a reward after cumulative top-ups reach a threshold. A later refund can lower the qualifying total. Deleting the original payment and rerunning rewards is unsafe: rewards, ordinary credits and refunds need separate evidence. This guide concerns milestone rewards, without implying a partnership with a commercial game or unconditional payment-channel acceptance.

Continue by topic

Define contributions before the campaign starts

Save campaign ID, rule version, time zone, boundaries, unit and participating account/server scope. Explain whether the total uses verified payments, fulfilled amounts or net payments after completed refunds, and whether bonus credits count. Publish the rules before participation rather than changing the threshold afterward.

Link each contribution to its payment and campaign so repeated callbacks do not increase the total. Define late confirmations, partial refunds, cross-server identities and deleted characters. Example amounts describe a merchant campaign, not 稳付pay prices or offers.

Separate qualification from claiming a reward

Eligibility says that a participant meets a tier under a rule version. A claim records whether that reward is reserved, delivered, under review or adjusted with approval. Use a unique scope covering campaign, participant, tier and reward type. Notification count must not become reward count.

Coordinate contributions and eligibility recalculation at one concurrency boundary. An external game delivery needs a stable action reference and outcome checks. If it times out, inspect the original action before another grant. Preserve the original character identity after deletion rather than granting to a new character with a reused numeric ID.

Example: 120 falls to 90, without blindly removing items

Suppose a 100 CNY milestone is reached by verified payments of 70 and 50 CNY. Its reward is granted once. A completed 30 CNY partial refund on the second order lowers net contributions to 90. A refund request first enters review; only a verified completed result determines the final adjustment.

Where a previously disclosed rule allows reversal, check whether the reward can actually be revoked and its current possession. If used, traded or of unknown revocation status, do not silently debit ordinary credits or manufacture a negative balance. Preserve the original reward and discrepancy for an approved decision. Virtual entitlements are not universally reversible.

Regaining eligibility does not erase a previous claim

A later 20 CNY top-up raises the total to 110. The participant qualifies again, but the same tier should not automatically pay twice. Check whether repeat claims are explicitly allowed and whether the original reward remains valid, was verifiably revoked or is unresolved. Adjustments must refer to the original tier and reason.

Test duplicate callbacks, simultaneous threshold crossings, claims racing with refunds, unknown refunds, regaining the same tier and reconciliation after campaign close. Trace each payment contribution through eligibility to the actual reward, so support can explain the history rather than only a current total.

Frequently asked questions

Should a refund request immediately remove the reward?

A request is not a completed refund. Any restriction on an unclaimed reward needs an agreed rule, recorded reason, scope and review; it does not justify an unsupported reversal of delivered entitlements.

Can the account claim the same milestone after qualifying again?

Only according to published rules and the original reward state. Regaining eligibility does not erase a claim. Keep one durable claim identity and explicit adjustment handling.

References