The Sandbox is a great tool to safely play around with our APIs and to get your integration set up. It offers a payment simulator that allows you to test various flows and scenarios.

It is not connected to our core banking system, any payment schemes or clearing houses. Due to its isolated nature, expect some limitations and Sandbox-specific behavior, which we'll guide you through.

Getting access to the Sandbox API

The authorization method is the same across both the Sandbox and production environments (see Connect to the API). However, since the Sandbox environment is a completely separate environment, it requires a separate set of certificates. Your Integration Manager will guide you through the process of getting set up to use it.

Your Sandbox will be set up with one company group containing two companies and with assorted account types.

📘

Don't forget to use the correct base URLs

The Sandbox base URL is https://sandbox.bankingcircleconnect.com and for the authorization endpoint it is https://authorizationsandbox.bankingcircleconnect.com/.

Best practices

The Sandbox is meant as an integration tool and we will review your integration to give you input on best-practice patterns before you are rolled on to the Production environment. In general, you should ensure the following for optimal performance:

• Renewing access tokens only when an active session expires, not with each request. If a session outlasts the access token's lifespan (300 seconds), renew the token
• Not making data requests than necessary. For real-time data updates, we recommend using webhook notifications

👍

Also want access to the Sandbox Client Portal?

Your Integration Manager can also give you access to our Client Portal (i.e. User Interface)