What is verification of payee (vop)? A complete merchant guide

• Learn how VoP verifies payee names before SEPA payments are processed.
• Understand match, close match, and no match outcomes and their liability implications.
• Discover practical steps merchants can take to prepare for VoP compliance and reduce payment friction.

Verification of Payee (VoP) is a name checking mechanism that sits between a payer hitting send and their money actually leaving the account. As of October 2025, VoP is mandatory for payment service providers (PSPs) across the euro area to reduce both fraudulent bank transfers and basic typos that result in money being sent to the wrong place.

If you’re a merchant moving money in Europe, VoP affects how you send and receive payments. This article covers everything you need to know about what VoP is and how it works, the matching outcomes, how it fits into wider payment regulations, and practical steps to take to ensure your payments go through under Verification of Payee. 
 

VoP was developed by the European Payments Council (EPC), and it became mandatory for eurozone payment service providers on October 9, 2025. The ultimate goal is to reduce fraud and misdirected payments by matching the payee name prior to fund transfer.

VoP requirements apply to all SEPA Credit Transfers, including Instant Credit Transfers. In some markets, you may hear Verification of Payee be referred to as bank account verification (BAV) or IBAN name check.

While VoP is currently only mandatory for SEPA countries within the eurozone, by July 2027, all non-Euro EU member states, such as Hungary, Denmark, and Poland, are expected to comply with VoP regulations. Other SEPA countries outside of the EU, like Iceland, Switzerland, and Norway, may also adopt VoP standards. However, timing and regulations depend on local law and whether PSPs in these locations adhere to the EPC VoP scheme. 
How does VoP work?
VoP is a relatively simple process and normally looks something like this:
 

1. The payer initiates a SEPA transfer through their PSP (the requesting PSP).
2. Requesting PSP queries the payee’s PSP (the responding PSP) via SEPA infrastructure or a Routing and Verification Mechanism (RVM).
3. Responding PSP checks the payee’s name and IBAN against its customer records.
4. Response returned to the payer in real time.

All of this happens in about one second and is free to the payer.

One thing to keep in mind is that VoP doesn’t block payments by itself. It checks the details and returns a result to a payer in real time. Acting on that result, whether it’s continuing, pausing, or cancelling the transaction, is up to the payer or the PSP’s risk rules. 
VoP matching outcomes
When VoP is initiated, there are three possible outcomes:
 

