Sandbox
The sandbox environment lets you test your integration without processing real payments or creating real orders.
Sandbox vs Live
| Feature | Sandbox | Live |
|---|---|---|
| Base URL | Same (/v2/partners) | Same (/v2/partners) |
| API Keys | Sandbox-prefixed keys | Production keys |
| Payments | Simulated (no real charges) | Real payment processing |
| Rate Limits | 5x higher than production | Standard limits |
| Webhooks | Delivered normally | Delivered normally |
| Order Data | Test data, periodically purged | Persistent |
How It Works
Your sandbox and live environments are determined by the API key you use. Sandbox API keys are issued separately from production keys in your partner dashboard.
- Use sandbox keys during development and testing.
- Switch to production keys when you are ready to go live.
- Both environments expose the same endpoints and accept the same request formats.
Simulated Payments
In sandbox mode, all payment processing is simulated:
- CARD payments are always approved without contacting the payment processor.
- GOOGLE_PAY and APPLE_PAY tokens are accepted without validation.
- IDEAL, REVOLUT, and BANCONTACT flows complete immediately without redirect.
- No real money is charged and no real payment method is required.
Testing Tips
- Use sandbox-prefixed email addresses (e.g.,
sandbox-user@example.com) for customer data to clearly distinguish test orders. - Test webhook delivery in sandbox to verify your endpoint handles payloads correctly.
- Simulate error scenarios by using specific test values documented in your partner dashboard.
- Rate limits in sandbox are 5x the production limits, giving you more room to test rapidly.