Orders and reconciliation
Availability and evidence
Confirm payments through server-side Checkout retrieval. Dashboard order lists have unconfirmed availability. If enabled, use them to locate orders while verifying authoritative payment results before delivery. Record submission, payment success, fulfillment and settlement separately.
Find and verify an order
- Find the business order in your own system. If available, filter the dashboard by order ID and time.
- Locate every associated Checkout, not just the latest attempt. Record the test or production environment to avoid checking another account.
- Retrieve the bound Checkout from your server and verify its ID, business order, expected amount and currency. Check the actual payment network when that information is available.
- Inspect both the main status and
exception_status. A failed query means the result is unknown; it does not erase an established payment fact. - Check whether goods, access or a delivery task already exist before acting.
| Checkout status | Action |
|---|---|
open | Wait for payment; resume the original entry while valid |
processing | Payment has been detected on-chain and awaits confirmation; do not request another payment |
succeeded | The session's confirmation threshold was met; verify association, amount, currency and exceptions before fulfillment |
failed | Inspect the reason; later funds do not make the original session successful |
succeeded and failed are terminal. Refunds, late funds and later exceptions do not reverse the main status. A null exception can also mean no payment has occurred.
Fulfill once after confirmation
Separate payment confirmation from fulfillment. Your technical owner should create a unique fulfillment task per business order, so polling, duplicate notifications and multiple successful Checkouts lead to one delivery result. Warehouse, entitlement and content delivery must also support retries using the same business identifier.
For “paid but not delivered,” inspect the payment and fulfillment task before acting; do not ask the customer to pay again. Recover an interrupted delivery through its original task. Two successful Checkouts still authorize only the agreed order delivery; handle extra funds through exception handling.
Reconcile each day
- Fix the timezone, interval, environment and currency, and save that scope.
- Associate orders, all Checkouts, and any available payment, refund and settlement records. Adding these resource amounts together does not produce revenue.
- Compare expected amounts, confirmed receipts, refunds, fees and actual wallet receipts, following the fee guide for each asset.
- Separate unknown results, funds exceptions, paid but unfulfilled orders, fulfilled orders under review, pending refunds and unfinished settlements. Assign an owner and next review time.
- Preserve explanations and final decisions. Append later funds or refunds rather than overwriting the original facts.
Private payments do not guarantee a public payer address or complete public transaction details. Do not infer wallet identity to fill a spreadsheet. See reports and analytics for aggregation rules.