Compare sandbox checkout states with order records
Run normal, declined-payment, unavailable-stock and refresh cases using the gateway’s supported test environment. Reconcile browser messages with application and payment records for each synthetic identifier. The checkout repair is accepted when the intended order state agrees across those records, not merely when one successful card path looks complete.
Worked example — illustrative data.
| Test case | Expected state | Evidence to capture |
|---|---|---|
| Valid synthetic order | One intended order and confirmation | Test ID, timestamp and sanitized response |
| Declined test payment | Clear recovery; no paid order | Provider-supported test case and visible error |
| Unavailable SKU | Accurate stock message before completion | Selected SKU and inventory state |
| Refresh after completion | No unintended duplicate order | Order IDs and browser sequence |
Confirm the gateway’s current supported sandbox procedure before testing. Record environment, relevant extension versions, selected SKU, delivery choice and test scenario. Follow the test ID through browser, application and gateway logs without storing payment secrets or real customer details. Reproduce one failure at a time and preserve the original response before changing configuration. After a fix, repeat the failed case and a normal purchase path to check for collateral breakage.
Payment success can outlive a failed confirmation screen
A payment can succeed while the order confirmation fails. Do not ask the customer to retry blindly or label the order unpaid solely from the browser screen; reconcile the actual payment and order records through the responsible owner.
Accept the repair only when the intended order state, customer message and downstream record agree for the reproduced case. No real purchase or payment action is needed for this worksheet.
Continue with Guides for stores, software teams and local businesses, eCommerce website design and development and Verify purchase and demo events after a website change.
Before applying the specimen, verify exact feature availability, required permissions and supported field formats in the provider’s current documentation and your store.