Private game server top-up packages: credits, bonuses and order snapshots
A private game server top-up needs more than a payment button. Reading only today’s package price, bonus or eligible realm can grant the wrong amount when payment arrives after a promotion. For owned or authorized servers, this guide explains how to preserve the offer at order creation and keep payment, delivery and settlement records separate. Confirm business acceptance and channel conditions with 稳付pay before integration.
Contents
1. Define what the top-up buys
Separate credits, membership time and one-off items into distinct products. Specify currency, price, base quantity, eligible realms, validity and after-sales rules for each. A successful payment does not prove every entitlement was delivered. Show the conditions before purchase so one package name does not imply different offers across realms. Merchants set prices and ratios; no fixed conversion rate is prescribed here.
2. Snapshot price and bonus rules
Calculate the payable amount on the merchant backend from trusted product configuration, not browser-supplied prices or bonuses. Preserve the product version, base and bonus credits, promotion reference, conditions, character and realm. An illustrative offer of CNY50 for 500 base plus 100 bonus credits needs separate recorded values, not just “premium package”. These numbers are examples, not 稳付pay pricing or a real promotion.
3. Record first-purchase and purchase-limit eligibility
Do not enforce first-purchase bonuses, account limits or promotion stock merely by hiding a button. Decide whether an order or confirmed payment reserves eligibility, then handle unpaid release, late payment and concurrent purchases. Link eligibility to the order and enforce appropriate database uniqueness. A conflict needs an explicit outcome; do not accept the advertised price while silently removing an unavailable bonus.
4. Bind payment to the original product and character
Before creating the order, validate the account’s right to top up the chosen character and ask the player to confirm realm, character and package. Verify callbacks under the actual integration specification, matching merchant order, amount, currency and status, then read its snapshot. The return page displays results, not credit grants. Never substitute the latest browser selection or newly edited package for an existing order.
5. Separate base credits, bonuses and delivery results
A local transaction can record verified payment, enqueue delivery and create a unique business grant reference. The game server is a separate system: retry or query with that same reference rather than claiming a local transaction covers remote delivery. Record base and bonus sources separately. Repeated callbacks reuse the processed result; a second actual purchase has its own order. Manual recovery must reference the original order and approval record.
6. Handle expired promotions, price changes and late payments
Define order expiry, promotion eligibility cutoffs and late-payment handling before purchase. Valid older orders use their preserved, applicable terms rather than today’s price. If a closed order later has confirmed payment, reconcile the channel result and original offer, then follow agreed review, delivery or refund procedures. A local expired label does not prove no money was received. Do not immediately ask the player to pay again.
7. Reconcile player credits and merchant USDT settlement separately
After WeChat or Alipay channel collection, merchant T0 real-time USDT settlement follows the agreed network, address, rate, fees and triggers. Player credit delivery and merchant transfer are separate states. With direct USDT payments to a merchant-owned wallet, supported monitoring covers TRC20 and ERC20; funds do not pass through the platform and callbacks follow configured on-chain confirmation conditions. Keep these fund flows distinct.
8. Frequently asked questions
Does payment after a promotion still earn a bonus?
Use the displayed, preserved eligibility and expiry rules. Manually review unclear late payments instead of silently switching packages.
Why not store only the total credits?
Separate base and bonus sources support eligibility checks, refund adjustments and disputes. A total alone cannot reconstruct the offer.
Does this article guarantee channel acceptance?
Explain the business, authorization and integration needs to primary contact @tonyyyds, then confirm channel conditions. No ready-made game plugin or unconditional acceptance is promised.
References
The official references support the general discussion of database uniqueness and transactions. Product, promotion and ledger examples are merchant-side design recommendations, not 稳付pay API fields or released dashboard features.
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 ↗