Verification of Payee (VoP): The SEPA Name Check Explained
From October 2025, EU banks must check a payee’s name matches their IBAN before each transfer. What VoP is, the four results, the deadlines, and how to prepare.
What is Verification of Payee (VoP)?
Verification of Payee (VoP) is a fraud-prevention check in which the payer’s bank confirms that the beneficiary’s name matches the IBAN before a credit transfer is executed. Introduced by the EU Instant Payments Regulation, it has been mandatory for euro-area payment service providers since 9 October 2025 and is offered to the payer free of charge. Every check returns one of four results: match, close match, no match, or verification not possible.
Validate your file right now
Free, instant and 100% in your browser - no file is ever uploaded.
What is Verification of Payee?
Verification of Payee (VoP), sometimes called “Confirmation of Payee”, is a check performed before a SEPA credit transfer is executed. The payer’s payment service provider (PSP) compares the beneficiary name entered by the payer with the name actually attached to the account behind the IBAN, and tells the payer whether they match.
The goal is to fight authorised push payment (APP) fraud and simple mistakes: forged supplier bank details, CEO fraud, or a mistyped IBAN. If the name does not match, the payer is warned before the money leaves the account.
VoP applies to every euro credit transfer — both standard SEPA Credit Transfers (SCT) and SEPA Instant Credit Transfers (SCT Inst) — not only instant payments. It runs in real time, within seconds, the moment the payment is initiated.
The four possible VoP results
A VoP check always returns one of four standardised outcomes. Knowing them helps you interpret the warning your bank shows you — or the response to a bulk file you submit.
Match
The name provided matches the account holder’s registered name. The payment proceeds normally.
Close match
The name is almost identical (an abbreviation, a missing legal form, a minor typo). The payer is shown the actual registered name and decides whether to continue.
No match
The name does not correspond to the IBAN. The payer receives a clear warning; they may still proceed, but they assume the risk and liability.
Verification not possible
The payee’s bank could not answer (account unreachable, service temporarily down, or IBAN outside the scheme). No confirmation is given.
The legal mandate and key dates
VoP is required by the EU Instant Payments Regulation (Regulation (EU) 2024/886), which amends the SEPA Regulation. The rule is deliberately broad: it covers all credit transfers, so banks cannot limit the check to instant payments only.
Euro-area payment service providers have had to offer Verification of Payee since 9 October 2025. Providers in non-euro-area EU member states have until 9 July 2027. Crucially, the check must be provided to the payer free of charge.
To make VoP work across thousands of banks, the European Payments Council (EPC) runs the VoP scheme — a common rulebook and a set of Routing and Verification Mechanisms (RVMs) so any payer’s PSP can query any payee’s PSP in a standard way.
How to prepare your SEPA files for VoP
If you send bulk payments (payroll, supplier runs) via a pain.001 file, a wrong or approximate beneficiary name now creates friction — close-match prompts or outright warnings that can delay a whole batch. These four steps keep your files clean, and you can check every one of them locally, before submission, without sending any data to a server.
- 1
Use the exact registered account name
Enter the beneficiary’s legal or registered account-holder name, not a trade name, brand or abbreviation. “ACME Trading Ltd” will close-match or fail against an account registered as “ACME Ltd”.
- 2
Respect the SEPA character set and length limits
Names are limited to 70 characters and the SEPA Latin character set. Truncated or transliterated names (accents dropped, text cut off) raise the risk of a close match instead of a clean match.
- 3
Validate the IBAN before you send
A structurally wrong IBAN (failed mod-97 check, wrong length for the country) can make verification impossible. Check each IBAN’s format and check digits first.
- 4
Validate the whole pain.001 file
Before submission, validate the file’s structure, control sums, names and IBANs. ValidateFin does this 100% in your browser — no beneficiary data ever leaves your machine.
Validate your SEPA file before it hits VoP
ValidateFin checks your pain.001 / pain.008 structure, IBANs, BICs, character set and name lengths entirely in your browser. Catch the issues that trigger VoP warnings — before you send.
Open the SEPA validatorFrequently Asked Questions
Is Verification of Payee mandatory?
Yes. Under the EU Instant Payments Regulation, euro-area payment service providers have had to offer Verification of Payee since 9 October 2025. Providers in non-euro-area member states must comply by 9 July 2027.
Does VoP apply only to instant payments?
No. Although it was introduced by the Instant Payments Regulation, VoP applies to all SEPA credit transfers — both standard (SCT) and instant (SCT Inst).
Does Verification of Payee cost anything?
No. The regulation requires that VoP be offered to the payer free of charge. Banks cannot bill the payer for the name check.
What happens if the name does not match the IBAN?
The payer gets a clear “no match” warning before confirming. They can still choose to proceed, but they then accept the risk and lose some fraud-related protections.
Can I still send the payment after a no-match?
Yes. VoP is advisory, not blocking. The payer keeps control and can proceed — but doing so against a no-match shifts liability towards the payer.
How does VoP handle company names and abbreviations?
Minor differences (legal form, abbreviations, small typos) usually return a “close match”, where the payer is shown the real registered name and decides. Exact registered names avoid this friction.
Can ValidateFin perform a real VoP check?
No — and no honest client-side tool can. A real VoP check queries the beneficiary bank’s systems, which requires PSP access and a network call. ValidateFin instead validates your file locally (IBAN, name length, character set, structure) so it is ready for VoP, without transmitting any data.
How can I reduce VoP rejections on bulk payment files?
Use exact registered payee names, respect the 70-character SEPA name limit and character set, validate every IBAN, and validate the full pain.001 file before submission. These checks can all be done locally beforehand.