Sandbox & testing
A fully simulated provider so you can test every path locally, without credentials or real money.
Connect the Sandbox provider (card, Apple Pay, Google Pay) and Crypto Sandbox in TEST mode. They behave like real providers: hosted pages, signed callbacks, status queries and refunds.
Card outcomes (sandbox bank page)
| Scenario | What happens |
|---|---|
success | Callback: succeeded → payment.completed |
declined | Attempt fails with card_declined; customer can retry another method |
insufficient_funds | Attempt fails with insufficient_funds |
expired | Attempt expires at the provider |
delayed_success | processing now, success ~8s later |
duplicate_callback | The same callback arrives twice — processed once |
out_of_order_callback | Success first, then a stale processing callback — ignored |
At attempt creation (checkout test panel)
| Scenario | What happens |
|---|---|
timeout | The provider charges but never answers. The payment becomes unknown (never failed) until reconciliation discovers the success. |
processor_unavailable | The provider refuses the request; the customer can try again. |
Wallets
The checkout test panel toggles whether the “device” supports Apple Pay / Google Pay (hidden when unavailable) and opens a simulated wallet sheet where you can authorize, decline or cancel.
Crypto
Choose Crypto, pick an asset and network, then drive the simulated processor from the test panel: payment_detected, confirming, completed, underpaid, overpaid, expired, provider_callback_delayed, duplicate_callback. Select exchange_quote_expired before choosing an asset to test quote expiry.