Testing a successful payment is not enough: declines, refunds and repeat notifications are what usually break in production. Walk each scenario end to end — from creating the payment to what your own system finally shows.
Scenarios to walk through
- Successful payment. The order becomes paid and the receipt reaches the buyer.
- Decline. The buyer sees a clear message and the order is not marked paid.
- Refund. Both full and partial — check the amounts match what you expect.
- Repeat notification. A second message about the same payment must not change the order twice.
- Unreachable handler. Make sure an order can still be closed by fetching the status manually.
Before live traffic
- The keys in settings belong to the live store, not a test one.
- The notification address points at production, not a developer tunnel.
- Logging of incoming notifications is on — without it incidents are unexplainable.
You can see what checkout looks like for a buyer on the demo page.
