A paid order missing from USDT settlement: inclusion rules and catch-up evidence
A missing settlement line does not make a customer payment unsuccessful. Find which inclusion condition remains unmet, then check other batches before requesting a catch-up. This is a merchant reconciliation design, not a claim that 稳付pay offers an automatic catch-up tool.
Continue by topic
1. Join eligible payments to settlement lines by identity
Keep verified merchant ownership, original order ID, payment reference, amount, currency and verification time. Each settlement list needs a batch, version and scope. Amount plus date is not a reliable join key.
Agree which confirmation, review, adjustment and cutoff rules determine inclusion. This guide sets no minimum or waiting period. Merchant USDT settlement of CNY collections currently uses TRC20; direct receipt into an owned wallet is a separate flow.
2. Give every excluded order an evidenced reason
Classify orders as included, awaiting an agreed condition, handled elsewhere or requiring review. Attach evidence, an owner and the next action. Export filters, merchant namespaces and mismatched versions can also hide a line.
In a fictional example the list contains A and B, while verified payments include C. Search older batches and adjustments for C before evaluating eligibility. Equal amounts do not make two orders duplicates.
3. Preserve the source and the remaining allocation
After confirming an omission, agree the correction method, calculation and execution evidence. Link the catch-up to the original order, reason and list version. Do not create another customer payment. For partially allocated orders reconcile only the remaining portion.
Use a unique local allocation reference and recheck versions during concurrent changes. Database isolation protects local records, not an external USDT transfer. An unknown transfer outcome stays unresolved; do not send another transfer as a test.
4. Close with an explained difference
Compare eligible payments, actual settlement lines, confirmed adjustments and unresolved items order by order. Retain approval, execution evidence and receipt checks separately; approval is not receipt.
Simulate missing lines, repeated exports, cross-batch allocation, partial handling and lost responses using owned test records. Preserve customer payment facts while tracking merchant settlement exceptions independently. Never request passwords, private keys or recovery phrases.
Frequently asked questions
Can I request another settlement immediately?
First check other batches, export conditions and actual execution. Confirm the remaining allocation before arranging a correction.
Does T0 automatically resolve every discrepancy that day?
No. Agreed settlement timing does not replace order mapping, exception review or on-chain receipt evidence.