Sandbox

What The Sandbox Gives You

Sandbox mirrors the production API — same endpoints, request shapes, error codes and webhook events — but no real funds move and no live rails are touched. FX quotes use indicative rates, and settlement outcomes are simulated deterministically so your test suites stay stable.

Test Scenarios

• Simulated fast settlement. Payouts to eligible local rails settle within seconds in sandbox, emitting the full event sequence.
• Delayed settlement. Simulate T+1/T+2 wire behaviour to test your pending-state UX.
• Failure & return. Trigger payout.failed and payout.returned using designated test beneficiary accounts.
• Compliance hold. Exercise your review-state handling with a simulated compliance hold and release.
• FX quote expiry. Let a locked quote lapse to verify your re-quote flow.

Environment Details

Sandbox keys are issued alongside production keys from the developer portal once KYB onboarding is approved. Sandbox data is isolated from production and may be periodically reset; do not store anything you cannot recreate.

A Typical Integration Path

Most teams follow the same arc: wire up authentication and request a first FX quote, create a test beneficiary and payout, then build the state machine around webhook events — payout.processing, payout.settled, payout.failed. The deterministic scenario accounts above let you exercise every branch of that state machine in automated tests, which is the difference between an integration that works in a demo and one that survives production.

Frequently Asked Questions

• Is the sandbox free to use? Yes — no funds move and no per-request charges apply. It exists so you can build and test thoroughly before touching production.
• Do sandbox FX rates match production? Sandbox quotes use indicative rates that are deliberately stable so test assertions do not flake. Production quotes reflect the live market.
• Can I use the sandbox for stakeholder demos? Yes — the full payout lifecycle, including webhook events and settlement confirmations, runs end-to-end with simulated outcomes, which makes it safe for demos and UAT.
• Does sandbox data persist? Sandbox data may be periodically reset. Keep seed scripts for anything your test suite depends on rather than relying on stored state.

Going To Production

When your integration passes the go-live checklist (webhook signature verification, idempotency keys, failure handling), switch the base URL and keys — no code changes required. See the API documentation for the checklist.