Game top-ups after a server merge or region change: identity snapshots and recovery
After a merge, move or rename, a payment order does not automatically know the new game identity. This guide links payment and delivery through order snapshots, operator mappings and top-up records, showing which orders can migrate automatically and which need review.
Contents
1. Define the service and status terms
A merge or region move can change a character's display name, server or internal ID. If an order stores only a nickname, later delivery may target the wrong character. Keep payment orders separate from game entitlements and reconcile using stable identifiers and an operator-approved migration map.
2. Bind each order to the purchased entitlement
Before a merge, snapshot each merchant order ID, amount and currency, product or point bundle, original server, unique character ID, account binding and order time. Preserve the product and promotion rules in effect then; do not reinterpret old orders using the post-merge page. Treat a nickname as display-only.
3. Process status only after server-side confirmation
Payment confirmation and in-game delivery are separate states. After verifying payment, use the operator-approved mapping to resolve the new identity and record old ID, new ID, mapping evidence and fulfillment entry. Automate only when the match is unique and conflict-free. Ambiguous or missing mappings require review, never guesswork.
4. Route exceptions and retain reconciliation evidence
For paid-but-not-delivered cases, check final payment state, original server and character snapshot, mapping version, point ledger, refund status and recovery job. Keep unknown outcomes pending; do not charge again. Use the same order ID to block duplicate grants if another callback arrives after recovery.
5. Pre-launch acceptance checklist
Test a single server, merged servers, multi-server moves, renamed characters, duplicate names, incomplete mappings, refunded orders, late callbacks and failed recovery. Reconcile payment, identity mapping, in-game points and case closure. Export a read-only pre-merge list and have operations review totals without requesting user passwords or keys.
6. Frequently asked questions
After a merge, can a top-up be moved using only the character name?
No. Names can change or repeat. Check the original server, unique character ID in the merchant order and the operator-approved migration mapping. Review ambiguous matches manually.
What if payment is confirmed but the game server is temporarily unavailable?
Keep the verified payment state and mark delivery pending. Follow the operator's maintenance and recovery process; do not charge again or revert payment to failed. After recovery, check fulfillment once using the same order ID.
Should a refunded order from before the merge still be fulfilled?
Do not rely on an old paid status alone. Check the final refund state, credit ledger and migration list. Close refunded orders under the merchant's policy instead of granting again, and retain linked refund and migration evidence.
Business scope
This guide applies only to game services owned or authorized by the merchant. It covers order and top-up reconciliation; 稳付pay staff must confirm business acceptance, channel terms and handling arrangements.
Confirm integration for your use case
Describe your products, order volume, payment methods and settlement needs to confirm interfaces, fund flows and exception handling.
Contact 稳付pay ↗