GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX

Payments - Introduction / Learning brief

Confirmation of Payee (UK)

Your notes

What this means in plain language

Confirmation of Payee is the United Kingdom's pre-payment name-checking service. Before a sterling transfer is sent, it tells the payer whether the name they typed matches the account holder, returning a match, close match, or no match, and it compares closely with the euro area's Verification of Payee.

Confirmation of Payee (CoP) is a name-checking service used in the United Kingdom before a sterling payment is sent. When a payer enters a payee's name, sort code, and account number, the paying bank asks the receiving bank whether that name really belongs to that account, and shows the payer the answer. The result is one of four kinds: a match; a close match, where the name is nearly right and the real account name is shown so the payer can compare; no match; or a response saying the check could not be done. Confirmation of Payee does not block the payment, so the payer still decides whether to continue, but the payer decides while informed. Its purpose is to reduce two problems at once: payments sent to the wrong account by mistake, and authorised push payment (APP) fraud, where a victim is tricked into paying a criminal. The payer stays in control throughout.

Understand the full idea, step by step

The same good idea often grows up twice, in two places, under two names. Checking a payee's name before you pay is one of those ideas. In the euro area it is Verification of Payee. In the United Kingdom, where sterling moves over its own rails and accounts wear a different format, it is Confirmation of Payee — and it arrived first.

Confirmation of Payee (CoP)the UK's pre-payment name-checking service

Confirmation of Payee is a pre-payment verification service across the United Kingdom's sterling systems, including Faster Payments and CHAPS (Clearing House Automated Payment System). It answers one question: does the payee name the payer typed belong to the account identified by the sort code and account number? The paying bank sends the name and identifiers to the receiving bank, which compares them against the name it holds and returns a result. It also takes account of whether the account is personal or business, because that shapes how a name should be matched.

Reading the four outcomes
OutcomeWhat it meansWhat the payer should do
MatchThe name and account agreeProceed with ordinary confidence — a match is not proof the payment is wise
Close matchNearly right; the bank returns the actual account nameCompare and judge — innocent (a shortened name) or a warning
No matchThe name does not correspond to the accountStop and check — the strongest signal to pause
UnavailableThe check could not be completed (account not reachable, or timed out)A normal outcome, not a fault — proceed with care

Advisory, and coverage grew in phases

Like its euro-area cousin, CoP informs the payer's decision but never makes it — the payer may still send after any result, including no match. Coverage grew in phases as more institutions joined, and not every account is reachable, so an unavailable result is a normal outcome rather than a fault. Crucially, a match is not a guarantee: a payer who has been deceived into paying a criminal's genuine account will still see a match, because the name really does fit that account. The service narrows misdirection; it does not certify intent.

The same idea, a different account format

CoP and VoP share a purpose and diverge in detail. Both are pre-payment checks comparing a payee name against the account it is being sent to; both return match, close-match, and no-match style answers; both are advisory. The differences are scope and mechanism. CoP operates on sterling payments and identifies accounts by sort code and account number. VoP operates across the Single Euro Payments Area (SEPA) and identifies accounts by IBAN. Their legal footing differs too: VoP is mandated and must be free of charge under the European Union's Instant Payments Regulation on a phased timetable, while the UK's CoP grew through regulatory direction and industry adoption on its own timeline.

CoP versus VoP
Confirmation of Payee (UK)Verification of Payee (SEPA)
Currency / areaSterling, United KingdomEuro, across SEPA
Account identifierSort code + account numberIBAN
Nature of the resultAdvisory (match / close / no match / unavailable)Advisory (match / close / no match / not-possible)
Legal footingRegulatory direction + industry adoptionMandated free-of-charge under EU Instant Payments Regulation

COMMON CONFUSION

An 'unavailable' result means something has gone wrong and the payment should be abandoned.

Unavailable is an ordinary answer, not an error. It happens when an account does not support the service or a request times out. It simply means CoP could not check this one — so the payer weighs the payment without that reassurance, exactly as people did before CoP existed. It is a missing check, not a failed one.

STRICTLY SPEAKING

Strictly speaking, CoP is operated under UK scheme and regulatory arrangements rather than the EPC rulebook, its reachability has expanded in phases, and its precise matching behaviour is set by the participating institutions. Both CoP and VoP are recent, so check the rules and coverage of each as of the date of use rather than assuming them fixed.

