Test Data

Payments test data

By default, all payments created in the sandbox will be confirmed as if the money transfer has been successful. However, to test your code against potential errors originating on the banking rails (blocked accounts, temporal Bank institutions' timeouts, etc.), we provide the following IBANs that, when used in the sandbox environment, will always generate a specific error you can manage:

Verifications test data

By default, all verifications created in the sandbox will be confirmed using the code with the number 000000 for it. So if you use any other code number, the verification will remain in delivered status, and you will have 5 attempts in total to confirm it or finally pass to the failed status.

If you created the verification in the sandbox and it is not confirmed within 7 days, the verification will go to expired status.

To test your code against possible errors originating from the bank rails in the verification submission (blocked accounts, temporary timeouts from banking institutions, etc.), you can use the same testing bank accounts provided for payments.

Verification of Payee (VoP) test data

For testing Verification of Payee (VoP) functionality, we provide specific test IBANs that return predictable responses. See our Verification of Payee documentation for detailed information about testing VoP integrations.

Holder Verifications test data

Please note that in the Sandbox environment:

Verifications for the following IBANs will become rejected with a specific error, provided that the request itself is otherwise valid and includes all required data:

Additionally:

• Verifications for the IBAN ES5869409999080993310110 will become confirmed with a close_match result and matched name John Doe
• Verifications for the IBAN ES1569409999020993310111 will become failed
• Verifications for any other IBAN will become confirmed