Game top-ups and entitlement delivery

Private game server top-ups paid but not credited: character, realm and recovery checks

When a private game server top-up is paid but credits are missing, do not ask the player to pay again first. For owned or authorized game servers, follow the original order, character and realm snapshot, payment evidence and grant record to recover without crediting the wrong character or granting twice. These are merchant-side recommendations. Confirm acceptance and channel conditions with 稳付pay; no game-brand partnership is implied.

Contents

1. Separate payment success from credit delivery

Support should locate the original merchant order, verify payment, identify its destination realm and character, then check the game-server ledger. A return page, screenshot or client balance is a clue, not sufficient authorization to grant credits. A zero balance on another character does not prove that the original character received nothing.

Record local payment states separately from delivery states: pending, confirmed or exception versus not dispatched, in progress, credited or outcome unknown. Maintenance must not reverse confirmed payment to unpaid; recovery must not turn unconfirmed payment into success. These state names are design examples, not 稳付pay API enums.

2. Freeze character, realm and product version at checkout

Store internal account and stable character identifiers, realm, product version, currency and amount due, base credits, bonus rule and creation time. A nickname helps confirmation but is not a unique delivery address. Character numbers may overlap across realms, and renaming must not change historical ownership. Ask the player to confirm the realm and character before payment and validate ownership on the backend.

Keep the old-to-new realm mapping and effective time during mergers, preserving original snapshots. For transferred characters, verify ownership through a controlled mapping and create a linked fulfillment correction after review instead of rewriting the order. Payments arriving after a promotion ends still use the original agreed bonus version, not the current promotion configuration.

3. Verify payment, then create one grant task

Validate notifications using the confirmed channel protocol; check merchant ownership, original order, currency, amount and success conditions. If unclear, authorized staff should use the agreed inquiry process rather than accept screenshots. Persist payment evidence and one grant task after confirmation. Acknowledgment and retries follow integration documentation; CNY collection rules are not USDT notification specifications.

A local uniqueness key can combine the original order and entitlement type; define whether base and bonus credits are granted together or recorded separately. Reuse a stable fulfillment identifier across services, including after timeouts. A database unique constraint prevents duplicate tasks. A local transaction can commit related records together but does not automatically include the remote game server.

Further reading: Payment callbacks

4. Resolve game-server timeouts before resending

A grant timeout may mean the request never reached the game server, or that credits were committed but the response was lost. Treating both as failure and granting again duplicates the latter. Look up the remote ledger by the original fulfillment identifier. If committed, save evidence and close the task; if non-execution is established, resend with the same identifier.

If the game supports neither idempotent receipt nor history lookup by fulfillment identifier, pause automatic resends and request manual review. Compare original top-up and spending entries, not just the current balance, since credits may already be spent. Record the review owner and next check time, display actual progress and avoid a fixed delivery-time promise.

5. Example: duplicate notifications during a realm merger

Suppose a demonstration order buys 1,000 base credits plus 100 bonus credits and snapshots the old realm and character. Figures are illustrative, not platform prices or exchange rates. A merger follows payment; the first notification creates a task, the game executes it but loses the response, then a second notification arrives. Check one payment, one task and one character mapping, then find the 1,100-credit entry for that fulfillment identifier.

If the entry exists, repair local delivery evidence rather than grant another 1,100. If only 1,000 base credits arrived, use the original bonus rule and split tasks to establish whether the bonus is missing; do not resend the entire order to fill it. Stop automation if the character mapping is ambiguous and verify ownership before correction. Retain order and fulfillment identifiers, operator, evidence and time for each step.

6. Preserve evidence for manual recovery and refunds

A recovery button should resume the original task through a controlled workflow: verify payment, establish non-delivery and reuse the fulfillment identifier. A target-character change requires review and access control, retaining the old target and reason. Support must not move someone else’s order based on a nickname. A player leaving the game does not justify deleting payment or grant history; apply the agreed after-sales rules.

Record and link refund requests, refund outcomes and credit adjustments separately. Product rules and actual conditions determine whether spent credits, bonuses and promotion benefits can be reversed; do not assume the payment platform can automatically remove game balances. After a game-server restore, reconcile top-ups and spending since the recovery point before reopening recovery, to avoid replaying existing deliveries.

7. Reconcile player credits and merchant settlement separately

In an isolated environment you own, simulate normal delivery, duplicate notifications, mergers, transfers, lost responses after execution, missing bonus credits and backup recovery. Prove that each order produces only the intended credit change, reaches the same character and leaves auditable manual actions. Simulation is not real channel payment; arrange live acceptance separately under agreed authorization and do not drill on production player accounts.

Player-credit delivery and merchant USDT receipt are separate reconciliation chains. T0 real-time USDT settlement after WeChat or Alipay collection follows the integration agreement. In direct USDT collection, customers pay the merchant-owned address; 稳付pay only monitors, confirms and sends callbacks without custody. A wallet transfer does not prove a particular character received credits, and a game delivery fault does not establish settlement failure.

Further reading: Real-time settlement

8. Frequently asked questions

Can support grant credits from a success screenshot?

Not from the screenshot alone. Verify the original order payment, then inspect its realm, character and grant ledger. Collect only necessary order, realm and character identifiers and redacted evidence, never passwords, verification codes, private keys or recovery phrases.

Can recovery use an old character number after a merger?

Check the controlled old-to-new mapping, ownership and effective time first. Matching numbers do not establish identity. Pause automatic recovery if the mapping is missing or ambiguous, and have authorized staff retain correction records.

Does 稳付pay integration guarantee every private game server is accepted?

No. This covers order and delivery design for owned or authorized games, not guaranteed channel acceptance or brand cooperation. Confirm the use case, authorization, channel and settlement conditions with primary contact @tonyyyds before integration. Do not infer that a ready-made game plugin exists.

References

The official references below support unique-constraint and local-transaction boundaries. Character snapshots, investigation order and recovery examples are merchant-side proposals, not 稳付pay internals or a game-server protocol.

Confirm integration for your business scenario

Describe your products, order volume, payment methods and settlement needs to confirm the APIs, movement of funds and exception handling item by item.

Contact 稳付pay ↗