Alipay callback logged before order creation: clock skew, event time and reconciliation windows

A callback logged at 12:00:05 and an order logged at 12:01:30 do not alone prove a fraudulent notification or broken order. Identify the machines, timezones and processing stages before investigating the original payment. 稳付pay callback authentication still follows the formal contract; correcting a clock cannot replace signature verification.

Continue by topic

Confirm onboarding and time conventions first

稳付pay publicly lists WeChat Pay, Alipay and UnionPay, subject to configuration. Confirm enabled methods, rates, amount limits and extra charges. Explain the authorized business, domain, server layout and callback route before onboarding; obtain private parameters and keys after account setup. Agree on clock alerts, log retention and incident handling rather than inventing a universal callback expiry window.

Merchant USDT settlement after CNY collection currently uses TRON/TRC20 only. Confirm triggers, charges and timing separately. Payment success, customer credit or entitlement delivery, and merchant settlement require separate evidence. Similar timestamps do not make them simultaneous. This guide addresses merchant-side clock evidence without changing the payment protocol.

Label every timestamp by its origin

Distinguish local order recording, any event time actually supplied by the provider, edge arrival, application receipt and ledger commit. Store only fields that the formal contract provides. If provider time is absent, mark it absent; do not present receipt time as payment time. Retain timezone, machine, source, original value and normalized value.

Illustration: a creation server runs 90 seconds fast and records the real 12:00:00 as 12:01:30. A receiver records arrival at the real 12:00:05. The apparent reversal does not justify rejecting payment. Inspect controlled hosts for synchronization status, measured offset and clock adjustments, then check queue and log-buffer delay. Do not edit historical logs to make them agree.

Use time for diagnosis and identity for credit

Follow the public signature and callback guides, with actual parameters and acknowledgments governed by the formal documentation. Authenticate and match merchant, original order, amount, currency and success state. Deduplicate by durable order identity and commit payment evidence with one credit or entitlement change within the local transaction boundary. An earlier displayed time must not reverse confirmed success; a newer time cannot authorize an untrusted message.

If the actual protocol signs time or imposes a validity check, preserve that check. Do not widen tolerance or disable it to hide clock failure; coordinate recovery and query the original order. A monotonic clock can measure elapsed work within a process. Values from separate machines are not comparable event times and must not be stored as payment timestamps across restarts.

Repair and reconcile a bounded overlapping interval

Retain incident boundaries, affected hosts and measured offsets. Correct the operating environment after agreeing on timezone conventions, while keeping original logs. Recheck a bounded interval that covers potentially missed records; determine its size from actual skew, delays and query limits. Deduplicate overlap with the same payment identity instead of moving order dates.

Use isolated simulations for fast and slow clocks, timezones, clock rollback, delayed logs and duplicate notifications. Verify one payment credit, documented delivery and a separately matched settlement. Assign discrepancies for review. Do not publish callback-latency or success-rate conclusions while timestamps are unreliable, and do not ask customers to repay unresolved orders.

Frequently asked questions

Does displaying everything in UTC remove skew?

No. UTC standardizes representation; synchronization and timestamp origin still need verification.

Can the newest log overwrite order state?

No. Advance state using authenticated evidence, transition rules and durable deduplication. Cross-host log ordering is not payment proof.

References