Delivering game gift top-ups: acceptance, rejection and refund evidence
Ordinary game top-ups often serve the paying account; gifts involve both a payer and a recipient. Where gifting is actually supported, merchants must decide who accepts, what rejection means and who receives support updates. This guide concerns merchant-owned or authorized services. It implies neither a game-brand partnership nor universal 稳付pay acceptance of games or gift products.
Contents
1. Confirm the product supports gifting
State which products can be gifted, recipient eligibility and use restrictions. Do not relabel personal memberships, nontransferable credits or unauthorized third-party top-ups as gifts. The payer does not need the recipient’s password; recipients confirm through their own accounts. Store only stable identifiers needed for delivery, show gift scope before purchase and confirm actual onboarding conditions.
2. Show the gift without exposing payment details
After the payer confirms the recipient, show the product, quantity, scope and acceptance deadline to that recipient. Do not expose the payer’s full channel account, screenshots or contact details. Any relationship or eligibility checks use the merchant’s disclosed minimum evidence, never payment passwords, verification codes or wallet recovery phrases. A recipient change needs renewed confirmation rather than an edit to the original order.
3. Track payment, acceptance and delivery separately
An order may be paid while awaiting acceptance, or accepted while delivery is pending. Record all three facts and times separately; “payment confirmed” must not mean “gift delivered.” If acceptance is required, a callback only advances payment confirmation and cannot bypass it. These state names are merchant design choices, not published 稳付pay API enums.
4. Apply disclosed rejection and expiry rules
Disclose whether the acceptance window starts at payment confirmation or notification, its timezone and boundary convention. Rejection or silence follows the agreed support process, without automatically converting the gift into the payer’s credits. If acceptance races with expiry, only one final decision can take effect. Hold delivery while uncertain, so the same gift is not both refunded and fulfilled.
5. Deliver once per gift reference
Give each gift a business reference linking payment, acceptance and delivery. Repeated callbacks, resent notices and page refreshes retrieve the same state. For example, one order gifting one cosmetic with two acceptance clicks should produce one acceptance and one delivery. If a remote game response is lost, investigate using the original reference rather than creating a second gift to bypass uncertainty.
6. Record refund destination and entitlement handling
For disputes after acceptance, check delivery, use and reversibility. A recipient cannot claim the payment simply by showing a gift page; refund destination and route follow actual channel rules and purchase terms. Do not promise that used items can always be recovered or deduct unrelated assets of equal value. Retain request, review, entitlement changes and refund evidence; compensation identifies its original gift.
7. Reconcile gift counts before settlement links
Daily, classify paid gifts as awaiting acceptance, accepted but pending delivery, delivered or under support review. Explain each record rather than comparing payment totals alone. Delivered gifts need acceptance evidence; refunded ones need an entitlement outcome. Reconcile delivery separately from merchant USDT settlement: settlement does not prove acceptance. Channel acceptance and settlement conditions remain subject to agreement.
Related verification guide: Payment callbacks
8. Gift acceptance checks and FAQ
With owned test accounts, cover acceptance, rejection, expiry, duplicate clicks, acceptance after refund and unknown remote results. Payer and recipient pages show only necessary data; support traces order and gift references. Confirm gifting scope through https://t.me/tonyyyds before onboarding. This workflow neither establishes an existing gift plugin nor replaces the game operator’s product rules.
Does nonacceptance cancel payment automatically?
No. Payment and acceptance are separate. Follow disclosed support rules after expiry and verify any refund independently.
Does resending a notice create another gift?
It should not. Reuse the gift reference and check original delivery on repeated acceptance or callbacks.
Can a payer see the recipient’s password or activity?
Payment grants no such permission. Show necessary gift status; account and activity access require appropriate authorization and privacy rules.
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 ↗