Authorized private game servers: reconciling top-ups at season close
A season reset is an operating event, not permission to erase paid top-ups or outstanding promises. For merchant-owned or authorized private game servers, this guide designs cutoff records and handover of unresolved obligations. It does not cover server setup or unauthorized operation. Confirm business and channel acceptance with 稳付pay first; no game-publisher partnership is implied.
Contents
1. Disclose what survives a season change
Distinguish seasonal items, continuing memberships and unspent top-up credits, explaining reset effects and undelivered orders individually. “All data resets” does not replace purchase commitments, and paid entitlements must not be reduced by a new rule. If carryover terms are unclear, pause ambiguous products and have authorized staff review historical promises and support arrangements without asserting legal conclusions.
2. Set separate order and delivery cutoffs
Record announcement timezone, new-order cutoff, old-season delivery cutoff and expected reopening window. Stopping orders does not erase payments still processing; continue receiving and validating original payment results. Maintenance notices explain original-order support and the next status update rather than directing duplicate purchases elsewhere. Keep notice versions and approval when windows change.
3. Build an unresolved-obligation register
At cutoff, list payments awaiting confirmation, paid undelivered orders, unknown delivery outcomes and refunds awaiting verification. Preserve promise, latest evidence time, owner and next action for each. Unknown does not mean unpaid. An independent authorized reviewer checks and seals a verifiable version. This is a merchant operations register, not a platform reset or batch-compensation feature.
4. Route late confirmations to the old-season register
When an old order confirms during maintenance, append it to the same register with arrival time. Do not award current-season products solely because the current season changed. Check previous delivery, then apply original terms for fulfillment, an explicitly agreed conversion or refund. Conversion needs actual product rules and customer confirmation, not a support-invented credit ratio. Preserve payment facts and final decisions.
5. Explain every new-season opening entitlement
List new-season grants, retained entitlements under applicable terms and outstanding-order fulfillment separately. For illustration, 100 opening gift points, 40 retained points and 60 from an old obligation need three sources and conditions. These are examples, not prices. A displayed total of 200 must remain explainable, and restarting an import must not duplicate a source.
6. Verify handover before reopening sales
Before reopening, an owner marks each obligation delivered, refund verified or still pending with an assigned owner and customer update. A working new-season login does not close top-up issues. Retain old-season reconciliation records read-only with access and retention controls. If imports disagree, pause new adjustments to affected entitlements and investigate instead of issuing credits to force a matching total.
7. Close cash and player obligations separately
Separate verified collections, refunds, merchant settlement and player delivery in season-close reports. Receiving USDT is not proof of player fulfillment. Payment, channel confirmation and delivery may occur on different days; preserve their actual times. Closing obligations must match the next season’s handover register. Every closure needs evidence and approval; a season change never justifies zeroing unresolved amounts.
Related verification guide: Support records and redaction
8. Season-change acceptance checks and FAQ
Use owned test records for orders created before cutoff but paid after it, repeated imports, unknown old delivery and old callbacks after reopening. Each must retain its original promise, explain opening sources and have an owner. Stop affected processing when terms, evidence or authority are missing. Contact https://t.me/tonyyyds for collection issues; never request game passwords or payment verification codes.
Can old top-up orders be deleted after reset?
A reset cannot erase records needed for delivery, refunds or reconciliation. Retain required evidence under applicable retention rules and hand over unresolved items.
Can old-season payments automatically become new credits?
Only where original rules allow it and required confirmation is complete. Preserve basis and source; never invent a ratio or duplicate delivery.
Does settlement complete the season reconciliation?
No. Settlement explains merchant funds; delivery, refunds and opening handover each require verification.
References
The references support general database and time-recording principles only. These are merchant-side designs, not 稳付pay dashboard features or API parameters. Current fiat collection channels are WeChat personal-code collection, WeChat native collection and Alipay native collection. T0 real-time USDT settlement follows the merchant’s agreed configuration and terms; it is not a success-rate guarantee. TRC20/ERC20 monitoring concerns payments directly to the merchant’s own wallet, without platform custody; callbacks follow configured confirmation conditions. The automated payout API is not open.
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 ↗