Declined Reasons
When a verification request involving Bank Account Verification is declined, the following reasons are presented to the end user or client.
| Status Code | Description |
|---|---|
| SPDR373 | The provided account is inactive or restricted. |
| SPDR374 | The provided name could not be sufficiently matched against the account holder records. |
| SPDR375 | The provided account could not be located. |
| SPDR376 | Match confidence was too low to confirm the account holder. |
| SPDR377 | The provided account number is not correctly formed. |
| SPDR378 | The provided IBAN is not correctly formed. |
Which Reasons Apply to Which Check
A decline reason describes the check that ran, so the same underlying outcome is reported differently depending on what was submitted.
| Check | Reasons you can receive |
|---|---|
| BAV Check, country that matches the name | SPDR373, SPDR374, SPDR375, SPDR376 |
| BAV Check, country that confirms existence only | SPDR373, SPDR377 |
| IBAN Check | SPDR378 |
An IBAN Check reads the structure and the check digits of the IBAN and contacts no bank, so the only way it can fail is a malformed IBAN. It never returns a name match or an account status reason.
For countries whose check confirms only that an account exists — it is not a name match — a malformed identifier is reported as SPDR377, naming the account number rather than an IBAN, and every other decline is reported as SPDR373. Those corridors answer a single question, so the distinction between a missing account and a blocked one is one they never draw.
A decline reason is returned in declined_reason alongside declined_codes in the response. See Response Parameters.