After a WeChat or Alipay collection refund: balances, entitlements and settlement adjustments
A support request, a completed payment refund and a customer-balance change are separate events. Do not turn the original paid order into an unpaid one, or leave all spendable credit after a confirmed refund. Confirm the channel’s actual refund process with the technical team; this article does not announce a public automated refund API.
Continue by topic
Create a refund record without erasing payment history
Use an internal refund identifier linked to the original order, requested amount, currency, reason and processing state. Preserve the confirmed payment and original credit entry. Requested, processing, unknown, completed and declined are illustrative merchant states, not gateway enumeration values.
A repeat of one request should find its existing record. A separate partial refund needs a separate relationship. Consider completed and in-flight amounts together so two concurrent requests cannot both claim the same refundable portion.
Reconcile consumption before agreeing the refund
Separate remaining purchased credit, promotional allocations, consumed items and time-limited membership rights using the terms disclosed at purchase. A visible balance does not establish which top-up funded it; currencies and customer accounts must stay separate.
For example, a top-up grants 100 internal units and 30 have been used. The remaining 70 units are not automatically CNY70 refundable. Confirm conversion rules, promotions, product terms and the actual refund arrangement, including how further spending is treated while a request is pending.
Apply the final reversal once a trusted result is confirmed
A refund-request receipt, screenshot or processing message is not final evidence. Keep uncertain results under reconciliation rather than issuing uncontrolled repeat requests. Apply the corresponding final balance or entitlement reversal only from the agreed trusted completion result.
Use a durable business identifier and a controlled transaction for the refund record and related ledger changes. For work across services, retain recoverable tasks and completion evidence; essential adjustments must not exist only in an in-memory queue after acknowledgement.
Reconcile merchant settlement separately
Connect the customer refund to its original payment and completion evidence. Track channel charges, previously settled batches and subsequent merchant adjustments separately. Settlement to the merchant in USDT does not automatically mean that the customer refund uses USDT.
Agree the route, conversion and costs where applicable. Test partial refunds, repeated results, simultaneous spending and refunding, and temporary entitlement-service failures. The records should explain which payment was refunded, which rights changed and why a settlement difference remains.
Frequently asked questions
Can the entire balance be removed as soon as a request is submitted?
No. Identify the original order and rights, and follow the disclosed pending-request rules. An application is not a completed refund.
Is an automated refund API publicly available?
No such capability is promised here. Confirm supported channels, conditions and handling with 稳付pay’s technical team rather than inventing endpoints or status fields.