Verification of Payee vs IBAN Validation: What Each Check Catches

Verification of Payee (VoP) and IBAN validation are two different fraud controls that are constantly confused because both run before a payment leaves. They answer separate questions. VoP asks whether the account behind an IBAN belongs to the named person or company, which only the receiving bank can answer. IBAN validation, and the account check digits layered on top of it, ask whether the account number itself is well-formed and routable, which can be checked instantly and for free. This guide draws the line precisely, shows which payment errors each layer catches, and explains why a free tool can do one of them honestly but not the other.

What does Verification of Payee actually check?

VoP is a name-matching check. The payer's bank sends the beneficiary IBAN and the name the payer typed to the beneficiary's bank, which compares it against the registered account holder name and returns match, close match, or no match. The decisive detail is where the answer comes from: only the bank that holds the account knows the name on it. VoP became mandatory for euro-area payment service providers on 9 October 2025 under the EU Instant Payments Regulation, it must be free to the payer, and participating banks reach each other through the European Payments Council's Directory Service. None of that infrastructure is open to a third party that does not hold accounts, so VoP cannot be replicated by an external validator. The UK runs an equivalent scheme, Confirmation of Payee, on the same principle.

What can IBAN validation catch without the bank?

A great deal, and all of it without any account-holder data. Structural validation confirms the country code, the country-specific length, the BBAN format, and the ISO 13616 MOD-97 check digits, then identifies the institution behind the bank code. On top of that, many countries embed a domestic account check digit that a validator can verify independently: the German Prüfziffer (96 calculation methods covering virtually every Bankleitzahl), the UK account modulus check published free by Pay.UK and VocaLink, the French and Italian RIB/CIN keys, and ISO 7064 checks used across much of Europe. Our engine also flags a UK bank-code/sort-code mismatch when the four-letter code and the sort code point to different banks. Together these catch the entire class of wrong account number errors: a transposed digit, a mistyped sort code, a number that cannot exist at that bank.

Which payment errors does each layer prevent?

• Typo in the account number or check digits — caught by IBAN validation and the national check digit, before the payment is ever sent.
• Sort code that belongs to a different bank — caught by mismatch detection and the UK modulus check.
• Impossible or non-existent account number — caught by the domestic check digit where the country defines one.
• Right account number, wrong owner — invoice fraud and authorised push payment scams, where the IBAN is perfectly valid but belongs to a criminal. This is the one class only VoP catches, because it is purely about the name.

Most of the value of a name check, in other words, is the part that overlaps with structural and check-digit validation; the unique part VoP adds is the name match itself.

Can a free tool do Verification of Payee?

No, and any tool that claims to is misleading you. Real name matching needs the account holder name, which is held only by the receiving bank and exposed only through the regulated VoP and Confirmation of Payee schemes. Joining those schemes requires being a regulated payment service provider or paying an aggregator per check. There is no open, free, third-party VoP, and a heuristic that guesses whether a name looks right would produce false reassurance, which is worse than no check at all. We hold a firm line on this: we will not display a name-match result we cannot actually perform. What we publish instead is every check that can be done correctly and for free, documented openly on our data methodology page.

How do the two work together in a payment workflow?

They are sequential, not competing. Validate IBAN structure and account check digits at data entry, ideally when a supplier is first onboarded and the details can still be corrected; the bulk IBAN checker runs an entire supplier file at once, and the single IBAN checker handles one at a time. A structurally invalid IBAN can never reach the VoP stage, because it cannot be routed to a beneficiary bank at all, so catching format and check-digit errors early removes noise from the later name check. Then, at send time, your bank performs VoP on the cleaned, valid IBANs. The free validation layer is the legitimate pre-payment control for the account-number class of errors; VoP is the bank-side control for the ownership class. For the regulatory background, see our guide to what Verification of Payee is and to PSD2 payee verification.

Sources & References

• Regulation (EU) 2024/886 — Instant Payments Regulation establishing the VoP mandate
• European Payments Council — Verification of Payee scheme
• EPC Directory Service — participant routing directory used by VoP
• Pay.UK — Confirmation of Payee, the UK name-check scheme
• VocaLink / Pay.UK — UK account modulus checking (free validation spec)

Last updated: June 2026