Test the Bridge Connect

Sandbox environment

When using sandbox credentials, you can use a special bank called Demo Bank (id = 574) to simulate the synchronization process through the Bridge Connect without using your personal bank credentials.
This can be very convenient when doing tests. Particularly when dealing with item statuses.

Environments are fully enclosed from each other. Resources (users, transactions, accounts, items, etc...) created with sandbox keys are not visible nor usable using production keys and vice versa.

Demo Bank

📘
You can select the Demo Bank when you're redirected in the Bridge Connect

Test the usual flow

Once you have chosen the Demo Bank, you can use any login and password.
Whatever the credentials used, you will access the same fake banking data:

4 checking accounts and 2 deferred debit cards with various transactions
1 saving account, 3 titles accounts and 2 credits

Test your integration

Use the logins below with any password:

Login	Test case
`success`	Successful synchronization (default case if you fill any random login).
`otp`	Synchronization needs a strong customer authentication with a One-Time Password (fill any code).
`otp_fail`	Synchronization needs a strong customer authentication with a code (fill any code). The code will be detected as wrong and you will be able to retry.
`app2app`	Synchronization needs a strong customer authentication with an App to App (wait for an automatic validation).
`app2app_expiry`	Synchronization needs a strong customer authentication with an app to app. The validation will automatically expiry.
`402`	Wrong credentials: item status `402`. You will be able to retry.
`429`	An action is needed on the bank's interface: item status `429`.
`1003`	Technical error: item status `1003`.
`1005_CLOSED_ACCOUNT`	For each item status, you can test specific errors by adding a `status_code_info` at the end.
`success.1010`	You can combine several logins, to experiment precise cases. In that case, the first synchronization will be in success and then the item will have a status `1010`. You can add some more, each refresh will update the status.
`success.1009`	The first synchronization will be in success and then the item will have a status `1009`.
`risky`	Add a risky transaction in the synchronized data.
`pro`	Add a pro account that the user needs to validate in the Bridge Connect. If the user quits the funnel before, the item will have the status 1100. You will need to call Validate pro items to make him validate the pro item.

You can test two transactional mechanisms:

is_deleted : after the full refresh, a temporary transaction is created on the checking account "Compte courant 1". For each next refresh, this transaction type will be deleted then recreate.
is_future : you can fetch some future transactions on the checking account "Compte courant 1".

Postman collection

You can test our API with our Postman collection: