Handle Expired Outpay Checkouts and Late Payments
Recover safely when a customer sends USDC after an Outpay checkout expires, preserving transaction evidence and avoiding false fulfilment.
Who this is for
Developers and merchants investigating a payment that arrived after a checkout's expiry window closed.
Steps
- Read the checkout's status from your server or the Dashboard.
- If the checkout is
expired, do not ask the customer to resend to the old recipient without an operator decision. - Capture the transaction hash, amount, token contract, network, and recipient address.
- Create a new checkout for a new order attempt, if the merchant elects to continue.
- Record the old checkout and the late transfer as an exception for reconciliation.
No automatic refund or late-payment workflow
The current release records a late payment as an expired or invalid path, but does not provide a merchant-facing refund or remediation API. Do not document a manual wallet transfer as an Outpay product feature — see settlement.
Expected result
The late transfer is documented with enough evidence (transaction hash, amount, timestamps) for a manual, operator-approved resolution, without implying Outpay can reverse or automatically credit it.
Related documentation
- Payment lifecycle — why a checkout expires in the first place.
- Transactions — the merchant-facing status table.
- Support — escalating a specific late-payment case.
Receive Outpay Payment Webhooks Safely
Verify, deduplicate, acknowledge, and fulfil an Outpay checkout.paid webhook after a confirmed USDC payment on Base.
Test an Outpay Checkout Integration Locally
Validate an Outpay payment adapter locally across API, webhook, expiry, and reconciliation layers without trusting browser redirects or fake blockchain claims.