On this page
concept

Verification of Payee (VoP)

Created 2026-10-10 31 connections

Verification of Payee (VoP)

A mechanism that checks whether the name entered by a payer matches the name registered to the destination bank account number before a payment is authorised. It applies to SEPA credit transfers in the EU (under Regulation (EU) 2024/886) and to Faster Payments and CHAPS in the UK under the name Confirmation of Payee (CoP). VoP is designed to prevent both misdirected payments (typos, stale account details) and Authorised Push Payment (APP) Fraud (scams where the payer is deceived into sending money to a fraudster's account).

How VoP works

The payer's PSP (Requesting PSP) sends the payee's account identifier — IBAN in the EU, or sort code and account number in the UK — plus the payee name to the payee's PSP (Responding PSP) via an API call. The Responding PSP checks its records and returns one of four outcomes instantly. The payer sees the result before confirming the payment and can proceed or abort. (Source: EPC VoP Scheme Rulebook v1.1, effective 20 September 2026; Stripe Support docs, 2025)

Response codes:

  • Match — name and account identifier align
  • Close Match — near-match; Responding PSP may return the registered name so the payer can correct their entry
  • No Match — name does not correspond to the account
  • Verification not possible — account not found, temporary outage, or responding PSP cannot check

Technical standard (EU): EPC Inter-PSP API Specifications EPC103-24 v1.0.1 (published May 2025). Authentication between PSPs uses QWAC PSD2 certificates. Routing and discovery via the EPC Directory Service (EDS) and national Routing and Verification Mechanisms (RVMs) such as STET Sepamail in France. Built on ISO 20022 resource elements. (Source: EPC VoP scheme page, fetched 2026-10-10; EPC103-24 v1.0.1, May 2025)

Check types: Name + IBAN; identification code (LEI or VAT number) + IBAN (name is optional for legal persons, mandatory for natural persons). (Source: EPC Rulebook v1.1)

Timing: PSPs must respond within 5 seconds; 1 second is the preferred target. (Source: Bottomline white paper via web agent, 2026-10-10)

Caching: At least one PSP implementation (ecommpay) documents that verified IBAN/name pairs can be cached for 10 days to reduce repeat-check friction. No regulatory carve-out for recurring payments confirmed. (Source: ecommpay developer docs, 2026-10-10)

UK (CoP): Uses sort code + account number (not IBAN). Operated via Pay.UK as an overlay service, with an aggregator model introduced in 2024 allowing smaller PSPs (especially fintechs) to participate indirectly. (Source: PSR CP26/2, July 2026)

EPC explicitly notes: "It cannot be relied upon to identify a private or a legal person." (Source: EPC VoP scheme page, fetched 2026-10-10)

EU mandate — Regulation (EU) 2024/886

Regulation (EU) 2024/886 amends the SEPA Regulation (Regulation (EU) 260/2012) to mandate VoP for all SEPA Credit Transfers (SCT) and SEPA Instant Credit Transfers (SEPA Instant Credit Transfer (SCT Inst)) regardless of the channel through which the payment is initiated — including open banking / pay-by-bank checkout flows. (Source: Bottomline white paper; finapi documentation, 2026)

Compliance timeline (as-of October 2026):

DateEventJurisdiction
8 April 2024Regulation (EU) 2024/886 entered into forceEU
5 October 2025EPC VOP Rulebook v1.0 entered into forceEU/EEA
9 October 2025VoP obligations effective for Eurozone PSPsEurozone
9 January 2027Receiving obligation for non-euro EEA PSPs beginsNon-euro EEA
9 July 2027Sending and VoP obligations for non-euro EEA PSPsNon-euro EEA
20 September 2026VOP Rulebook v1.1 becomes effectiveEU/EEA
End November 2026 (planned)VOP Rulebook v2.0 to be publishedEU/EEA

(Sources: EPC Press Release "VOP Rulebook Now Into Force", 6 October 2025; Natixis CIB, 9 March 2026; EPC VoP scheme page, October 2026)

EPC entry into force vs. regulatory obligation date: The EPC VOP Rulebook entered into force on 5 October 2025 (EPC Press Release, 6 October 2025), while the EU Instant Payments Regulation obligations became effective on 9 October 2025 (same EPC source; Natixis CIB, March 2026). These are distinct: the scheme pre-dates the legal compliance deadline by four days. No source retrieved explains what this meant in practice for PSPs.

EPC Rulebook v1.1 (effective 20 September 2026): Published 16 March 2026. Addressed "urgent change requests" arising from the initial deployment: technical issues discovered post-go-live and clarifications to the API specifications and API Security Framework (ASF). (Source: EPC Rulebook v1.1 publication page, March 2026)

UK — Confirmation of Payee (CoP)

The UK's equivalent scheme, operated by Pay.UK as an overlay service. Launched in 2020. Uses sort code + account number rather than IBAN. Governed by Payment Systems Regulator (PSR) Specific Directions rather than an EU regulation.

Regulatory history (as-of July 2026, PSR CP26/2):

  • SD10 (August 2019): Six largest banking groups required to offer CoP
  • SD11 (February 2022): Updated technical environment
  • SD17 (October 2022): Expanded to all qualifying PSPs in two groups
    • Group 1 deadline: 31 October 2023
    • Group 2 deadline: 31 October 2024
    • SD17 expiry: 1 November 2026
  • CP26/2 (PSR consultation, July 2026): Proposes (a) removing the SD17 expiry date so the direction continues indefinitely; (b) creating Group 3 from PSPs that adopted CoP voluntarily, with a 31 December 2026 deadline

Coverage (as-of August 2025, Pay.UK): Almost 400 PSPs; more than 99% of PSPs initiating Faster Payments in the UK. (Source: Pay.UK, August 2025)

Volume: Over 2 million CoP checks per day as of June 2025 (as-of June 2025); 2.5 billion checks since launch as of October 2024 (as-of October 2024). (Sources: Pay.UK June 2025; Finextra, October 2024)

PSR rationale for removing expiry (verbatim, CP26/2, July 2026): "Without an ongoing obligation there is a risk that participation could drop off — particularly as any new PSPs who enter the market after 1 November would not be required to provide the service meaning that not all PSPs would be on an equal footing."

Risk signal: "Transactions where the expected recipient name doesn't match the account are 25 times more likely to be fraudulent." (PSR CP26/2, July 2026, citing Form3 research, September 2023)

Fraud impact data

UK CoP (as-of 2023–2026 data):

  • 59% reduction in claims for payments to the wrong account since CoP launch (Pay.UK data, cited in PSR CP26/2, July 2026)
  • 20–40% reduction in losses to end users for some fraud types (Pay.UK data, cited in PSR CP26/2, July 2026)

The 17% reduction in APP fraud in 2023 (Pay.UK figure, cited by Finextra and Bottomline) is 2023 data. The PSR CP26/2 cites updated figures (59% reduction in wrong-account claims; 20–40% fraud loss reduction) from Pay.UK, which are more recent but not precisely dated within CP26/2.

EU VoP — post-launch (France, as-of early 2026): First month of operation (November 2025) through STET Sepamail (French RVM): 180 million transactions processed. Breakdown: Match 66%, Close Match 13%, No Match 19%, No Answer 2%. Overall match/close-match rate: 80%. Overall impact on transfer volumes described as "relatively neutral" — no measurable decrease in SCT/SCT Inst volumes. (Source: Natixis CIB, 9 March 2026)

Mismatch rates vary significantly by market: Luxembourg's Association of Banks (ABBL) reported approximately 40% of bank transfers flagged for name mismatch or incomplete details in the first weeks after the 9 October 2025 launch (Paperjam.lu, late 2025, described as "preliminary"). France's STET Sepamail reported 19% no-match for its December–January settled data (Natixis CIB, March 2026). These may reflect genuine differences in data quality between markets, timing (preliminary first-weeks vs. settled one-month data), or methodological differences. Neither figure has been independently verified.

No ecommerce-specific conversion data post-October 2025 VoP go-live was found in sources retrieved. All checkout friction data is inferential or pre-mandate. (Gap identified: 2026-10-10)

Impact on ecommerce

VoP applies to all SEPA credit transfers regardless of how the payment is initiated — including Open Banking/pay-by-bank flows used in ecommerce checkout, A2A payments, and recurring mandates. (Source: Bottomline white paper; finapi documentation)

Corporate and bulk payment complexity: VoP for bulk payment file processing was not fully implemented as of early 2026. Corporate clients are in "an observation and assessment phase" (Natixis CIB, March 2026). KPMG noted that "close match" or "no match" results can cause delays in crediting; some payments must be released twice. (Source: KPMG DE VoP overview, October 2025)

Stripe merchant guidance (2025): Merchants should ensure customers send payments using "the exact business name as it appears in your Stripe account." Mismatches can result in payment delay for manual review, return to sender, or additional verification steps. (Source: Stripe Support, VoP for incoming SEPA bank transfer payments, 2025)

Caching: Verified IBAN/name pairs can be cached (10-day default per ecommpay), reducing friction for repeat A2A transactions to the same account. (Source: ecommpay developer docs, 2026-10-10)

BNPL: No BNPL-specific VoP interaction data found in sources retrieved. (Gap)

Key providers

ProviderRoleGeography
EPC (via EDS + RVMs)Scheme governance; routing; directory serviceEU/EEA
STET SepamailFrench RVM; largest post-go-live volume confirmedFrance
SurePayDutch VoP operator; partnered with FIS for international rolloutNetherlands + international
Pay.UKUK CoP operator; aggregator modelUK
Swift BAVCross-border beneficiary account validation (not SEPA-specific)Global

(Sources: Natixis CIB March 2026; IBSIntelligence on SurePay/FIS; Pay.UK February 2025)

Domestic pre-existing schemes: Belgium, France, Italy, and the Netherlands had domestic-level VoP before the EPC-wide mandate. Interoperability challenges existed between domestic schemes prior to the EPC rulebook going live. (Source: Finextra VoP blog, late 2024)

UK CoP vs EU VoP — comparison

DimensionUK CoPEU VoP
Account identifierSort code + account numberIBAN (+ optionally BIC)
Payment railsFaster Payments and CHAPSSEPA CT and SCT Inst
Mandate effective2020 (big 6); ~99% by Oct 20249 October 2025 (eurozone)
RegulatorPSRRegulation (EU) 2024/886 + EPC rulebook
Scheme operatorPay.UKEPC (scheme); national RVMs
Participating PSPsAlmost 400 (as-of Aug 2025)~3,400 expected
Corporate name checkName onlyName or unambiguous ID (VAT/LEI); name optional for legal persons
Bulk paymentsNot natively in APISingle-payee API; bulk via third-party tooling
InteroperabilityDiscovery phase initiated (Pay.UK, Feb 2025)Separate scheme

(Sources: PSR CP26/2 July 2026; Pay.UK August 2025; EPC Rulebook v1.1; Finextra blog late 2024)

Fraud-security caveats

VoP as fraud prevention vs. false sense of security: Natixis CIB's anti-fraud coordinator warns that VoP "could create a false sense of security" and that "fraudsters are already finding ways to circumvent this system" — for example, by directing transfers to an individual account matching the name, rather than a company account. (Source: Natixis CIB, 9 March 2026). This directly challenges the dominant regulatory and vendor framing of VoP as an APP fraud prevention measure.

EPC limitation statement: "It cannot be relied upon to identify a private or a legal person." (Source: EPC VoP scheme page, fetched 2026-10-10)

Key terms

TermMeaning
VoPVerification of Payee — EU/EEA name for the scheme under Regulation (EU) 2024/886
CoPConfirmation of Payee — UK name for the equivalent account name-checking scheme
APP FraudAuthorised Push Payment (APP) Fraud — scam where victim is tricked into authorising a payment
SCT InstSEPA Instant Credit Transfer (SCT Inst) — SEPA instant payment rail
RVMRouting and Verification Mechanism — inter-PSP routing layer in EU VoP scheme (e.g., STET Sepamail)
EDSEPC Directory Service — PSP discovery and authentication layer
QWACQualified Website Authentication Certificate — PSD2 certificate used for PSP-to-PSP authentication
LEILegal Entity Identifier — used as alternative to name for legal persons in EU VoP
SD17Specific Direction 17 — UK PSR regulatory direction mandating CoP

Benchmarks (as-of 2025–2026)

MetricValueSourceAs-of
UK CoP daily checks2M+Pay.UKJune 2025
UK CoP cumulative checks2.5 billionFinextra / Pay.UKOctober 2024
UK CoP PSP coverage~400 PSPs; 99%+ of Faster Payments initiating PSPsPay.UKAugust 2025
Wrong-account claims reduction (UK)59%Pay.UK via PSR CP26/2July 2026
Fraud loss reduction (UK CoP, some types)20–40%Pay.UK via PSR CP26/2July 2026
EU VoP first-month volume (France, STET)180M transactionsNatixis CIBNov 2025 data
EU VoP match rate (France, Dec–Jan)66% match, 13% close match, 19% no match, 2% N/ANatixis CIBMarch 2026
Luxembourg mismatch rate (preliminary)~40%ABBL/Paperjam.luFirst weeks, Oct 2025
Fraud likelihood for name mismatch25× more likelyForm3/PSRSeptember 2023

What practitioners report

  • Bulk corporate VoP integration is the main post-go-live implementation challenge; single-payment consumer flows worked well at launch in France. (Natixis CIB, March 2026)
  • Fraudsters are already adapting: routing transactions to named individual accounts to pass VoP checks. (Natixis CIB, March 2026)
  • Belgian VBANs (Stripe BE IBANs) had initial UX issues post-mandate: Stripe advised merchants to instruct customers to skip VoP warnings and verify details manually while Stripe resolved the UX. (Stripe Support, 2025)
  • The aggregator model introduced by Pay.UK in 2024 was critical for scaling UK CoP coverage to fintechs and smaller PSPs. (Pay.UK, February 2025)
Research agent · 2026-10-10