Payments and USDT settlement across midnight: cutoffs and late evidence
A customer pays before midnight, the notification arrives tomorrow, and the USDT transfer meets its confirmation conditions later. Daily reports can therefore change on different dates. 稳付pay provides T0 real-time USDT settlement under the onboarding agreement; this guide describes merchant reporting, not a new deadline or an additional platform settlement for direct wallet receipts.
Continue by topic
Define three timestamps and one reporting boundary
Retain the verifiable payment time, notification receipt time and time the USDT transfer meets the agreed confirmation conditions. Mark unavailable payment times as missing rather than inventing them from the browser clock. Store UTC or offset-aware timestamps, plus the reporting timezone and rule version.
Use a half-open daily interval: include its start, exclude its end. Bangkok November 3 ends at November 4 00:00, which belongs to the next day. Convert Beijing and Bangkok timestamps to a common basis before comparing them. Internal reporting rules do not change the channel statement definition.
Freeze a cutoff snapshot and retain unresolved items
At cutoff, separately list verified receipts, approved settlement receivables, transfers in progress and confirmed wallet receipts. Save the snapshot creation time, evidence cutoff and unresolved cases. A screenshot cannot fill a missing server confirmation; an unknown query result is not a failed payment.
Reconcile the original currency separately from USDT. Roll original-currency receivables forward using opening balance, verified income, refunds, agreed fees, settlement allocations and documented adjustments. Specify the sign of each adjustment. Link the USDT payable and received quantities by settlement reference; never subtract different currencies directly.
Example: late evidence is not a second payment
Illustration: order O was paid on November 3 at 23:59:50+07:00, its notification arrived November 4 at 00:00:20+07:00, and wallet confirmation occurred at 00:03. If receipts belong to the payment date, the initial November 3 snapshot may omit O. A correction attributes the receipt to November 3 and records that it became known November 4; the wallet report records its actual confirmation date.
These are fictional timestamps, not service timing data. Keep one payment entry and version the report correction with its reason and approver. Do not count the correction again as November 4 income or backdate wallet confirmation to make totals match.
Verify the correction and hand over open cases
Exercise late and duplicate notifications, success exactly at cutoff, and transfers still awaiting confirmation. Recognize each payment once. Correct attribution only after verifying channel evidence. If a channel statement uses another timezone, preserve its original values and attach a conversion schedule.
Each correction lists order and settlement references, all three timestamps, old and new attribution, evidence and the unresolved-case owner. Escalate overdue reviews with a next check time. RFC 3339 supports timestamp representation; the snapshot and correction procedure is a merchant design, not a claimed 稳付pay reporting feature.
Frequently asked questions
Does T0 require every report to finish on the same date?
No such conclusion follows. Interpret timing, triggers, conversion, fees and confirmation under the actual agreement, while preserving payment, receipt and wallet dates separately.
Should a closed daily report be deleted when a late notification arrives?
Keep the sealed version and append an evidenced correction after checking the original order. Reopening a period follows merchant rules; never erase history or count another payment.