™I-X Function Run a scenarioRequest a demo
Blog · Payments ·

Payee name checks are here to stay: what treasury teams should do now

The UK has made Confirmation of Payee permanent and EU Verification of Payee is a year old. Here is how corporate payment teams can use both checks well.

On 22 October 2026 the UK Payment Systems Regulator (PSR) published a policy statement removing the expiry date from Specific Direction 17, the rule that requires most payment service providers (PSPs) to offer Confirmation of Payee (CoP). The direction had been due to lapse on 1 November 2026; it now continues in force until the PSR varies or revokes it. In the same month, the euro area's equivalent, Verification of Payee (VoP), turned one, and the European Banking Authority (EBA) described the rollout as broadly successful at a conference in Paris on 15 October.

Put together, these two developments settle one question for anyone who pays suppliers, staff or counterparties by bank transfer in the UK or the euro area: checking the payee's name against the account before money leaves is now a permanent part of the payment, not a temporary project. The open question is how well corporate payment processes use the answer.

What the UK decision changes, and what it does not

CoP checks whether the name a payer enters matches the name on the account at the receiving bank, for Faster Payments and the Clearing House Automated Payment System (CHAPS). The PSR says more than 320 organisations offer CoP checks and more than two million checks are completed every day.

The regulator's reason for keeping the rule is that CoP is a network service. Its policy statement notes that a check can only be completed where both the sending and receiving PSP take part, so without an ongoing obligation, coverage could erode as firms leave or new firms never join.

The evidence for the check is in the PSR's July consultation. It states that transactions where the expected recipient name doesn't match the account are 25 times more likely to be fraudulent, and cites Pay.UK figures showing a 59% reduction in claims for payments to the wrong account and a 20-40% reduction in losses for some types of fraud since CoP launched.

Two things did not change. The decision does not widen the rule to firms that offer CoP voluntarily; the PSR says it will continue engaging with stakeholders on whether and how CoP requirements could be expanded before deciding whether to consult. And the regulator will review the requirement in five years, or sooner if the payments landscape shifts.

One year of Verification of Payee in the euro area

VoP does the same job for euro credit transfers. Under the Instant Payments Regulation, a VoP service had to be in place by 9 October 2025 for euro payments between PSPs in the European Union and European Economic Area. The payee's bank answers with one of four results: match, close match, no match, or verification not possible. The payer then decides whether to go ahead.

The corporate picture is where the first year looks different. The regulation lets businesses opt out of the check when they submit multiple payment orders as a package, and many have. Deutsche Bank reported that in January 2026, 80% of SEPA credit transfer files and 67% of SEPA Instant files sent to it over EBICS were opt-outs (SEPA is the Single Euro Payments Area; EBICS is the Electronic Banking Internet Communication Standard, a common corporate-to-bank channel). That is one bank's client data, not a market measure, but the bank links it to a wider gap: the VoP step has not yet been embedded in most corporate treasury software, because there is no common model for the customer-to-bank side.

Opting out does not move risk to the bank. The European Payments Council (EPC) is explicit that whenever a corporate user authorises a payment, whether after receiving the VoP result or after opting out, the corporate user remains the liable party.

What is still coming

The scope is still growing. Payment institutions and e-money institutions in the euro area must send and receive instant euro transfers from 9 April 2027, and providers outside the euro area follow from 9 July 2027, when VoP also becomes mandatory for them. FinTech Weekly reports that the EBA expects the third Payment Services Directive (PSD3) and the Payment Services Regulation to extend VoP to credit transfers in all EU currencies. The scheme rules also keep moving: the EPC plans to publish versions 1.2 and 2.0 of the VoP rulebook at the end of November 2026.

What it means for treasury and payment operations

The checks exist at the bank. Whether they protect the business depends on what happens to the result inside the company. Five practical steps:

  1. Make the opt-out a decision, not a default. If your bulk files skip VoP, write down why, who agreed and when it will be reviewed. Since the payer stays liable either way, the opt-out should be backed by other controls on the supplier master file.
  2. Treat "close match" and "no match" as exceptions with an owner. A result that sits in a bank portal and never reaches the person releasing the payment is not a control. Decide who reviews each result type, how fast, and what evidence they need before they override it.
  3. Clean the payee data. Name checks compare what you send with what the receiving bank holds. Trading names, abbreviations and outdated legal names generate needless mismatches, which train staff to click through warnings.
  4. Protect the bank-detail change. The most damaging frauds change a known supplier's account details. Require an independent check and a different approver for any change of account before the next payment to that payee.
  5. Keep the evidence. For each payment, record the check result, who saw it, and who decided to proceed. If a payment goes wrong, that record is what the investigation and any claim will rely on.

The institution must confirm its own obligations under CoP, the Instant Payments Regulation and any local rules; this post is not legal advice.

Where IXFXN fits

Your bank runs the name check. IXFXN makes sure someone acts on the answer, and keeps the proof. It is one approval layer for every payment, whichever bank or provider it goes through: AI drafts it, your people approve it, every step is recorded.

The five steps above map onto controls in IXFXN today:

  • New bank details need a second person. When a supplier's bank details are added again or changed, no payment can use them until a different Admin or Approver confirms them and records how they checked. The rule is enforced in the database, not only on screen.
  • The approver sees the name check result. It sits next to the Approve button: Match, Close match, No match or Verification not possible. For anything but a match, approving takes one extra tap, "I've seen the name check", and IXFXN records who saw which result and when.
  • Exceptions have an owner. Close matches, mismatches and checks that could not be completed go to an Admin's list until someone deals with them.
  • Opting out is a decision. If your team opts out of name checks for bulk files at your bank, IXFXN records it with a reason, who agreed and a review date, and the decision comes back for review on that date.
  • The evidence stays with the payment. Each payment's record, the export and a Name checks report show the result, who saw it and who decided. If bank details change after approval, the payment is not sent.

IXFXN does not perform CoP or VoP checks; those stay with your bank, and IXFXN is not a CoP or VoP provider. In the Beta, every name check result is simulated (IXFXN compares the names itself, no bank is asked), and bank transfers and recipient screening are simulated too, while CoinPayments, DepiPay and bank statement files are live as read-only connections. If you want to see how these controls would sit alongside your bank's name checks, ask us.

Sources

IXFXN's weekly briefing on payments, treasury and AI. Not legal or investment advice. Get new posts in a feed reader (RSS).

More from the blog