IBAN verification: the 5 criteria of a solution that really verifies

In short: choosing an IBAN verification solution comes down to five criteria: the actual level of verification (format, existence, account holder), neobank coverage via VOP, B2B capability (matching the IBAN to the company number), the absence of false positives, and integration at the right moment in the journey. A correctly formatted IBAN proves neither that the account exists nor that it belongs to the right beneficiary.

Since October 2025, VOP (Verification of Payee) has been mandatory in the SEPA area for credit transfers, and bank detail fraud remains one of the most costly for companies: a fake bank details document slipped into a supplier or HR file is enough to divert tens of thousands of euros. Here is how to choose a tool that truly verifies.

1. The level of verification: format, existence, or account holder?

There are three levels of verification, and many tools stop at the first. The format check (ISO 13616 standard, check digits) validates the syntax and nothing else: a fraudulent IBAN almost always has a perfect format. The existence check confirms that the account is open and active. The account holder check, the only one that blocks fraud, verifies with the bank that the account actually belongs to the applicant: name, type of holder (individual/business), and account status.

Question to ask: "Do you verify the name/IBAN match with the bank, or only the format and existence?"

2. Coverage: traditional banks AND neobanks

VOP, mandatory across the SEPA area since October 2025, is the European standard covering banks and neobanks alike, including N26, Qonto, Revolut and others. Open banking can complement the setup where the journey allows it. Some markets also have national interbank verification networks, and a good solution plugs into them where they exist. A serious solution combines these channels and tells you honestly what remains ineligible.

Coverage also has a second, often forgotten side: availability. A solution that relies on a single verification source stops working the moment that source goes down, and your payments stop with it. Robust solutions rely on several aggregators and switch automatically from one to another in case of an outage, without interrupting your flows.

Questions to ask: "What is your actual coverage of neobanks, and what happens when an IBAN is not eligible?" And: "What happens when your verification source is down?"

3. B2B: linking the IBAN to the company

Verifying that a business IBAN belongs to the company (to its company registration number: the SIREN in France, the Companies House number in the UK, the Handelsregister number in Germany), not merely to a similar-sounding name, is the decisive check against supplier transfer fraud and shell companies with a real bank account. Also check how legitimate edge cases are handled: a sole trader without a dedicated business account will trigger an "incorrect holder type" that needs to be interpreted, not rejected.

Question to ask: "Can you confirm that an IBAN belongs to a given company number, and how do you handle sole traders?"

4. Zero false positives: proof, not a score

IBAN verification is the only anti-fraud check that can be binary: the bank confirms or denies, there is no statistical grey area. That is its strength, provided the answer really does come from the bank. Beware of interpretation in both directions: a matching IBAN does not clear a file (much fraud uses a perfectly valid account), and a KO deserves a second look (a recently closed account may simply be a customer who changed banks).

Question to ask: "Does your answer come directly from the account-holding bank, and what is your false positive rate?"

5. Integration at the right moment in the journey

The IBAN check must come before the expensive checks (no point paying for document analysis of bank details whose IBAN is already KO) and be repeated at critical moments: the first transfer, a change in a supplier's or employee's bank details, an insurance claim payout. Also check the practical cases: several IBANs per file (co-borrowers), a history that can be consulted without triggering a new billable analysis.

Question to ask: "How do you handle a change in a supplier's bank details: automatic re-check or manual action?"

The decision grid at a glance

• Level of verification: the minimum, format (ISO 13616); the differentiator, account holder confirmed by the bank.
• Coverage: the minimum, traditional banks; the differentiator, + neobanks via VOP.
• B2B: the minimum, similar name; the differentiator, match to the company number.
• Reliability: the minimum, probabilistic score; the differentiator, binary answer, zero false positives.
• Journey: the minimum, one-off check; the differentiator, before expensive checks + re-check at critical moments.

How Meelo meets these 5 criteria

Meelo's IBAN Analysis verifies the account holder via VOP across the SEPA area, neobanks included, plugs into national interbank networks where they exist, and is complemented by open banking where the journey allows it: account existence and activity, name match, holder type, link to the company number in B2B. The verification relies on several aggregators with automatic failover between them in case of an outage: service continuity is guaranteed, unlike single-source solutions that stop when their source goes down. The answer is binary, match or no match, with no false positives, returned in a few seconds, with up to 3 IBANs per file (co-borrowers) and a consultable history. And since the IBAN check rarely lives alone, the same API covers document verification of bank details, KYC of the applicant and KYB of the company. To test the check on your own flows, you can schedule a demo.

FAQ

How do you verify an IBAN?

At three levels: the format (ISO 13616 standard), the actual existence of the account, and above all the match between the IBAN and its holder (VOP), confirmed by the bank. Only the third level protects against fraud.

How can you find out who an IBAN belongs to?

An IBAN only publicly reveals the country and the bank, never the holder. To confirm that it belongs to a given person or company, you need an account holder verification (VOP) with the account-holding bank.

Is VOP mandatory?

Yes: since October 2025, Verification of Payee has been mandatory in the SEPA area for credit transfers. The bank must verify the match between the beneficiary's name and the IBAN before execution.

Does a matching IBAN guarantee that the file is safe?

No. Much fraud presents a perfectly valid IBAN in the fraudster's own name. The IBAN match is one building block, to be cross-referenced with identity verification, document analysis and the fraud score.

When should an IBAN be re-verified?

At every critical moment: the first transfer, a change in a supplier's or employee's bank details, an insurance claim payout. Most transfer fraud goes through a change of bank details that was never re-checked.

‍