EPC Publishes New Verification Of Payee Matching Recommendations
AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

Before you orderOffer from Amazon

Get smart everyday buys delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

The European Payments Council has published Version 2.0 of its Verification of Payee matching recommendations, adding guidance on character conversion and comparing beneficiary names. The document aims to support more consistent results, but payment service providers remain responsible for verification outcomes and retain discretion over their matching criteria.

The European Payments Council (EPC) has published Version 2.0 of its recommendations for matching names under its Verification of Payee (VOP) scheme, adding guidance on character handling and how payment providers assess beneficiary names before a payment is initiated. The recommendations are intended to support more consistent responses, while responding payment service providers remain responsible for verification results and can choose the matching criteria they apply.

The updated document explains how responding payment service providers should prepare and compare a payee’s name when deciding whether a verification request is a match, close match or no match. It covers issues that can affect comparisons, including spelling errors, reversed letters, initials, phonetic differences and commonly accepted abbreviations. For businesses and other legal entities, a provider may also take a commercial name into account alongside the registered legal name.

The EPC also clarifies the character sets used in VOP requests and responses. According to the report, inter-provider API messages generally use a limited Latin character set, with complex regional characters converted to basic letters. The recommendations refer to UTF-8, a standard for encoding text, and address how providers and routing or verification mechanisms (RVMs) can handle conversion and names containing characters outside the permitted set.

The recommendations apply to the matching process used by responding providers and the technical services that help handle account-verification requests. The EPC presents the guidance as a way to reduce unnecessary no-match or close-match responses that could add friction before a payment. It does not remove providers’ responsibility for the outcome or prescribe a single matching method for every participant.

At a glance
announcementWhen: Published after the EPC’s 2026 change m…
The developmentThe EPC released updated recommendations for how payment providers handle characters and assess names when matching payees under its Verification of Payee scheme.

How Name Matching Affects Payments

A name comparison that fails to account for differences in spelling, character encoding or the way a business is known can produce a result that does not reflect the intended payee. The EPC’s added guidance addresses these practical variations in a process designed to check beneficiary details before payment initiation. More consistent handling could help reduce avoidable interruptions for people and businesses making transfers.

The possible effect is not a guarantee that all providers will return the same result for every name. The recommendations leave matching criteria to individual providers, which remain responsible for their decisions. For customers, the guidance could influence whether a check returns a match, a close match or no match, but the source does not specify a uniform customer experience or quantify any expected reduction in payment friction.

The guidance also has implications for cross-border and multilingual name data: character conversion can affect how a name is represented when information moves between systems. Clarifying how providers and RVMs handle characters outside the permitted set gives participants a shared reference, though the document’s publication alone does not establish how consistently each service will implement it.

Products Worth Considering

Logitech MX Master 4 for Mac Wireless Ergonomic Mouse, Space Black

Logitech MX Master 4 for Mac Wireless Ergonomic Mouse, Space Black

As an affiliate, we earn on qualifying purchases.

From Consultation to Version 2.0

Version 2.0 follows the 2026 change management cycle for the EPC’s VOP scheme rulebook and a related public consultation. That consultation ran from April 1 through June 30, 2026, according to the source report. The material provided does not detail the consultation responses or identify which recommendations changed as a result of feedback.

VOP checks are intended to compare the payee details entered for a prospective payment with information held by the receiving side. The source report says the requirement became mandatory for payment service providers from October 9, 2025, as part of efforts to reduce losses linked to fraud and human error in the Single Euro Payments Area. A check indicates whether details match, closely match or do not match; the new recommendations focus on how those categories are reached, rather than changing the basic purpose of the check.

“The recommendations aim to support more consistent and user-friendly VOP implementations across the market.”

— European Payments Council, as described in the Finextra report

Implementation and Customer Effects

The source material does not state when individual providers are expected to implement Version 2.0, whether the recommendations are binding, or how the EPC will monitor adoption. It also provides no data measuring current false no-match or close-match responses, or estimating how much the new guidance might reduce them.

It remains unclear how providers will resolve difficult cases in practice, including names with characters that cannot be represented in the permitted set. Because providers retain discretion over their criteria, the recommendations do not guarantee identical outcomes across banks or intermediaries. The source report also does not describe any changes to the customer-facing warnings or appeal processes associated with a verification result.

Provider Adoption After Publication

The immediate next step is for payment service providers and routing or verification mechanisms to review the recommendations and decide how they fit their matching and character-conversion processes. The EPC’s publication sets out guidance, but the available source does not announce a separate implementation deadline or a further milestone.

Readers should look for provider communications or later EPC updates for details on adoption, operational changes and any evidence of effects on verification results. Until those details emerge, the confirmed development is the release of expanded recommendations—not a documented change in how every VOP check is already being handled.

Key Questions

What did the EPC publish?

The European Payments Council published Version 2.0 of its recommendations for matching processes under its Verification of Payee scheme. The update adds guidance on character handling and beneficiary-name assessment.

What kinds of name differences does the guidance address?

The recommendations cover spelling mistakes, reversed letters, initials, phonetic variations and commonly accepted abbreviations. For legal entities, providers may also consider a commercial name alongside the registered name.

Does Version 2.0 require every provider to use the same matching criteria?

No. The source says responding payment service providers remain responsible for verification outcomes and retain discretion over the criteria they apply.

When did VOP become mandatory, according to the report?

The Finextra report says VOP became a mandatory requirement for payment service providers on October 9, 2025. The new publication concerns recommendations for the matching process within the scheme.

When must providers adopt the new recommendations?

The source material does not give an implementation deadline or say whether Version 2.0 is binding. Provider adoption timing and the practical effects on verification results remain unclear.

Source: finextra.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

Can AI Turn A Firefox Security Fix Into A Working Attack?

Epoch AI says GLM 5.3 built file-reading attacks against six Firefox releases. Mozilla patched a separate flaw in Firefox 159.

Why The Worst AI Manager Still Gets 26 Points: Inside A Benchmark That Refuses To Hand Out Zeros

A new AI management benchmark reveals even the weakest AI managers score 26 points, highlighting the importance of trust and task completion in AI performance.

What Made This TV Box Botnet A Google Takedown Target?

Google says it disrupted the XCPE botnet, which used more than 1.3 million TV boxes. The alleged firmware backdoor may remain after the takedown.

A Supply Chain Attack Put Malicious Anthropic Claude Add-ons On Devices

A WIRED headline reports a supply chain attack involving Claude extensions, but the attack’s scope, method and user impact remain unverified.