FOR NOW, REMEMBER

  • Confirmation of Payee is the UK's pre-payment name check across sterling systems, using sort code and account number.
  • It returns match, close match, no match, or unavailable — a close match returns the actual account name to compare.
  • It is advisory: the payer decides, and a match confirms the name fits the account, not that the payment is safe.
  • CoP and VoP are the same idea in two areas — sterling/sort-code versus euro/IBAN — with different legal footings.
  • An 'unavailable' result is normal, meaning the check could not run, not that anything failed.

TRY IT YOURSELF

Arjun pays a builder he knows as 'J Smith Building'. CoP returns a close match and shows the actual account name as 'Smith Building Services Ltd'. What is the sensible read?

A close match with a plausibly-the-same business name; Arjun should confirm it is the right firm and can then proceed — the difference looks innocent.

Correct — Correct. Close match exists for exactly this: a name that is nearly right. The returned name lets Arjun judge that a trading name and a registered company name are the same builder, then decide — the choice stays with him.

A close match means the account is fraudulent and the payment must be abandoned.

Not this one — A close match is not a fraud verdict — it is a similar-but-not-identical name, very often innocent, like a trading name against a registered company name. CoP hands Arjun the information and leaves the judgement to him.

CoP has already blocked the payment, so there is nothing for Arjun to decide.

Not this one — CoP never blocks a payment. It is advisory; Arjun may proceed after any outcome, including no match. Here it has given him the real account name to compare, not a decision.

Name checks make a push payment safer. A different overlay changes the conversation entirely — letting the payee ask, and keeping the payer in control of the answer. Next: Request to Pay and e-mandates.

KEEP GOING

Three things to remember

  1. 01

    Confirmation of Payee checks whether the payee name a payer enters matches the name on the destination account before a sterling payment is sent.

  2. 02

    The result is advisory — a match, close match, no match, or a check that could not be performed — and the payer still chooses whether to proceed.

  3. 03

    Its aim is to cut misdirected payments and authorised push payment fraud, not to block transfers automatically.

Where you would use this

USE CASE 01

A retail customer paying a new payee sees a close-match warning with the real account name and pauses to check the details before authorising.

USE CASE 02

A bank builds Confirmation of Payee into its app and online banking so every new sterling payment instruction is name-checked at the point of entry.

USE CASE 03

A fraud team reviews how often no-match warnings are overridden, using the pattern to spot customers who may be acting under a scammer's pressure.

Put the idea into a real situation

Illustrative example: a customer of a fictional bank, Kingsbridge Bank, sets up a GBP 2,400.00 payment to what they believe is 'Rosewood Plumbing Ltd', entering a sort code of 20-00-00 and an eight-digit account number. Before the payment can be authorised, Kingsbridge asks the receiving bank whether that name matches the account. The receiving bank holds the account under 'Rosewood Building Services Ltd' and returns a close match, showing the real name. The customer, who was expecting an invoice from Rosewood Plumbing, stops and telephones the supplier on a number they already know. The check took under 3 seconds and blocked nothing; it simply gave the payer the account's real name at the moment the decision was made. Had the names agreed exactly, the response would have been a match and the payment would have continued normally.

Evidence & review

REVIEWED 2026-07-13

Confirmation of Payee across UK sterling systems; compared with SEPA Verification of Payee.

What this brief simplifies: CoP's phased coverage and matching behaviour described rather than dated; operator/scheme detail summarised at a teaching level.

Sources for this brief3
  1. Market practice

    CHAPSBank of England · UK sterling payment systems (Faster Payments, CHAPS) context

    Describes CHAPS, the UK's sterling high-value payment system, settled payment by payment in the Bank of England's RTGS infrastructure. · Checked 2026-07-12

    The Bank of England has operated CHAPS directly since November 2017; participant-facing reference documents are published separately.

  2. Scheme-specific ruleversion 1.1 (EPC218-23)

    Verification Of Payee scheme rulebookEuropean Payments Council · SEPA VoP, for the contrast

    Governs the EPC Verification Of Payee scheme under which PSPs check a payee's name against the account identifier before a credit transfer is sent. · Checked 2026-07-12

    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.

  3. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    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.

Learn this properly

Related briefs

View Payments - Introduction archive

Misc Payment Concepts

Provides a compact glossary of foundational terms such as SWIFT, SEPA, ISO 20022, payment infrastructures, and related standards.

READ BRIEF

Charges and FOREX (FX)

Explains common payment charge allocations and how foreign-exchange conversion and margins affect cross-currency transfers.

READ BRIEF

Payment Engines

Introduces the bank software that validates, routes, enriches, and processes incoming and outgoing credit transfers at scale.

READ BRIEF