Verification of payee: the name check before a euro transfer leaves
Verification of payee, short VoP, is the check your bank runs on the payee name against the name on the account behind the IBAN, before the transfer goes out. The EU instant payments regulation made it compulsory across the SEPA area, and the European Payments Council operates it through the Verification of Payee scheme rulebook, which entered into force on October 5, 2025.
This page works below instant payments in Europe, which explains the ten-second transfer and names the check. Here the subject is the scheme itself: what the responding bank owes, what the payer actually sees, how the request is routed between thousands of institutions, and what a company has to change in its own payee files. If you run accounts payable or a payment product, the detail below is where your work sits.
What the check does and what it does not promise
VoP compares two strings. The payer types a name and an IBAN, the payer's payment service provider asks the account-holding provider whether that name belongs to that account, and the answer comes back before the payer confirms the payment. The check exists against two problems: a typo or an outdated IBAN that sends money to a stranger, and the fraud pattern where a criminal supplies a real IBAN under a false name.
What VoP does not do is judge whether the payee deserves the money. A fraudster who opens an account in their own name and tells the victim that name passes the check cleanly. The warning is also advisory: the payer may send the payment anyway after a mismatch, and most banks let them. That is why the check reduces exposure without closing it, which the pages on fraud prevention in Germany and APP fraud take further.
The EPC scheme rulebook and the responding provider's duties
The European Payments Council writes the Verification of Payee scheme rulebook, the same way it writes the rulebooks for credit transfers and direct debits. The rulebook splits the work between a requesting participant, acting for the payer, and a responding participant, which holds the payee account. Joining the scheme is what makes the two sides interoperable: without a common rulebook each bank pair would need a bilateral agreement.
The responding side carries the harder duty. It has to answer every properly formed request, within the seconds the payer is waiting, at every hour of every day, and it has to answer from the account data it actually holds. It may not use the request for anything else, and it may not charge the payer's provider in a way that breaks the regulation's pricing rule. An institution that cannot answer within the time limit returns the response that verification was not possible, which is itself a defined outcome.
What the payer sees: match, close match, no match
The scheme defines a small set of outcomes, and the payer's provider has to show them. A match means the name belongs to the account. A close match means the names differ in a way the responding side considers minor, a missing middle initial or a legal form left off a company name, and the responding side returns the name it holds so the payer can decide. A no match means the names do not correspond, and verification not possible means the question could not be answered at all.
The close match is the interesting one for a business. "Mueller Logistik" against "Müller Logistik GmbH" is the everyday case, and a payer who sees three close matches a day stops reading the warnings. A payment team that wants the check to work therefore has to care how its own name is registered at its own bank, because that is the string every customer will be compared against.
The API and the routing directory
A name check between any two of several thousand European institutions needs two things: a common message and a way to find the right counterparty. The scheme defines the request and response as an API call, so the question travels in seconds and not in a batch file. A payer's provider sends the IBAN and the name, the responding provider answers with one of the defined outcomes, and nothing is stored on the payer's side.
Finding the counterparty is the routing problem. The IBAN carries a bank identifier, but the institution that holds the account is not always the institution that answers VoP requests for it, because smaller banks route through a central institution or a service provider. A routing directory resolves that: it maps the identifier to the endpoint that answers. Any provider building VoP has to keep that directory current, or its requests go to an address that no longer answers.
The deadline under the instant payments regulation
Regulation (EU) 2024/886, the instant payments regulation, is what made the check compulsory instead of optional, and it sets two dates. Payment service providers in the euro area had to offer verification of payee from October 9, 2025, the same day the EPC rulebook took effect. Providers in EU member states outside the euro area have until July 9, 2027 for the euro transfers they handle, as the compliance timeline sets out. The check applies to ordinary SEPA credit transfers as well as instant ones, so a bank cannot escape it by routing a payment the slow way.
The duty binds every provider offering credit transfers, whatever its size: banks, payment institutions and e-money institutions alike, on the requesting side and on the responding side, and in corporate channels as well as retail ones. The regulation also sets the pricing rule that holds the whole thing together: a provider may not charge the payer for the check, and may not charge more for an instant transfer than for a standard one. Payments regulation in Germany covers how BaFin supervises the duty in the German market, and PSD3 and the PSR cover what the next legislative package adds on top.
Who is liable when the payer sends anyway
The warning changes the legal position, and it does not move the loss by itself. Where the provider ran the check and showed the payer a no match or a close match, and the payer confirmed the payment regardless, the provider's liability for the resulting loss is limited: the payer made an informed decision. Where the provider failed to offer the check at all, or failed to answer a request it received, the protection falls away.
Enforcement runs through the national competent authorities, not through a single European schedule of fines. Each member state sets the penalties in its own law for a provider that does not offer the check or does not respond to requests, which in Germany puts the question with BaFin. A provider that has not built the responding side ends up answering "verification not possible" to every counterparty, which is visible to every other bank in the SEPA area and is its own kind of pressure.
How the UK confirmation of payee differs
The UK built the same idea first and built it differently. Confirmation of payee, short CoP, started in 2020 on the UK rails and was extended by Pay.UK to a much wider set of institutions afterwards. It runs over the UK account numbering and sort codes, not over IBANs, and it is tied to the UK reimbursement regime for APP fraud, which gives a bank a direct financial reason to get the check right.
The practical differences matter to anyone running both markets. CoP distinguishes personal from business accounts in the request, which the SEPA scheme handles differently. The two schemes do not talk to each other, so a euro transfer to a UK account and a sterling transfer from one follow separate rules. Cross-border payments in Europe covers what else changes at that border.
What a merchant or corporate payer has to change
The work for a company sits in its master data, not in its payment software. Every payee record now gets compared against a bank's own register, so a supplier stored as "Schmidt AG" when the bank holds "Schmidt Aktiengesellschaft" produces a close match on every single payment run. A payment file of two thousand supplier payments turns into two thousand warnings nobody reads, which is worse than no check at all.
Three things fix that. Clean the payee names against the legal names the suppliers actually use, ask your bank how it exposes the outcome in your payment channel and whether a bulk file returns per-item results, and tell your own customers the exact name on your own account so their check passes. Corporate treasury covers the wider payment process this sits inside, and the SEPA direct debit covers the collections side, where the check does not apply.
What is verification of payee?
Verification of payee is a check that compares the payee name a payer entered with the name on the account behind the IBAN, before the credit transfer is sent. The payer's bank asks the payee's bank, the answer comes back in seconds as a match, a close match, a no match or a verification not possible, and the payer decides whether to continue.
Is verification of payee mandatory in the EU?
Yes. The instant payments regulation, Regulation (EU) 2024/886, obliges payment service providers in the SEPA area to offer the check, with the euro-area duty applying from October 2025 and non-euro-area providers following later. The EPC Verification of Payee scheme rulebook, in force since October 5, 2025, sets the rules both sides follow. A payer may still send a payment after a mismatch warning.
Can a bank charge for verification of payee?
No, not to the payer. The instant payments regulation bars a provider from charging the payer for the check, the same way it bars charging more for an instant transfer than for a standard one. Commercial terms between providers for answering requests are a separate question from what the customer pays.
Does verification of payee apply to bulk payment files?
Yes. The duty covers a payment file as well as a single transfer, so a payroll run or a supplier payment batch gets each payee checked before the file is released. How the result reaches you depends on your bank's channel: some return a per-item result the payer has to clear, others return a summary and leave the file to go through. Ask your bank which it does before your first run under the rules, because a file of two thousand items with a per-item hold needs a process behind it.
Verification of payee and Finance Loop
Finance Loop puts the people who had to build verification of payee in the same room: the bank teams that implemented the responding side, the payment institutions that route the requests, and the corporate payers whose supplier data the check now tests. Finance Loop is the meeting place for payments in Europe, with meetups and conferences on instant transfers, fraud and payment regulation. Finance Loop keeps the dates in its event calendar.
Finance Loop is a professional network and has the goal of driving the adoption of emerging technologies in finance, such as AI, tokenization, stablecoins, and DeFi. Finance Loop helps its members build skills and personal networks in these fields: Investment & Digital Assets, Payments & Digital Money, Digital Infrastructure & Sovereignty, and Risk & Compliance.