Perform a Confirmation of Payee (CoP) check via the Pay.UK scheme before initiating a Faster Payments transfer

Steps

1. Obtain CoP API access either as a Direct Participant (your own connection to the Pay.UK central routing service) or as an Indirect Participant via an aggregator such as TechnoXander, Konsentus, or similar approved service
2. Build a CoP request payload with the payee's sort code, account number, account type (Personal or Business), and the name as entered by the payer; POST to the /cop/check endpoint (exact path depends on your aggregator)
3. Interpret the response code: MATCH means the name matches exactly, CLOSE_MATCH means the name is similar (present the suggestion to the payer), NO_MATCH means name does not match, CANNOT_CONFIRM means the account holder's bank does not participate or cannot respond
4. For CLOSE_MATCH: display the suggested name to the payer and require explicit confirmation before proceeding; log the payer's decision for your APP fraud liability records
5. For NO_MATCH: display a high-prominence warning per PSR PS22/3 requirements; do not block the payment outright but document the payer's override if they proceed
6. Record the CoP response and payer decision against the payment reference; this audit trail supports reimbursement claim defences under the mandatory APP fraud reimbursement rules effective October 2024