Checkout.com Sandbox
Last verified 2026-08-09
Checkout.com provides a sandbox environment reached by signing up for a test account. Developers test payments, response codes and 3DS flows with documented test cards, and sandbox payments are stored for 30 days. The sandbox uses separate access tokens and a dedicated sandbox API host.
Key specs
| Free tier | Free (test account) |
| Cost | Free |
| Retention | Payments kept 30 days |
| Host | api.sandbox.checkout.com |
Strengths
- Free test account
- Response-code and 3DS simulations
- Separate sandbox host and keys
Trade-offs
- Sandbox payments retained only 30 days
- Requires test-account signup
Best for: Developers integrating Checkout.com payments across cards and alternative methods.
How the Checkout.com sandbox works
Signing up for a Checkout.com test account grants access to the sandbox, which runs on a separate API host (api.sandbox.checkout.com) with its own keys. You test payments, response codes and 3DS flows using documented test cards, and can force specific outcomes to exercise decline and error handling. Sandbox payments are retained for 30 days. It is free. The main things to note are that 30-day retention limits long-lived test data, and you need to complete test-account signup before you can call the APIs.
Head-to-head
Alternatives to Checkout.com Sandbox
See the full Checkout.com Sandbox alternatives comparison →
Sources: Checkout.com testing docs ↗ · Checkout.com API reference ↗
Is Checkout.com Sandbox right for your workload?
Tell us your use case and we'll confirm the fit, flag anything to watch for, and get you real pricing from the Checkout.com Sandbox team. No spam.