One of the reasons Verification of Payee works so well is that it never leaves the payer guessing. Instead of a yes/no, it returns one of four clear outcomes, each mapped to a standard SEPA scheme code. Here's how to read them.
Match
The name you entered matches the account holder of the IBAN. This is the expected, low-risk result: the money is going where you intend. The response also includes the responding bank's BIC, confirming which institution answered.
Close match
The name is almost right. This is common and usually legitimate — a missing middle name, a legal name versus a trading name, or a transliteration. The service can return the verified name as a suggestion so you confirm or correct without guessing.
A close match is a prompt, not a failure
Treat it as a chance to double-check, not a reason to abandon the payment. Showing the suggested verified name turns a moment of doubt into a quick confirmation.
No match
The name does not belong to this IBAN. For an expected payee this is a strong signal to stop and re-check — and it is the classic red flag for APP fraud and misdirected payments. The payment is not blocked automatically; you decide.
Not available
The payee's bank could not verify right now — for example, the institution isn't reachable for VoP at that moment. It's neither good nor bad news; treat a new, unverifiable payee with a little extra caution.
Across all four, VoP stays informative: it advises, but never seizes control of the payment. RoxPay returns these same standardised outcomes, with scheme codes and the responding BIC, via API and dashboard.