Verification of Payee
Before a euro transfer is authorised, the payer learns whether the name and IBAN really belong together — how Verification of Payee works.
L0 Explain simply
An everyday analogy: you hand a bank teller an envelope of cash and say 'this is for Maria Keller, account 4471'. A careful teller checks the ledger and tells you: 'that account is actually held by M. Kellner — do you still want to send it?' You decide. Verification of Payee is that teller built into euro payments: before you authorise a credit transfer, your bank asks the beneficiary's bank whether the name you typed matches the name on the IBAN, and shows you the answer. It does not block anything — you may still send — but you send informed. Many misdirected payments and a lot of impersonation fraud die at exactly this moment, which is why European law made the check mandatory.
L1 Core concepts
Verification of Payee (VoP) is a pre-payment check: the payer's PSP sends the payee name and IBAN the payer entered to the payee's PSP, which compares them against the account it holds and answers — a match, a close match, no match, or that the check could not be performed. The payer sees the outcome before authorising. Under the EU Instant Payments Regulation, PSPs in the euro area must offer this service, free of charge, since 9 October 2025; PSPs outside the euro area follow by 9 July 2027. The EPC published a dedicated VOP scheme rulebook so that PSPs across SEPA perform and answer these checks in a uniform way, covering credit transfers ahead of both SCT and SCT Inst. The payment itself is untouched: VoP informs the payer's decision, it does not replace it.
L2 Practitioner view
Operationally, VoP is a low-latency lookup service bolted onto the front of every credit transfer, and its difficulties are data difficulties. Names are messy: personal names with diacritics, transliterations, and abbreviations; company trading names versus registered names — so the responding PSP's matching logic decides how often customers see 'close match', and on a close match the response can carry the name actually held, letting the payer compare directly. Latency budgets are tight: the check sits inside a checkout or app flow. Bulk corporate files are handled differently from single-payment journeys. And the check changes conversations, not just fraud numbers: customer services must explain no-match results that are innocent — a maiden name, a joint account — without training customers to ignore warnings. Institutions differ in matching thresholds and in how results are presented.
L3 Technical details
The EPC's VOP scheme rulebook defines the mechanics: the roles of requesting and responding PSPs, the API-based exchange between them, the answer categories, and the timing expectations that keep the check usable inside a payment flow. Adherence to the VOP scheme is separate from SCT adherence, and for organisations the scheme supports verification against identifiers beyond the name alone. The Instant Payments Regulation is the legal layer above: it makes offering the check mandatory and free, whether the payer then sends an instant or a standard transfer. This is among the newest parts of the SEPA stack — first rulebook generation, early operational experience — so both the rulebook version and market practice should be checked as of the date you read this rather than assumed stable.
Sources & standards1
- Scheme-specific ruleversion 1.1 (EPC218-23)
Verification Of Payee scheme rulebook ↗ — European Payments Council · VOP scheme rulebook — roles, answer categories, and timing
The first rulebook version entered into force on 5 October 2025; version 1.1 was published in March 2026 to address issues found after deployment, and the EPC has announced a version 2.0 for later in 2026.
L4 Standards & sources
The scheme document is the EPC's VOP rulebook, EPC218-23. The version in force since 5 October 2025 defines the roles of requesting and responding PSP, the VOP request/response exchanged over the scheme's inter-PSP API — specified in separate API specifications and a security framework — the answer categories (match, close match carrying the name actually held, no match, verification not possible), a five-second maximum execution time, and a directory service for reachability. The legal driver is Regulation (EU) 2024/886, the Instant Payments Regulation: it amends the SEPA Regulation to make the check mandatory and free for euro-area PSPs from 9 October 2025, for instant and ordinary credit transfers alike. The scheme is revising fast: a 2026 version 1.1, issued March 2026, takes effect on 20 September 2026 — check the EPC library for the version in force.
Sources & standards1
- Scheme-specific ruleversion 1.1 (EPC218-23)
Verification Of Payee scheme rulebook ↗ — European Payments Council · EPC218-23 — roles, VOP request/response, answer categories, and maximum execution time (section 3.3.2)
The first rulebook version entered into force on 5 October 2025; version 1.1 was published in March 2026 to address issues found after deployment, and the EPC has announced a version 2.0 for later in 2026.
SEE THE PAYMENT MOVE
Read the steps as text
- 05PostingBank Alfa debits RiyaBank Alfa (payer PSP)
With the check passed and the payment confirmed, Bank Alfa books the debit on Riya's account. Her money has left her account, but nothing has yet moved between the banks.
- DR Riya's current account at Bank Alfa — EUR 480.00
- 07SettlementThe banks settle in central bank moneyBank Alfa (payer PSP) → Nordbank (payee PSP)
TIPS moves the amount between the banks' positions in central bank money the instant the transfer is accepted. Only now has money actually moved between Bank Alfa and Nordbank — the VoP message earlier carried no funds.
- DR Bank Alfa position at TIPS — EUR 480.00
- CR Nordbank position at TIPS — EUR 480.00
- 08PostingNordbank credits Arjun within secondsNordbank (payee PSP)
Nordbank books the credit and Arjun can use the money immediately. The transfer is complete end to end: name verified, Riya debited, banks settled, Arjun credited.
- CR Arjun's current account at Nordbank — EUR 480.00
Sources for this topic2
- Scheme-specific ruleversion 1.1 (EPC218-23)
Verification Of Payee scheme rulebook ↗ — European Payments Council · VOP scheme rulebook
The first rulebook version entered into force on 5 October 2025; version 1.1 was published in March 2026 to address issues found after deployment, and the EPC has announced a version 2.0 for later in 2026.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The teller analogy compresses an API exchange into a conversation, and all names and account numbers shown are fictional. Matching algorithms, thresholds, and result presentation vary by institution and are not specified by this summary; legal effective dates were verified in July 2026 against the Instant Payments Regulation timeline.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Deepest material on this page: L4 — Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.