IBAN Name Mismatch: Why Your Payment Was Rejected and How to Fix It
An IBAN name mismatch is a common reason a payment gets rejected on Wise or Revolut: you typed the IBAN carefully, hit send, and instead of a confirmation you got a warning that the name does not match the account. Now the transfer is stuck, the recipient is asking where their money is, and you are not sure if you made a mistake or the app is just being paranoid.
An IBAN name mismatch means the receiving bank told your provider that the name you entered does not match the name on file for that account. It is not a random block: since 9 October 2025, EU banks must run this check (Verification of Payee) on every SEPA transfer, and the UK’s biggest banking groups have run an equivalent check (Confirmation of Payee) since 2020. You can usually still send the payment, but only after you confirm the recipient’s exact registered name.
What “no match” actually means
Wise, which publishes its own rules on this, breaks the result into three outcomes:
Match safe
The name you entered matches the account holder’s name exactly. Wise’s own guidance: “the name completely matches the account holder’s name, so you can safely send your payment.”
Close match check it
The name is similar but not exact, the kind of gap between “Mick Jager” and “Mick Jagger.” A missing middle name, a trading name instead of a legal name, or a typo will land here.
No match stop and verify
The receiving bank says the name does not belong to that account at all. This is the result that should make you stop and call the recipient before doing anything else.
Proceeding after a “no match” does not just risk your money. Wise states it directly: “if you choose to proceed with the transfer after receiving the No match warning, you’ll be liable for the transfer if it’s fraudulent.” The check exists to protect you, and choosing to override it shifts that protection back onto you.
Why an IBAN name mismatch gets your payment rejected even when the IBAN itself is correct
Two separate rules are running here, and mixing them up is the most common source of confusion.
In the EU, the Instant Payments Regulation (2024/886) requires providers to offer a free Verification of Payee check before authorising a credit transfer, comparing the account identifier against the payee’s name, per the European Central Bank. That requirement became mandatory on 9 October 2025, and it applies to standard SEPA transfers, not only instant ones.
In the UK, Confirmation of Payee is older and runs on a different rail: it checks name, sort code and account number together, not an IBAN. The Payment Systems Regulator first directed the six largest banking groups to build it in 2019, live by March 2020, then extended the requirement in stages, “Group 1” providers by October 2023 and roughly 400 more firms (“Group 2”) by October 2024, pushing coverage toward nearly all Faster Payments transactions.
Neither system blocks the payment outright; both hand the decision back to you with a warning. Banks would rather flag a transfer than silently reject a legitimate one, like rent paid to a landlord’s company account under a trading name.
What to do right now
- ✓
Stop before resending. A second attempt with the same wrong name will fail the same way.
- ✓
Ask the recipient for their exact registered account name, not a trading name or nickname. Business accounts are often registered under a legal entity name that looks nothing like the brand.
- ✓
Re-enter the name character for character, including middle names and accented letters, a frequent cause of “close match” results.
- ✓
On “close match,” proceed only if you are confident in the recipient; treat repeated close matches on the same person as a reason to call them, not just click through.
- ✓
On “no match,” do not send until you confirm the details directly with the recipient. This is exactly the scenario the check was built to catch.
If a transfer stays stuck longer than a routing mismatch should, the friction can escalate into a wider account review rather than a simple resend, a different problem covered in what to do when your Revolut account gets frozen. If name-check friction keeps happening across providers, it may be worth comparing options through which Revolut alternatives actually hold up under scrutiny, not just their fees.
FAQ
Is Verification of Payee the same as Confirmation of Payee?+–
No. VoP covers SEPA credit transfers across the EU/EEA, mandatory since 9 October 2025. CoP covers UK Faster Payments and CHAPS, mandatory for major banks since 2020. A transfer between a UK account and an EU account can trigger either check depending on which leg fails.
Can I still send the money after a “no match” warning?+–
Usually yes, the payment is not automatically blocked. But Wise, for example, states plainly that you become liable for the transfer if you proceed and it turns out to be fraudulent, so only continue once you have verified the recipient’s details directly, not through the same channel where you received the payment request.
Why did a payment I have sent before suddenly get flagged?+–
The recipient’s registered name may have changed, or your provider may have only just switched on the check for SEPA transfers after the October 2025 deadline. A payment that worked in September can get flagged in November purely because the check itself is new.
Written by Daniel Hart, who covers neobanks, account freezes and cross-border banking for neobankfit. Based on regulator and provider documentation: the European Central Bank’s Instant Payments Regulation summary, the UK Payment Systems Regulator’s Confirmation of Payee page, and Wise’s published Verification of Payee guidance.
This article is general information, not legal or financial advice. Rules, deadlines and protection limits change and depend on your country, account and provider entity. For your situation, check current terms and consider a qualified adviser.
