How accurate is Verification of Payee?
VoP name matching is designed to catch wrong accounts without blocking genuine payments. Here's how the matching works, what affects accuracy, and why a 'close match' is a feature, not a bug.
How VoP matching works
Verification of Payee compares the name a payer entered against the registered account holder and returns one of four standardised outcomes: match, close match, no match, or verification not possible. It's not a simple yes/no — it's graded, so payers get useful nuance.
A close match handles the everyday reality of names: a missing middle name, initials vs full names, a legal name vs a trading name, accents, or word order. Rather than failing a legitimate payment, the scheme can return the verified name as a suggestion so the payer can confirm.
What affects accuracy
Match quality depends on data and naming conventions on both sides.
Legal vs trading name
Companies often pay under a brand name that differs from the registered legal name — a classic close match.
Formatting & accents
Initials, punctuation, accents and word order are normalised so trivial differences don't cause a false no match.
Joint & business accounts
Multiple holders or organisation identifiers (VAT/tax code) are factored in for a more accurate result.
Source data quality
Accuracy ultimately depends on the responding bank's account-name data being correct and up to date.
A 'close match' is doing its job
Close match exists precisely so VoP is accurate in the real world: it flags small differences without blocking genuine payments, keeping false negatives low while still catching wrong accounts.
FAQ
VoP uses standardised, tolerant name matching that returns match, close match, no match or not possible. It's designed to catch genuinely wrong accounts while minimising false mismatches on legitimate payments — accuracy ultimately depends on the source account-name data too.
Because the name is almost right — for example a missing middle name, initials, or a legal vs trading name. The service returns the verified name as a suggestion so you can confirm or correct without guessing.
It can, if the name entered differs substantially from the registered holder or the source data is outdated. Tolerant matching and the close-match outcome are designed to keep false no-match results low.
RoxPay applies scheme-compliant normalisation (accents, initials, word order, legal vs trading names) and uses organisation identifiers for legal persons, returning a clear graded outcome with a suggested name where relevant.
See VoP matching in action
Try the sandbox and test real names and IBANs against the four outcomes.