Concurrent first-top-up rewards on a private game server: account eligibility and separate ledgers
Two near-simultaneous first purchases can both be real payments. Deliver each verified base purchase, but grant an account-level first-top-up reward once. Payment idempotency and promotion eligibility require different constraints.
Continue by topic
Confirm game eligibility and commercial terms
This concerns normal promotions on an owned or authorized private game server, not unconditional acceptance of any game business. Public payment methods are WeChat Pay, Alipay and UnionPay, subject to approved configuration. Onboarding establishes the actual business, site and delivery flow. Ask the team about channel limits, fee basis, refund costs and exceptional review; no universal pricing or handling deadline is offered.
Merchant USDT settlement after CNY collection currently uses only TRON/TRC20, with conditions and timing confirmed separately. Owned-wallet monitoring is a different direct-to-wallet service supporting TRC20/ERC20. Customer payment does not prove base credits, a promotional reward or merchant settlement completed. The merchant implements promotion eligibility, reward delivery and the game ledger; they are not claimed as built-in collection-platform features.
Define the eligibility scope before launch
Publish whether first-top-up eligibility belongs to an account, server or character; identify qualifying verified payments, the event-time rule and refund policy. For account-level eligibility, retain immutable account identity plus character/server snapshots at purchase, and key eligibility by account and campaign version. A mutable nickname is not an identity key. Specify whether participation in an old campaign affects a new one before callbacks arrive.
Keep payment orders, base-credit postings and promotional claims separately. An illustrative internal reward_claim (account_id, campaign_version, source_order, decision_ref) requires non-null account/campaign fields and uniqueness for that pair. Reward jobs need a unique key too. These are not 稳付pay API fields. Freeze the recipient character in the claim; a later retry must not target whichever character happens to be logged in.
Credit two purchases and claim one reward
Authenticate notifications under the formal signature contract and verify order, amount, currency and merchant ownership. Post base credits once per order. Atomically claim promotion eligibility under its own rule. A successful base posting with an already-used reward claim is normal; do not discard the second genuine purchase. One transaction can persist the base posting and claim decision, with a durable reward job deduplicated again at execution.
Simulate account U paying orders A and B concurrently. Base purchases of 100 and 200 must both post, while the promotion produces one claim and one delivery job. If the winner must be the earliest trusted payment time, lock acquisition order is insufficient: collect candidates and decide after an agreed cutoff and late-arrival window. If the rule is real-time first accepted, disclose that explicitly. These illustrative quantities are not a package price or reward promise.
Exceptions, refunds and acceptance checks
A reward-service timeout retries the same job after checking delivery evidence; it does not release eligibility for another order. Unknown payment evidence stays pending. Missing or suspended recipient characters require authorized review, not automatic reassignment. Whether a refund restores eligibility depends on the published policy and reward consumption. Use referenced compensation records; do not erase payment, base-credit or claim history.
In isolation test concurrent purchases, duplicate notifications, reward-job crash/retry, different character logins, late payments and refunds. Confirm both base purchases total correctly, one account/campaign claim exists and the recipient matches the snapshot. Then reconcile CNY payments and merchant TRC20 settlement by order; free reward units are not collected money. Use simulated evidence, with no real payment or customer transaction queries. Formal onboarding and callback documentation provide the actual payment contract.
Frequently asked questions
May one genuine payment be discarded to enforce the reward limit?
No. Verify and credit both base purchases. The limit applies to promotional claims, not legitimate payment records.
Can a refund delete the promotional claim?
Do not delete it. Apply the published policy, examine consumed rewards and record compensation with references; restoring eligibility needs an explicit decision.