Connecting Sandbox
The Sandbox gateway is a simulated payment provider for testing. It needs no credentials or account with anyone else, and no money moves.
Connecting it
Section titled “Connecting it”The Sandbox gateway is only listed on sandbox (test) accounts. Add it like any other payment provider: choose Sandbox from the list of providers and save. On a test account with no providers yet, Skip on the provider list installs it for you, so you can try the checkout straight away.
Enable Cards is on when you first connect it. You don’t need to change any other settings unless you are testing a particular scenario.
Settings
Section titled “Settings”| Setting | What it does |
|---|---|
| Enable Cards | Takes credit and debit cards at the checkout. |
| Enable ACH | Takes ACH (US bank debit) at the checkout, for USD payments only. |
| Enable SEPA | Takes SEPA (euro bank debit) at the checkout, for EUR payments only. |
| Enable Hosted | Emulates a hosted checkout: a pay button that opens a popup window with another provider’s checkout, as with GoCardless, Mollie or PayPal. In the popup you choose whether the payment succeeds or is declined. |
| Developer Mode | Shows the advanced settings below. If you aren’t building an integration, leave it off. |
With Developer Mode on, these settings appear:
| Setting | What it does |
|---|---|
| Disable Network Tokenisation | Turns off network token payments, which Apple Pay and Google Pay use. Network tokenisation is on unless you select this. |
| Disable Save Card | Emulates a payment provider that can’t save cards. |
| Pending | Emulates a payment provider that returns PENDING instead of approving straight away. Enter how many Seconds the payment stays pending (for example 600 for 10 minutes). |
| JS Wrapper | Emulates a payment provider that adds its own JavaScript library to the checkout page. |
| Require 3DS Window | Emulates a payment provider whose 3D Secure step must open outside an iframe. |
| Require Account Name | Emulates a payment provider that needs an account name to authorise a payment. |
| Require address (AVS) | Emulates a payment provider that needs a billing address to authorise a payment. |
| Require CVC | Emulates a payment provider that needs a CVC to authorise a payment. |
| Require Email | Emulates a payment provider that needs an email address to authorise a payment. |
| Require Phone | Emulates a payment provider that needs a phone number to authorise a payment. |
| Require Line Items | Emulates a payment provider that needs line items to authorise a payment. |
The checkout handles most of the developer settings for you. If you build your own integration, still handle a PENDING result and the approval or decline webhook that follows.
The card numbers, bank accounts and other details that give each result are in Sandbox test cards.
Was this page helpful?
What went wrong?
Thanks for telling us.