An Alipay order expires, then a success result arrives: late confirmation and fulfillment
A success message after an expiry screen should neither be discarded nor automatically extend membership. Establish who declared the order expired and which payment attempt received the money. Actual channel states and closure capabilities must follow the agreed integration protocol.
Continue by topic
Separate three different kinds of ending
A page countdown ends a display window. Local cancellation is a business decision. Confirmed channel closure needs the channel’s own trusted result. One boolean cannot represent all three without losing genuine late payments.
Retain the original identifier, quote, customer ownership and reason. Do not delete an expired record or reuse its identifier. Where a closing process exists, distinguish sending a close request from receiving confirmation that it completed.
Verify the result against the original attempt
Verify the notification under the actual collection agreement and reconcile merchant, original order, currency and amount. Browser returns, screenshots and unverified messages are investigation clues only. Resolve conflicting results through an authorized query or technical review rather than newest-message-wins logic.
Example: O1 stops being displayed at 12:00 and its trusted confirmation arrives at 12:01. Keep the local expiry, payment-confirmation and notification-receipt times separately. This distinguishes late payment from late delivery; it is not a platform timing promise.
Decide payment truth and deliverability separately
If the original product remains deliverable, use its snapshot and unique fulfillment record. Repeated results should find the existing entitlement. If stock, promotion eligibility or a service window has expired, use a defined after-sales review instead of substituting another plan without agreement.
Keep the confirmed payment and track pending fulfillment, review or refund handling separately. Confirm available refund arrangements with the technical team. Marking the local order unpaid is not a substitute for actually returning money.
Keep unresolved expired orders in bounded reconciliation
Use an agreed review mechanism for locally expired orders whose payment outcome remains unknown. Set query frequency, review horizon and escalation according to the actual service, without infinite polling or deleting unresolved evidence at a timer boundary.
Test notification-first, query-first, closure/result conflicts, two genuine payments and repeats during after-sales handling. The final record should explain when payment was confirmed, which old order it belongs to, the fulfillment outcome and who authorized the resolution.
Frequently asked questions
May all notifications be ignored after the countdown ends?
No. Display expiry does not prove the payment side ended; reconcile trusted results against the original order.
Can a newer success message overwrite confirmed closure?
Not just because it is newer. Check source, order mapping and actual channel state through the authorized reconciliation process.