Follow bank account lookup verification status

On this page, you will find comprehensive information about the bank account lookup verification lifecycle.

Verification statuses

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

StatusDescriptionRecommended action
pendingThe bank account lookup verification has been initiated.Wait for the status to change.
inconclusiveThe verification could not be completed (e.g. the SEPAmail DIAMOND service could not be reached).
For more details, refer to the status codes section below.
Initiate a new bank account lookup verification.
verifiedThe IBAN have been successfully verified against the holder's details provided.Proceed with accepting the request that required a bank account's holder's details verification.
failedThe bank account lookup 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 lookup 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.


STATUS: failed

CodeTypeDescription
BALV_1000Verification couldn’t happenSepamail DIAMOND could not process the request.
BALV_1101Issue with the bank accountBank account is closed. The PSP has the account in their database, but the account was closed in the past 14 months
BALV_1103Issue with the bank accountBank account is non-existent. The PSP doesn't have the account in their database, or the account was closed in the past 14 months
BALV_1104Issue with the bank accountBank account is out of scope. The account is not eligible for Sepamail DIAMOND verification
BALV_1200Issue with the bank account typeThe expected holder type differs (natural person / legal person).
BALV_1300Issue with the SIREN/SERETThe account does not match the provided SIREN/SIRET, possibly due to mergers, groups, or transfers.
BALV_1320Issue with the SIREN/SERETUnverifiable SIREN/SIRET — certain accounts (co-ownerships, associations) are ineligible.
BALV_1330Bank account doesn’t match expected ownerThe declared names (first name, last name) do not match the holder's identity. Check and correct spelling for individuals, then retry the verification.
BALV_1400Issue with companyThe company is not in business, thus the bank account check can't be done

📘

To avoid seeing BALV_1400 codes, it is recommended to make sure that company_number is the number of an active, registered company. This is a prerequisite to successfully validate that the bank account exists