Verification statuses

The bank account IBAN verification lifecycle is really simple and consists of the following stages:

Status	Description	Recommended action
`pending`	The Bank Account IBAN Verification has been initiated.	Wait for the status to change.
`inconclusive`	The verification could not be completed (e.g. the Verification of Payee scheme could not be reached or the extraction of the IBAN from the document was unsuccessful). For more details, refer to the status codes section below.	Initiate a new bank account IBAN verification or try with a different bank account details document.
`verified`	The IBAN has been successfully verified against the holder's details provided.	Proceed with accepting the request that required a bank account holder's details verification.
`failed`	The Bank Account IBAN Verification failed due to certain issues. For more details, refer to the status codes section below.	Reject the request that required a bank account verification. If needed, initiate a new Bank Account IBAN Verification.

Status codes

If the verification is inconclusive or failed, the status codes can help diagnose the issue. A verification may include multiple reason codes.

STATUS: inconclusive

ℹ️
Unlike verified or failed statuses, an inconclusive verification does not incur a charge to the client.

Code	Type	Description
`BALV_1000`	Platform error	The verification could not be completed due to a technical issue with our provider. Please initiate a new verification later.
`BALV_1001`	File issue	Unreadable file or image
`BALV_1002`	Verification couldn’t happen	Ineligible: the account is not eligible to the Verification of Payee
`BALV_1105`	Issue with extraction	IBAN extraction from document failed.
`BALV_1106`	Issue with the extracted IBAN	The IBAN must be from a supported country: AT, BE, HR, CY, EE, FI, FR, DE, GR, IE, IT, LV, LT, LU, MT, NL, PT, SK, SI, ES.
`BALV_1107`	Issue with the extracted IBAN	[Deprecated] Following the move to VOP Scheme verification, this status code is no longer returned. It previously indicated that the IBAN did not belong to a SEPAmail DIAMOND member payment service provider. Clients still checking for this code should migrate to the equivalent VOP Scheme status.
`BALV_1108`	Issue with the extracted IBAN	The IBAN is structurally invalid: it does not satisfy the IBAN checksum. It was most likely misread from the document by the optical recognition.

STATUS: failed

Code	Type	Description
`BALV_1003`	Issue with the bank account	No answer could be obtained for this account. Either the bank does not know it, or the bank was temporarily unreachable. Because a bank outage is transient, retry the verification later before treating the account as invalid.
`BALV_1100`	Issue with the bank account	The bank account cannot receive funds. The payment against it was pre-validated as one that will fail, or could not be confirmed.
`BALV_1101`	Issue with the bank account	Bank account is closed. The account is in the bank's database, but it was closed.
`BALV_1103`	Bank account doesn't match expected owner (no match)	The declared name does not match the account holder. Unlike a close match, this is not a spelling variation: verify the account details before retrying. When the expected holder is a legal person, the bank may still return the company name it holds in `data.account_holder`.
`BALV_1104`	Issue with the bank account	Bank account is out of scope. The account is not eligible for Verification of Payee.
`BALV_1200`	Issue with the bank account type	The expected holder type differs (natural person / legal person).
`BALV_1330`	Bank account doesn't exactly match expected owner (close match)	The declared name does not exactly match the account holder's identity. Check and correct the spelling, then retry the verification. When the bank discloses it, the name it holds is returned in `data.account_holder`.