Set up test environment

Create a Sandbox account, get your test keys, and point your integration at Sandbox - whatever you're building.

Whatever you're building, Sandbox gives you a safe place to rehearse: try payment links with test data, run test checkouts in your plugin, or exercise your API calls - all without touching real money. The Revolut Business Sandbox environment mirrors Production with test data.

How it works​

Setting up your test environment takes one of two paths:

Before you begin​

Run through these checks before you start - they decide which parts of this page apply to you:

• Know your path - building with the API or connecting a plugin that uses an API key, or exploring the dashboard only? The tabs above show which sections you should follow.
• A working email address and phone number - that's all you need to create an account, from the API Console if you're building, or directly in Sandbox if you're not.
• If you're building - a dual-environment setup - decide where your app keeps the base URL and API key config for each environment, so the Sandbox and Production pairs can't mix. See Point integration at Sandbox.
• If your server allowlists incoming traffic - get ready to allowlist the Sandbox webhook IPs alongside your Production ones.

Implement your test environment​

Work through the sections your path needs:

Create Sandbox account​

On the Dashboard only path, this is your only step: create your Sandbox account here, then skip the rest of the steps - no keys to fetch, no development environments to point anywhere.

Here's how to get started:

1. Register: Visit the Revolut Business Sandbox sign-up page and register a new account.

2. Provide details: Fill in the necessary details to create your account.

   • If you're unsure about which option to choose as Legal business type, select Public Limited Company. Freelancer accounts are not supported in Revolut Business.
   • When you see the pop-up about verification email, click the Skip email verification button in the top right corner.
   • When asked for a confirmation code, click the Autofill code button above the input field.

3. Automatic approval: Unlike the Production environment, where account verification and approval might take some time, Sandbox account approvals are automatic. This lets you jump straight into testing without any delays.

4. Log in: Once the registration is complete, you can start using your account. These account credentials are unique to the Sandbox environment and cannot be used in the Production environment.

Get API keys​

Building with the API, or connecting a plugin that uses an API key? This step happens entirely in the API Console - the Console guides cover the mechanisms, and your Sandbox account comes with everything you need:

• Get started with the API Console - create your account and choose Sandbox: a Revolut Business Sandbox account is created for you, and it includes a pre-generated full-access API key.
• Test your integration with Revolut Sandbox - open the Sandbox app and log in with your Sandbox credentials from API Console.
• Create an API key - when you need more keys or different permissions.

Point integration at Sandbox​

The final step of the build path: point whatever you've built - a plugin, or your custom integration - at Sandbox.

Plugins​

If you have installed one of our no-code plugins, you can test payments by changing the mode of the plugin to Sandbox mode (or Test mode in some cases) and, if your plugin connects with an API key, providing your Sandbox API key from the API Console in the configuration.

API​

Most integrations run on two layers: your backend calls the Merchant API to create orders and manage payments, and your checkout initialises a Revolut SDK to render the payment method for your customer. Some flows run on the API alone. Point both layers at Sandbox through a single environment switch in your app - one config value that selects the Sandbox or Production pair across your base URL, API key, and SDK mode. Flip it once, and your whole integration moves:

Server-side calls​

Keep the base URL and API key for each environment in your app's config - never inline - and load the pair that matches the switch:

REVOLUT_MERCHANT_API_BASE_URL=https://sandbox-merchant.revolut.com/
REVOLUT_MERCHANT_API_KEY=r_test_...

REVOLUT_MERCHANT_API_BASE_URL=https://sandbox-merchant.revolut.com/
REVOLUT_MERCHANT_API_KEY=r_test_...

The pairs never mix: your Sandbox API key only works against the Sandbox base URL, and your Production key only against live endpoints. Secret keys carry their environment in the prefix - r_test_... for Sandbox, r_prod_... for Production - but public keys look the same in both environments.

Checkout SDKs​

Every Revolut SDK has its own environment switch - initialise it from the same config, using the public key from the matching account in the API Console: Sandbox key with sandbox mode, Production key with prod:

// Token-based initialisation - mode is a positional argument (default: 'prod')
await RevolutCheckout('order_token_here', 'sandbox')

// Payments module - mode is part of the options object
await RevolutCheckout.payments({ publicToken: 'pk_...', mode: 'sandbox' })

// Token-based initialisation - mode is a positional argument (default: 'prod')
await RevolutCheckout('order_token_here', 'sandbox')

// Payments module - mode is part of the options object
await RevolutCheckout.payments({ publicToken: 'pk_...', mode: 'sandbox' })

With the switch in place, going live is a flip, not a rewire: switch the base URL, the API key, and the SDK mode to Production all at once.

What's next​