# Sandbox > Sandbox is a built-in test processor. It is a simulated gateway, not a connection to a real payment service provider, so no funds ever move and no live merchant Sandbox Sandbox is a built-in test processor. It is a simulated gateway, not a connection to a real payment service provider, so no funds ever move and no live merchant account is required. Use it to build and test end-to-end payment flows — authorisations, captures, refunds, voids, 3D Secure, and saved payment methods — against deterministic test data before connecting a production payment provider. Sandbox needs no credentials and has no external onboarding step: you choose what it emulates with toggles in its connection settings. ## At a glance | | | | ------------------ | -------------------------------------------------------- | | **Type** | Gateway | | **Connection** | No credentials (settings toggles only) | ## Where it operates Sandbox is a test processor and is not tied to any acquiring region, so merchants can onboard it in every supported country. ## Payment methods Sandbox simulates each payment method with fixed test credentials rather than contacting a real network, so every result is deterministic and repeatable. Each method is enabled independently in the connection settings (at least one must be enabled). Our integration supports: - **Cards:** Visa, Mastercard, American Express, Discover, Diners Club, JCB, and UnionPay. Dedicated test card numbers drive specific outcomes — successful authorisation, insufficient funds, stolen/seize card, invalid CVC, rate-limit, 3D Secure required, refund declined, and delayed processing. - **Bank debits:** ACH (USD) and SEPA (EUR), each with test routing/account numbers or IBANs that simulate success, account closed, insufficient funds, unauthorised debit, and other decline scenarios. - **Hosted payments:** a simulated hosted-payment flow for testing redirect and off-session token capture. The gateway also exposes developer-mode options for testing edge cases, including pending/settlement delays, required-field enforcement (CVC, AVS, account name, email, phone, line items), a 3DS challenge window, and disabling network tokenisation or card saving. Network tokenisation, which Apple Pay and Google Pay use, is on unless you disable it. ## Setting up Sandbox See [Connecting Sandbox](/payment-providers/sandbox-connect/) for adding it and what each setting does, and [Sandbox test cards](/payment-providers/sandbox-test-cards/) for the card and bank details that give each result.