Sandbox
Setting up the Sandbox environment and testing payments
Barion Sandbox is a non-PCI DSS compliant test server that provides a playground environment for Barion developers, that’s identical to the production server in terms of Barion API support.
The point of Barion Sandbox is to simulate Barion Smart Gateway features, and Barion API endpoint functionality on the live Barion server environment, so you can try out your custom or plugin-based webshop integration without real-world financial consequences.
Note that because the production server and Barion Sandbox are separate environments, you can use the same email address as Barion ID on both.
This also means that you can’t port the Barion Wallet you’ve created in the Barion Sandbox to the production environment – you explicitly need to create a new Barion Wallet in production.
Differences between production and Barion Sandbox
Barion Sandbox differs from the production environment in the following:
- the URL has “test” added:
secure.test.barion.comapi.test.barion.com
- a standard HTTPS certificate is used as opposed to Extended Validation (EV) used on the production server
- transactions are made in nominal funds:
- outgoing transfers to bank accounts aren’t supported
- only the dedicated test bank cards are supported for payments and adding money to your Barion Wallet balance
- test cards that trigger various pre-set payment process responses are supported
- 3D-S authentication isn’t performed when using test cards
- actual bank cards aren’t guaranteed to work
- the RecurringFrequency property of subsequent payments in a subscription payment scenario isn’t checked
- callbacks for payment status changes are sent from a different IP address
- Barion shops are approved automatically – you don’t have to go through onboarding when setting up a test Barion shop
- no KYC procedures are in place:
- there’s no need or indeed way to verify your identity as the owner of a Barion Wallet,
- there aren’t any (transfer, balance, or payment) limits on Barion Wallets in the Barion Sandbox
- no data you enter during registration (email address, shop details, etc.) is checked or verified
- the Barion Smart Gateway is displayed with a warning ribbon
- token payment scenarios are enabled by default
- Barion Bridge is enabled by default
- there’s no SLA for any downtime, or assurance for any potential data loss resulting from a server update
Using the Barion Sandbox
Make dummy purchases in your Barion shop on the Barion Sandbox server using test card data that always returns the same payment process results to test whether your Barion integration reacts properly to various payment outcomes.
Test cards
Each of the ProcessResult property value options in the FundingInformation object returned by the payment state endpoint has a dedicated test card that reliably triggers it.
All test cards accept any future date as expiration date, and any 3-digit number as CVC code.
| Successful | 4444 8888 8888 5559 |
| ProblemWithCard | 4444 8888 8888 4446 |
| LowFunds | 4444 8888 8888 9999 |
| LostOrStolenCard | 4444 8888 8888 1111 |
| Declined | 4444 8888 8888 3331 |
| FraudulentTransaction | 4444 8888 8888 6664 |
| CardSystemError | 4444 8888 8888 7779 |
| ScaSoftDeclined | 4444 8888 8888 0006 |
Using the Barion mobile app in Sandbox mode
Add “test#” in front of your Barion ID email address when logging in to the Barion mobile app to make the app connect to the Sandbox server instead of the production one: test#[email protected]
The Barion mobile app displays a green ribbon across the top of the device screen to indicate that it’s currently connected to the Barion Sandbox server.
Related links
When you’ve made sure that your Barion shop’s website handles all the necessary user interactions and API responses, switch to the production environment.