A refund request arrives during USDT settlement: holds, in-flight transfers and net adjustments

A customer requests a refund while another operator is preparing USDT settlement. Subtracting a number from a pending total cannot resolve that race. This guide concerns merchant settlement after WeChat or Alipay collection. It proposes a merchant-side workflow, not an available 稳付pay hold API or automatic-refund facility. Direct receipt into a merchant wallet follows a different path.

Continue by topic

Identify the original payment and affected allocation

Keep a refund request ID, original order, requested amount, approval result and responsible operator. A request is not a completed refund. Locate its allocation to a settlement batch and distinguish the affected share from unrelated orders.

Ask the settlement operator whether execution is unapproved, handed off with an unknown outcome, supported by a transfer receipt or confirmed received. A screen saying processing does not establish whether execution can still be stopped. Preserve the payment fact and track refund, settlement and fulfillment separately.

Coordinate approval and dispatch at one boundary

A merchant system can use one disposition record per payment, with a row lock or version comparison to coordinate permission to settle and a review hold. Commit the state, reserved allocation, operator and reason together. A database lock cannot reverse an external transfer; the execution operator must also acknowledge responsibility and report the original outcome.

A successful hold only controls future execution. If an external request has started and its result is unknown, retain its in-flight allocation. Do not spend it again or describe a local cancellation as a reversal of an on-chain transaction.

Work through a partial-refund example

An example order is 100 CNY, the refund request is 30 CNY and the originally agreed settlement quantity is U. U is not 100 USDT; a 30 CNY request does not justify subtracting 30 USDT. Confirm conversion, quote version and fee responsibility under the actual agreement.

Before execution, review the affected allocation and authorize any remaining portion. If U was already transferred and confirmed, preserve the receipt and create a separately approved adjustment receivable or later offset. An unknown transfer remains under review. Do not promise both completed refund and cancelled settlement without evidence.

Resume only with matching authority and evidence

If a refund is rejected or withdrawn, release its hold against that decision without recreating the payment. If completed, append an adjustment linked to its refund evidence. Retain the full history so an operator cannot continue dispatching from an obsolete list.

Rehearse approval before dispatch, dispatch before approval and an execution timeout. Each must explain the payment, executable allocation, in-flight allocation and confirmed receipts. Resume only after the original outcome and current authority agree. Escalate discrepancies instead of using another transfer to test the outcome.

Frequently asked questions

Can the refund simply be deducted from the next batch?

Only under an explicit agreement after checking the original execution, later receivables and fees. A request alone does not authorize a deduction; an unknown in-flight amount must remain traceable.

Does processing mean no transfer was sent?

No. Check the original execution request and receipts with the responsible operator. Keep an unknown outcome under review instead of repeating the action.

References