1. Match – The name and IBAN fully align. The payer can proceed with confidence since the payee's name is displayed back. Payee names are only displayed in cases of a match or a close match. 
2. Close Match – Names are similar but not identical. The payer is shown the close match and (depending on the PSP's rules) the suggested correct name. Close matches can happen due to typos, legal name vs. trading name mismatch, initials vs. full names, title prefixes, etc. 
3. No Match – The names don’t align. In these cases, the payer is not shown the stored name. The payer can still proceed with the transaction, but liability shifts.

It’s also possible to receive an outcome along the lines of “unable to verify”, which means the system couldn’t complete the check due to being offline, having no record, or other related reasons.

Before any check starts, the responding PSP (the payee’s bank) cleans up the name it was sent, following its own checking rules. Doing this helps the matching process so that a stray capital letter or rogue accent doesn’t sink a name that’s otherwise a perfect match.

Clean up steps may include ignoring the case, flattening accents, stripping punctuation and non-character symbols, and removing titles like Mr. or Mrs. Once the name is normalised, the matching process can run. 
VoP under PSD3 and PSR
PSD3 and Payment Services Regulation (PSR) are the EU’s next overhaul of payment services, and they’re what take VoP beyond SEPA. PSD3 is the updated directive, while the PSR is what carries VoP forward. Essentially, the PSR applies SEPA’s VoP rules to all EU credit transfers, regardless of currency or scheme. It also swaps out IBAN for ‘unique identifier’, so the same name check runs even when an IBAN isn’t involved.

VoP exists to close a gap in how SEPA previously worked. Before VoP, an IBAN told a bank which account to credit but said nothing about who owned it, making these transfers easy to exploit for invoice fraud or impersonation scams. The EPC’s first version of VoP was voluntary, but the Instant Payments Regulation (IPR) amended SEPA and made VoP mandatory for all euro credit transfers. The PSR carries this forward and pushes the same name check across all of the EU.

The PSR also changes who’s liable when VoP is involved. If a PSP skips the check or doesn’t catch a mismatch and the payment goes wrong, the payer’s PSP is responsible for the refund. If the fault lies with the payee’s PSP, liability shifts to them. But if you enter the wrong details yourself and authorise the payment anyway, you’ll be on the hook for the refund.

The proposed PSR extends name matching beyond instant payments to all credit transfers, not just SEPA. This will significantly expand the scope of VoP and make it a permanent element of European payment flows rather than a niche scheme. 
VoP vs. UK Confirmation of Payee
Both Verification of Payee and Confirmation of Payee (CoP) exist to check the name a payer enters against the name on the receiving account before any money moves. Both schemes were implemented to fight authorised push payment fraud and misdirected payments, but the difference is in where they run, who governs them, and what identifier they check against.

Confirmation of Payee is the UK’s version, which was launched in 2020 and is owned and governed by Pay.UK. Through this scheme, there’s no IBAN involved, but there are checks against a sort code and account number for domestic UK transfers. Because Confirmation of Payee came first, it’s effectively the model the EU learned from and operates in a similar way by returning matching outcomes. Like VoP, CoP does not block payments on its own, but rather returns a result and leaves the decision (and liability) up to the payer or PSP.

On the other hand, verification of Payee is the SEPA/EU version. It’s governed by the European Payments Council and checks against the IBAN. While CoP is specifically for the UK, VoP is designed to work across all SEPA participants. 
What VoP means for merchants
If you’re a merchant operating in SEPA, VoP changes (or will eventually change) the process for making payments or getting paid yourself. Several actions can be taken preemptively to ensure payments continue to run smoothly, both on the merchant and customer side. 

When you’re getting paid
Your business name now shows up on every payer’s VoP check. So when a customer sends you money, their bank compares the name they typed against the name your bank holds for your account.

If you trade as ‘XYZ’ but your bank has you listed as ‘XYZ Payment Services Limited,’ every payer gets a close match instead of a clean one. At checkout, this might be a small red flag for some users, and in pay-by-bank flows where the customer is moving money straight from their account, a close match can be enough to make someone hesitate or drop off.

Merchant Action: Audit the name your bank holds against your trading name in every market you operate in. Either reconcile them, or accept that close matches are your normal and plan around it. It’s also worth preparing your support team for questions about why your name came back looking different from what people expected, so they know the answer ahead of time. 

When you’re the one paying
Paying suppliers, issuing refunds, running payouts, processing payroll, and beyond may now use VoP on the sending side. Your finance teams will start seeing close matches in volume because supplier records rarely line up perfectly with the names used in banking.

Merchant Action: Clean up your supplier master data so names match exactly what the bank holds wherever you can. Create a documented process for handling close matches and no matches before a queue builds up. 

How to prepare for VoP as a merchant
On the merchant side, there are specific actions that can be taken in advance to make sure there are no issues with VoP. Consider the following:

• Audit your bank-held legal name against your trading name to reduce ‘close match’ outcomes.
• Update customer-facing brand assets to match what banks return, or accept close matches and tell customers what to expect for transfers.
• Clean your supplier master data and match supplier names to their banking name whenever possible.
• Document a close match and no match handling policy for your finance teams to avoid a liability shift under VoP.
• Check how your PSP has integrated VoP to ensure it aligns with your processes.
• Track your VoP response rates. A high close match rate normally means messy data on your side rather than a customer problem. 
   

Frequently asked questions about Verification of Payee

Is Verification of Payee mandatory?
Verification of Payee is mandatory for payment service providers in the euro area under the Instant Payments Regulation. EU member states that don’t use the euro are expected to follow by July 2027.

How do I verify a payee?
You don’t verify a payee manually – this is handled by the PSP who runs a check for you as soon as you enter the payee’s name and account details. The PSP will compare these against the name the receiving bank has and return the result in about one second. All you have to do is act on what comes back, whether it’s a match, a close match, or no match. But remember that if you proceed with a transaction after a no match result, you’re the one liable if there’s an issue with the payment.

Can a payment go through after a no match VoP response?
A payment can still go through after a no match VoP response because the process doesn’t block anything on its own. You can still authorise a no match payment, but the liability shifts to you if you proceed and the payment goes wrong. 

Does VoP apply outside the eurozone?
VoP is expanding outside the eurozone with EU states expected to comply by July 2027. Non-EU SEPA countries like Switzerland, Norway, and Iceland can adopt VoP standards too, but it depends on local laws and regulations. 

What’s the difference between VoP and CoP?
The difference between VoP and CoP comes down to location and what each checks. VoP is the SEPA/EU scheme, governed by the European Payments Council, that matches against the IBAN. CoP is the UK scheme governed by Pay.UK that matches against the sort code and account number rather than the IBAN. They do the same job (name checking before a payment), just within two different systems.