Using test data in sandbox to improve and secure your integration
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:
| IBAN | Error Code | Error type |
|---|---|---|
| ES3930350000020000000201 | ERR-0001 | blocked_account |
| ES3930350000020000000104 | ERR-0002 | closed_account |
| ES9030350000070000000202 | ERR-0003 | integration_error |
| ES2530350000030000000501 | ERR-0004 | invalid_bank |
| ES2330350000000000000005 | ERR-0005 | recoverable |
| ES9530350000050000000210 | ERR-0006 | suspended_bank |
| ES7430350000090000000101 | ERR-0007 | wrong_account_number |
| ES5530350000000000000302 | ERR-0008 | wrong_amount |
| ES1730350000040000000305 | ERR-0009 | wrong_operation_code |
| ES1730350000040000000402 | ERR-0010 | other |
The following test data will raise a custom reason code unrelated to the network you are using.
| IBAN | Error Code | Error type | Reason |
|---|---|---|---|
| ES0330350000050000000605 | ERR-0011 | processor_failure | DEVERR1 |