Skip to main content
The sandbox runs the same API as production, but no real money or mainnet crypto moves. Use it to run every order outcome your integration must handle before you ask for production access.

​
Hosts and keys

Sandbox keys only work on sandbox hosts. See Environments.

​
Testnets and test tokens

In sandbox, crypto is delivered on testnets. Testnet chains come back from the supported-config endpoints with isTestnet: true. Production only returns mainnet chains. Use these codes as dstChain (onramp) or srcChain (offramp). Your account may have only some of them enabled, so check the live list first: see Supported config. Use a testnet wallet address you control.

​
Simulated payments

In sandbox, payments go through a payment simulator instead of real card networks and banks. You turn simulation on and pick the outcome of each payment (accepted, declined or expired) from your Partner Dashboard.

Payment Simulator

Enable simulation, settle card and bank transfer payments, and see what each outcome does to the order.

​
KYC

Sandbox has no self-serve way to force a KYC approval or decline yet. To test KYC outcomes, email [email protected].

​
Suggested test run

1

Happy path

Create an onramp order to a testnet wallet, accept the payment in the simulator, and confirm you get processing and completed webhooks and a dstFillAmount.
2

Payment declined

Reject or fail the payment. Confirm you show the user an error and treat payment_failed as final.
3

Expired

Expire the payment, or leave the order unpaid for 15 minutes. Confirm you handle expired.
4

Webhooks and polling

Verify webhook signatures, and check that Get Order returns the same status.
When every case passes, move on to the Go-Live Checklist.