Test the Bridge Transfer (sandbox credentials)

To try the Bridge Transfer to execute transfers, you need to have at least one synchronized Demo Bank item.

📘
Please refer to Test the Bridge Connect for more details about the Demo Bank.

To test different cases with Demo Bank, you can use the label field and you will get different results. Here are the different rules.

To apply different Strong Customer Authentication select the sender account you need

Sender Account	Result
Account (For Single Transfers Only) Without Sca	The user won't have any Strong Customer Authentication to initiate a single transfer This sender account only supports single transfers
Account With Otp Sms	The user will have to go through a SCA with a One Time Password (enter 123456 to get a success)
Account With Sca App2app	The user will have to go through an app to app SCA (you just need to wait for a few seconds and it will redirect you to the success page)
Account Without Sca	The user won't have any Strong Customer Authentication to initiate transfers

To apply different statuses on a transfer

Label	Result
`initiated executed`	The transfer will first have the status `initiated` and it will change to `executed` after an hour
`initiated failed`	The transfer will first have the status `initiated` and it will change to `failed` after an hour In this case the `status_reason` will always be `regulatory_reason`
`executed`	The transfer status will be `executed`
`unknown`	The transfer status will be `unknown`

To apply different status_reason on a transfer

When a transfer fails, you will get more information in the status_reason field. To test them, you just need to set the transfer label as the status_reason you want to get. In this case the transfer status will always be failed. Here is every possible status_reason you can get and test:

status_reason / label
`invalid_sender_account`
`closed_sender_account`
`blocked_sender_account`
`not_authorized_for_sender_account`
`too_many_transfers`
`invalid_execution_date`
`cancelled_by_customer`
`technical_error`
`regulatory_reason`
`not_specified`
`invalid_receiver`
`invalid_credentials`

To apply different status_reason on a bulk

Bulks can also have status_reason when a whole bulk fails. You can test them by setting a transfer label as bulk {{status_reason}}. If you define several different labels this way, we will apply the first label we read.

status_reason can be different for a bulk and a transfer so here is the list for bulks:

status reason / label
`bulk invalid_sender_account`
`bulk closed_sender_account`
`bulk blocked_sender_account`
`bulk not_authorized_for_sender_account`
`bulk too_many_transfer`
`bulk invalid_execution_date`
`bulk cancelled_by_customer`
`bulk technical_error`
`bulk not_specified`
`bulk invalid_credentials`

You can also test an amount error by entering an amount inferior to 1€ or superior to 30 000€ (you can execute transfers inferior to 1€ or superior 30 000€ in real life, depending on your bank).