Name-checking controls are moving from optional fraud-prevention tools to a core layer of real-time payment infrastructure as faster transfers reduce the time available to detect and reverse mistakes or scams.
A small check is becoming a large piece of infrastructure
For most of the history of electronic banking, payment safety was built around a simple assumption: there was enough time to detect a problem before the money became difficult to recover. Batch processing, banking hours and slower settlement created friction, but they also created pauses. Real-time payments change that balance. When funds can move within seconds, the industry has less time to correct a wrongly entered account number, question an unexpected beneficiary or interrupt a scam after a customer presses send.
That is why payee verification is moving from a useful front-end feature to a foundational control. The concept is straightforward. Before a transfer is released, the payer's bank asks whether the name entered by the customer is consistent with the account information held by the receiving institution. The payer receives a result such as a match, close match or no match and can decide whether to continue.
In Europe, this idea is now embedded in the regulatory architecture for instant payments. The European Central Bank explains that payment service providers in the euro area must offer Verification of Payee for both standard and instant credit transfers, free of charge to the payer, with the obligation applying from 9 October 2025. The service is designed to warn customers of discrepancies before a transfer is initiated.
The strategic significance is larger than the user interface suggests. Payee verification is becoming a network capability: a standardised query, a matching process, a response taxonomy, security rules, directories and operating procedures that have to work across thousands of institutions. Once that infrastructure is widely available, it can support not only fraud prevention but also better payment initiation, corporate controls and cross-border interoperability.
Why instant payments make verification more important
Faster settlement compresses the time available for intervention. In a traditional payment environment, fraud monitoring could sometimes rely on post-initiation reviews, manual queues or delayed settlement. In an instant environment, controls have to move upstream. The strongest place to stop a bad payment is before the instruction is sent, not after the funds have already arrived in a mule account and begun moving through the system.
This changes the economics of fraud prevention. A name check is relatively lightweight compared with the operational work required to investigate a scam, trace funds, handle a reimbursement claim and communicate with several institutions after the event. It also changes customer behaviour by introducing a targeted moment of friction: the payer is not blocked from paying, but is shown information that can make an error or impersonation attempt easier to spot.
The scale of the problem remains material. UK Finance’s Annual Fraud Report 2026 reported that authorised push payment fraud losses rose to £576.4 million in 2025, up 19% from the previous year, across 248,070 cases. Investment fraud accounted for £221.5 million of losses, while purchase scams represented 71% of APP cases. The figures underline a crucial limitation: the payment may be technically authorised even when the customer has been manipulated into sending it.
Payee verification cannot determine whether an investment is genuine, whether a romantic partner is real or whether an invoice has been maliciously altered. What it can do is reduce the gap between the identity a payer believes they are paying and the account that will actually receive the funds. That makes it one layer of a broader fraud-control stack rather than a complete solution.
The UK shows what happens when name checking becomes ubiquitous
The UK provides one of the clearest examples of payee verification becoming infrastructure rather than a niche bank feature. According to the Payment Systems Regulator, more than 320 organisations now offer Confirmation of Payee and more than two million checks are completed every day. The service covers more than 99% of Faster Payments transactions.
That degree of coverage matters because a verification service is only as useful as its reach. If a payer receives reliable confirmation for one bank but no result for another, the absence of a match can be difficult to interpret. Network effects therefore apply: every additional participating institution increases the probability that the payer receives a meaningful response, and widespread adoption makes the check part of normal payment behaviour.
The regulatory path also shows how infrastructure matures. In 2022, the PSR directed hundreds of additional payment service providers to implement Confirmation of Payee, with the aim of raising coverage from 92% to 99% of Faster Payments transactions. A later compliance report showed participation rising from 10 organisations in 2022 to around 320 by 2025.
By July 2026 the PSR was consulting on removing the expiry date from the direction that underpins broad participation and on expanding its scope. That is an important signal. A control initially introduced as a targeted anti-fraud measure is becoming a durable rule of the payments system.
Enforcement reinforces that interpretation. In February 2026, the PSR fined Bank of Ireland UK more than £3.7 million for failing to implement Confirmation of Payee by the required deadline. The significance is not the fine itself, but the message that name checking is no longer treated as an optional enhancement.
Europe is turning Verification of Payee into a common scheme
The European model is broader because it has to work across multiple domestic banking systems. The European Payments Council’s Verification of Payee scheme gives participating payment service providers a common process for sending a request and receiving a response before a SEPA Credit Transfer or SEPA Instant Credit Transfer is initiated.
The responding institution compares the supplied beneficiary information with the data it holds and returns a result such as match, close match, no match or verification not possible. This sounds simple, but the infrastructure underneath has to resolve practical questions about character sets, legal names, aliases, abbreviations, corporate identifiers, request routing, availability, response times and secure API connectivity.
Those operational details are still evolving. The EPC published Version 1.1 of the Verification of Payee rulebook in March 2026 following experience from the initial deployment. The update, due to become effective on 20 September 2026, includes clarifications and urgent changes to the rulebook, API specifications and API security framework.
That evolution is normal for network infrastructure. The first objective is interoperability; the second is reliability at scale. Once millions of requests are flowing each day, edge cases that looked minor in a specification can become operationally significant. A recurring source of complexity is matching itself. A legitimate account may be held under a registered legal name that differs from the trading name a customer recognises. Individuals may use initials, middle names, transliterations or different ordering conventions. Joint accounts and public-sector entities add more variation.
The challenge is to make the service sensitive enough to catch suspicious discrepancies without generating so many warnings that customers learn to ignore them. This is why matching quality, not merely API connectivity, will determine whether payee verification creates genuine safety or only another warning screen.
Australia and the United States are moving in the same direction
The trend is not confined to Europe. The Reserve Bank of Australia’s Payments System Board reported that Australian Payments Plus launched an industry-wide Confirmation of Payee service in July 2025 for payments addressed using a BSB and account number. The rollout was intended to cover more than 95% of personal accounts by December 2025, with banks introducing the service progressively.
Australia’s architecture matters because it extends the concept across both newer and legacy payment rails. This reinforces the idea that the control belongs at the account-addressing layer rather than being tied to one specific payment product.
In the United States, the Federal Reserve announced that the Reserve Banks would introduce a Payee Name Verification tool in 2026 to support efforts to reduce fraud and misdirected payments. The terms published in Operating Circular 5 describe a service that lets an institution evaluate whether an intended payee name is consistent with the title of the account identified by the routing and account number.
The Federal Reserve’s operating terms also make an important distinction: the service does not itself stop a payment from processing or settling. It provides information that the requesting institution can use in its own decisioning. That model preserves the separation between verification, fraud controls and payment execution.
This separation may become increasingly important as institutions combine name checking with behavioural analytics, device intelligence, transaction monitoring and customer warnings. The verification result can become one signal among many, rather than a binary gate.
Payee verification is really a data-quality problem
The technology is often described as a name-matching problem, but the deeper issue is data quality. A verification service can only compare what the payer enters with what the receiving institution stores. If account records are incomplete, inconsistent or outdated, false mismatches increase. If matching logic is too loose, genuine fraud indicators can be missed.
This creates a new operational incentive for banks and payment providers to improve customer master data. Legal names, trading names, account titles and identifiers become part of payments infrastructure rather than static onboarding records. For corporate accounts, the ability to associate recognised trading names with legal entities can reduce friction for customers who may know a merchant by its brand rather than its registered company name.
The same principle applies to payment initiation. Corporate treasury systems often rely on beneficiary templates, ERP master data and supplier files. If those records are clean and consistently mapped to verified account information, payee verification can be integrated into supplier onboarding and payment controls. If the data is poor, the service may simply expose errors that have been sitting inside enterprise systems for years.
The next stage is payment pre-validation
Once a payment network can validate a name before a transfer, the natural question is what else can be checked at the same point. Account status, routing eligibility, beneficiary type, payment purpose and structured invoice information are all candidates for pre-validation where regulation and privacy rules allow it.
This does not mean every payment should become a lengthy interrogation. The value of modern payment infrastructure lies in automating routine checks so that most transactions remain invisible and fast. The better model is selective friction: a clean, high-confidence match allows the payment to proceed smoothly, while a material discrepancy generates a clear and proportionate warning.
For banks, that architecture could improve straight-through processing as well as fraud prevention. A payment that has been pre-validated is less likely to fail because of incorrect beneficiary details. For corporates, it can reduce operational losses and repair work. For customers, it can increase confidence in account-to-account payments at a time when instant payments and open-banking payment initiation are expanding.
Warning fatigue is the main design risk
The biggest risk is that payee verification becomes technically ubiquitous but behaviourally weak. Customers already encounter fraud warnings, security prompts, confirmation screens and transaction limits. If verification produces frequent close matches or ambiguous results, users may learn to click through automatically.
That makes user-interface design part of payment security. The warning needs to explain what did not match, what the customer should check and what proceeding means. At the same time, institutions should avoid wording that suggests a name match guarantees the legitimacy of the underlying transaction. A fraudster can control an account whose name genuinely matches the details shown to the victim.
There is also a privacy trade-off. A poorly designed service could reveal account-holder information to someone probing account details. Verification schemes therefore need controls on what information is returned, who may request it, how requests are authenticated and how abuse is monitored. The infrastructure is valuable precisely because it connects institutions; that same connectivity has to be governed carefully.
Cross-border interoperability will be the harder problem
Domestic name-checking systems are easier to design because banks share a language, account format and legal framework. Cross-border payments introduce different scripts, transliteration rules, entity identifiers and privacy requirements. The beneficiary name used on an invoice may not match the registered account title, and intermediaries can add complexity.
The European scheme offers one route toward common standards because SEPA already provides shared payment instruments and technical rules. But global interoperability will require more than one standard. The practical objective is likely to be compatible verification outcomes rather than a single worldwide matching engine.
This is where structured identifiers may become more valuable. The EPC scheme already allows for the possibility of identifiers such as a VAT number or Legal Entity Identifier in some contexts. For corporate payments, an unambiguous identifier can be more reliable than free-text name comparison. Over time, the combination of verified identifiers, richer ISO 20022 data and payment pre-validation could make beneficiary assurance much stronger than simple string matching.
What this means for banks, fintechs and regulators
For banks, payee verification is becoming a resilience and fraud-control capability that has to operate at payment-system scale. Availability matters: if the verification service fails during a high-volume period, institutions need clear fallback rules that do not unnecessarily stop legitimate commerce. Matching models need monitoring, and customer-service teams need to understand why mismatches occur.
For fintechs and payment providers, the opportunity lies in orchestration. Firms that initiate payments can use verification results to improve onboarding, beneficiary management and transaction risk scoring. But the commercial value will depend on access rights, scheme rules and data protection. A third-party interface should not become a weak link that allows automated account probing.
For regulators, the challenge is calibration. Mandating participation can create network reach, but regulation also has to encourage consistent performance. Coverage statistics alone are not enough. Authorities will increasingly care about response quality, false-match rates, service availability, customer outcomes and how institutions behave when the result is inconclusive.
For investors in payments infrastructure, the broader theme is that fraud controls are moving into the rails themselves. The more real-time and irrevocable payments become, the more valuable pre-transaction intelligence becomes. That can increase demand for identity data, account validation, fraud analytics and secure API infrastructure alongside the payment rail.
A necessary control, but not a fraud solution on its own
Payee verification should not be oversold. Many scams involve a customer knowingly sending money to an account whose displayed name is exactly what the fraudster told them to expect. In those cases, a successful name match may provide false reassurance if the interface is poorly designed. Fraud prevention therefore still requires behavioural monitoring, scam intelligence, transaction limits, customer education, receiving-bank controls and rapid interbank information sharing.
The UK experience makes that point clearly. Despite widespread Confirmation of Payee coverage, APP fraud losses still rose in 2025. The PSR itself describes Confirmation of Payee as an important mechanism for reducing misdirected payments and certain types of APP fraud, not as a universal defence.
The strongest case for payee verification is therefore not that it solves fraud. It is that it removes one avoidable source of uncertainty before a payment becomes irreversible. In a real-time system, that is increasingly valuable.
Conclusion: verification is becoming part of the rail
The payment industry spent years making transfers faster, cheaper and more available. The next phase is making them more certain. Verification of the intended recipient is one of the simplest ways to add that certainty without slowing every transaction down.
The direction of travel is now visible across several major markets. Europe has made Verification of Payee a regulatory requirement for euro-area providers. The UK has pushed Confirmation of Payee toward near-ubiquitous coverage and is considering how to make that framework permanent. Australia has rolled out a national service, while the Federal Reserve has established terms for a US Payee Name Verification offering in 2026.
Taken together, these developments suggest that payee verification is moving into the same category as routing, messaging and settlement: a shared capability that customers increasingly expect to be present before money moves. The more payment systems become instantaneous, the more important it becomes to know that the destination is not merely valid, but consistent with the person or organisation the payer actually intends to pay.
References
1. European Central Bank — Instant Payments Regulation: Verification of Payee
2. European Payments Council — Verification Of Payee scheme
3. European Payments Council — Verification Of Payee Scheme Rulebook v1.1
4. European Commission — Payment services and instant payments
5. Payment Systems Regulator — CP26/2: Confirmation of Payee, July 2026
6. Payment Systems Regulator — Confirmation of Payee coverage and daily checks
7. Payment Systems Regulator — PS22/3 Extending Confirmation of Payee coverage
8. Payment Systems Regulator — Confirmation of Payee compliance report on SD17
9. Payment Systems Regulator — SD17 enforcement cases
10. UK Finance — Annual Fraud Report 2026 press release
11. Reserve Bank of Australia — Payments System Board Annual Report 2025
12. Australian Payments Plus — Payments roadmap update
13. Federal Reserve Board — 2026 Federal Reserve Bank services notice
14. Federal Reserve Financial Services — Operating Circular No. 5, Payee Name Verification terms