Open banking confirmation of payee is not one product. It is two things that get searched together: open banking, which is the set of APIs that read account data and initiate payments with the payer's consent, and Confirmation of Payee, which is a name-versus-account check. Open banking can carry a payment and report its status. It does not, on its own, tell you whose account an IBAN belongs to.
That distinction matters because the phrase sounds like a single feature you can switch on. It is not. If you are a payer, the name check you see comes from your bank's payment flow. If you are a business, it comes from a dedicated name-check service. Open banking sits next to both, and replaces neither.
What 'open banking confirmation of payee' actually means
Two definitions, kept apart, explain almost every confusing result on this topic.
- Open banking: under PSD2, banks in the EU must let licensed third parties access account information (AIS) and initiate payments (PIS) with the customer's explicit consent. The APIs return balances, transaction lists and payment statuses. They are about access to an account, not about the identity of a payee.
- Confirmation of Payee: a check that compares a name the payer supplies with the name registered on the destination account, and returns a standardised answer. In the UK this is the CoP scheme run on sort code and account number. In the EU the regulated version is Verification of Payee on the SEPA scheme, on the IBAN.
The two get conflated for a simple reason: many open banking payment providers also offer a name check, so the marketing pages describe both in one breath. The underlying services are still separate, with separate inputs and separate answers. If you want the wider picture of how the pieces fit, the article on open banking, PIS, AIS and VoP sets them side by side.
One question each
Open banking answers 'can I see this account, and can I move money from it?'. A name check answers 'does this account belong to the party I named?'. A provider may sell both, but they are not the same answer.
How Confirmation of Payee works: name, account number, sort code
Confirmation of Payee is the UK name-checking scheme. The mechanics are simple and worth knowing, because they explain why the UK pages you find do not describe a SEPA payment.
- 1 The payer enters the payee's name, sort code and account number.
- 2 The payer's bank sends those details to the bank that holds the destination account.
- 3 That bank compares the name with the name on its own records, using the scheme's matching rules.
- 4 It returns one of four answers: match, close match, partial match or no match.
- 5 The payer's bank shows the answer before the payment is confirmed. The payer decides whether to continue.
Two details matter. First, the identifiers are the sort code and account number, which are UK domestic details - not an IBAN. Second, the check is advisory in the same way the EU check is: it warns the payer, it does not block the payment. A 'partial match' is the UK scheme's way of saying the names overlap but not fully, for example a first name against an initial.
Where open banking fits - and where it stops
Open banking APIs are good at three things: reading balances and transactions, initiating a payment from the payer's account, and reporting what happened to that payment. The third is where the confusion starts.
A payment initiation returns status messages as the payment moves. In ISO 20022 terms you will see statuses such as AcceptedCreditSettlementCompleted, which means the payment was accepted and settled. That is genuinely useful for reconciliation: you know the money left and arrived. It says nothing about who received it. A payment to a fraudster's account settles exactly as cleanly as a payment to your supplier.
- What open banking gives you: consent-based access to account data, payment initiation, and payment status reporting.
- What open banking does not give you: the account holder's name as a lookup. Account holder data is personal data under GDPR, and only the bank that holds the account can confirm it.
- What a payment status proves: that the payment was accepted and settled. Not that the destination account belonged to the party you named.
This is the gap the ranking pages leave open. A status of AcceptedCreditSettlementCompleted is a confirmation of payment, not a confirmation of payee. If you want the mechanics of a real name-check request and response, the worked example on this site walks through a full exchange.
Settled is not the same as correct
A misdirected payment settles. An invoice-redirection payment settles. The status message tells you the rail worked, not that the payee was right - which is why the name check has to happen before the payment is released, not after.
CoP vs Verification of Payee (VoP) in the EU
The UK scheme and the EU obligation solve the same problem with different legal bases and different identifiers. Keeping them apart stops you from building to the wrong specification.
- Legal basis: CoP is a UK scheme rule. VoP in the EU is mandated by the Instant Payments Regulation, Regulation (EU) 2024/886, which requires payment service providers to offer a name check on SEPA credit transfers.
- Identifier: CoP works on sort code and account number. VoP works on the IBAN.
- Timing: euro-area PSPs have had to offer VoP on euro credit transfers since 9 October 2025; PSPs in non-euro EEA states follow by 9 July 2027.
- Cost to the payer: the EU regulation requires the check to be offered to the payer free of charge on euro credit transfers.
- Outcomes: both schemes return a small set of standardised answers, and both are advisory rather than blocking.
If you are building for a European bank or PSP, the specification you implement is the EPC VoP rulebook, not the UK CoP scheme. The full comparison of the two sits on its own page; here the point is narrower: an open banking integration does not satisfy either obligation by itself.
What a name check can and cannot tell you
Every name check, UK or EU, resolves to one of four outcomes. Each calls for a different reaction, and the reaction is where most of the value is.
- Match - the name agrees with the account holder. Proceed with normal confidence.
- Close match - the names are similar but not identical: a missing middle name, initials, a trading name against a registered name. The verified name comes back so you can confirm or correct it. It is a prompt, not a failure - and not a guarantee either.
- No match - the name does not belong to that account. For a payee you expected, this is a stop signal. Do not resend with a tweaked name to force a match.
- Not available - the payee's bank could not answer at that moment. Neither good nor bad news; treat a new, unverifiable payee with extra care.
The limits are just as important as the outcomes. A match confirms that the name on the account agrees with the name you supplied. It does not confirm that the payee is honest, that the invoice is genuine, or that the account is not a mule account. And because the check is advisory, a no match only protects you if someone actually acts on it.
Close matches deserve a word of their own, because they are where businesses get it wrong. A close match on a supplier whose legal name differs from its trading name is normal and should be accepted once, then recorded. A close match on a supplier whose bank details 'just changed' is a different situation entirely: confirm it through a channel you already had, never through the message that carried the new IBAN.
What this means for banks, PSPs and businesses
The practical implications differ by who you are, but they all point the same way: the name check is a separate control that has to be built or bought.
- Banks and PSPs: VoP is an obligation under Regulation (EU) 2024/886, in both directions - as the requesting PSP for your payer and as the responding PSP for accounts you hold. An open banking gateway does not discharge it.
- Businesses and accounts-payable teams: verify supplier and payroll IBANs before release, and re-verify whenever bank details change. That is the moment invoice-redirection fraud exploits.
- Platforms and marketplaces: verify payees at onboarding and again at payout time, because a verified payee today can be a changed payee next month.
The honest limit: an open banking payment gateway is not a name-check service. It can move the money and tell you it arrived. It cannot tell you whether the account belonged to the party you named, and no amount of status reporting closes that gap.
How to check a payee name in practice
- 1 Use the name check your bank already offers. On a euro credit transfer in the EU it must be offered to you free of charge, and it appears in your banking app before you confirm.
- 2 For bulk payments, run the whole file through a dedicated VoP or IBAN name-check API before release, rather than checking payees by hand.
- 3 Enter the name exactly as it appears on the invoice, contract or statement - not as you remember it.
- 4 On a close match, accept the verified name the bank returns rather than overriding it, and record the decision.
- 5 On a no match, stop and confirm the details through a channel you already trusted.
- 6 Keep the result with the payment record, so you can show what you checked and when.
RoxPay delivers Verification of Payee on the SEPA scheme through one REST API and a dashboard, returning the standardised outcomes - match, close match, no match and not available - in well under a second, with the verified name on a close match, for a single payment or a whole payment file.