An IBAN name check tells you whether the name you typed matches the name registered on the account behind an IBAN. It is answered by the bank that holds the account, not by a website, and in the EU it runs as Verification of Payee (VoP) on the SEPA scheme. It does not tell you the holder's name unless the names are close but not identical, and it does not tell you whether the payee is trustworthy.
That is the short answer. The rest of this article is about the three different things people call an IBAN name check, because mixing them up is how a green tick gets mistaken for a guarantee.
What an IBAN name check actually checks
Three separate layers get bundled under the same phrase. They use different inputs, they are performed by different parties, and they prove different things.
- IBAN structure and checksum validation. A validator reads the IBAN itself: the country code, the length for that country, the two check digits and the bank identifier. It confirms the number is well formed and routable. It never contacts a bank.
- Account-holder name lookup. Someone asks the bank that holds the account what name is registered on it. This is not a public service: account holder data is personal data, and only the holding bank can answer.
- The regulated name-vs-IBAN comparison. Your payment service provider (PSP) sends the name you supplied and the IBAN to the payee's PSP, which compares the two against its own records and returns a standardised outcome. In the EU this is Verification of Payee, mandated by the Instant Payments Regulation.
Only the third layer compares a claimed name against the bank's record. The first layer cannot see a name at all, and the second is not something you can do yourself.
A validator confirms format, not ownership
A fraudster's IBAN passes every format and checksum test, because it is a real, well-formed account number. Validation tells you the number could exist. It cannot tell you who it belongs to.
Why the top 'IBAN checker' results don't answer the question
Most pages ranking for 'IBAN name check' are IBAN validators or IBAN calculators. They are useful tools, and they are honest about what they do if you read them closely - but the search query and the tool do not match. A validator takes an IBAN as input and returns a verdict on its structure. It has no connection to the account, no access to the holder's name, and no way to compare anything.
So a green tick from a validator means: this string is a plausible IBAN. It does not mean the account exists, that it is open, that it belongs to the company on the invoice, or that the person who sent you the number is who they say they are. If you want the background on what an IBAN is made of, the site's guide to IBAN structure covers it; the point here is narrower - structure is not ownership.
IBAN validity vs account-holder name vs VoP: a comparison
The table below is the shortest way to keep the three apart. Read it by column: what goes in, what comes out, who can do it, and what it proves.
- IBAN validation - input: an IBAN. Output: valid or invalid, plus the bank identifier. Who: anyone, with a free tool or a few lines of code. Proves: the number is well formed and routable. Does not prove: that the account exists or who owns it.
- Account-holder lookup - input: an IBAN. Output: the registered name. Who: only the bank that holds the account, and only in defined circumstances. Proves: who the account belongs to. Not available to the public.
- VoP name check - input: a claimed name plus an IBAN. Output: match, close match, no match or not available. Who: PSPs on the SEPA scheme, and businesses through a VoP API. Proves: whether the name you supplied agrees with the bank's record.
The VoP name check is the only one of the three that compares a claimed name against the bank's record. That is why it is the one that catches a swapped account number on an invoice.
How the VoP name check works in practice
The check is a conversation between two banks, not a lookup in a shared register. Your PSP is the requesting PSP; the bank that holds the destination account is the responding PSP.
- 1 You enter the payee name and IBAN - in your banking app, your ERP or a payment file.
- 2 Your PSP sends a verification request carrying the claimed name and the IBAN.
- 3 The scheme routes the request to the PSP that holds the account.
- 4 That PSP compares the claimed name with the name on its own records, using the scheme's name-matching rules.
- 5 A standardised outcome comes back to your PSP, which shows it to you before you confirm.
Only the name comparison travels. The amount, your balance and the payee's transaction history are not part of the message. If you want the mechanics of the request and response in detail, the worked example on this site walks through a full exchange; here the point is who is allowed to answer.
Reading the result: match, close match, no match
VoP never returns a vague answer. Every check resolves to one of four outcomes, and each one calls for a different reaction.
- Match - the name agrees with the account holder. Proceed with normal confidence.
- Close match - the names are similar but not identical: a missing middle name, initials instead of a first name, a trading name against a registered name. The verified name comes back so you can confirm or correct it. It is a prompt, not a failure - and not a guarantee either, because the scheme is telling you the names are close, not that they are the same.
- No match - the name does not belong to that account. For a payee you expected, this is a stop signal. Do not override it out of habit because the payment is due today.
- Not available - the payee's bank could not answer at that moment. Neither good nor bad news. Treat a new, unverifiable payee with extra care.
The check is advisory: it warns you, it does not block the payment. That is deliberate, because the decision to send stays with you - and it is also why a no match only protects you if you actually act on it.
Who can run an IBAN name check, and who cannot
This is the part most pages skip, and it explains why no website can look up an arbitrary account holder's name.
- Banks and PSPs run it as part of the payment flow. Euro-area PSPs have had to offer VoP on euro credit transfers since 9 October 2025, and PSPs in non-euro EEA states follow by 9 July 2027. It must be offered to payers free of charge.
- Businesses run it through a VoP API or a provider's dashboard, typically on a whole payment file before release and again whenever a supplier's bank details change.
- An individual payer cannot run it independently. You rely on the name check your own bank or payment app shows you when you set up or pay a payee - which is the same check, just delivered inside your banking app.
There is no public directory of account holders, and that is by design: account holder data is personal data under GDPR, and only the holding bank can confirm it. A site that claims to reveal holder names is guessing, recycling leaked data, or selling something else. If you want the step-by-step version of what an individual can do, the guide to checking a bank account holder name covers it.
What an IBAN name check does not prove
A match is a strong signal about one thing only: the account belongs to the party you named. It is not a fraud clearance, and treating it as one is how people get hurt.
- It does not prove the payee is honest. A genuine account can belong to a genuine company that will not deliver what you paid for.
- It does not prove the invoice is genuine. A fraudster who has taken over a supplier's mailbox can send you a real invoice with a real, matching account - just not the supplier's.
- It does not prove the account is not a mule account. Money mule accounts are real accounts in real names, opened or rented by people who then pass the funds on.
- It does not prove the person instructing you is who they claim to be. That is a separate control: call back on a number you already had.
What it does remove is the account-detail risk: the mistyped digit, the out-of-date account number, the quietly swapped IBAN. That is a large share of misdirected payments, and it is worth having. It is just not the whole of fraud prevention.
Two controls, not one
A name check answers 'is this the right account?'. A callback on a known number answers 'is this the right instruction?'. Invoice redirection needs both, because the fraud usually changes the instruction and the account together.
Checklist before you send a payment
- 1 Validate the IBAN format first. It is free, instant, and it catches typos before anything else runs.
- 2 Run the name check wherever it is available - in your banking app, or through a VoP API if you pay in bulk.
- 3 Enter the name exactly as it appears on the invoice, contract or statement, not as you remember it.
- 4 On a close match, accept the verified name the bank returns rather than overriding it.
- 5 On a no match, stop. Confirm the details through an independent channel - a number you already had, never one from the message that carried the new IBAN.
- 6 On not available, treat a first-time payee with extra care: a small test payment or an independent confirmation.
- 7 Keep the result with the payment record, so you can show what you checked and when.
RoxPay delivers Verification of Payee on the SEPA scheme through one REST API and a dashboard, returning the standardised outcomes - match, close match, no match and not available - in well under a second, with the verified name on a close match, for a single payment or a whole payment file.