v1

latestOpenAPI 3.1.02026-07-26290133.2 KB

Confirmation of Payee (CoP) Validation

Confirmation of Payee (CoP) is a fraud prevention tool used to verify the name of the account holder upon creating a new UK beneficiary or modifying the details of an existing beneficiary entry. CoP offers more transparency during UK bank transfers and ensures that each Faster Payments/Chaps payment is sent to the intended recipient, reducing the risk of misdirected payments due to mistakes or fraud. Prior to registering or updating a UK beneficiary, the CoP system can check if the name entered matches the name on the recipient's account and will eventually return one of four responses: Exact Match: The name matches the intended recipient's account. Close Match: The name is similar but not an exact match, and the payer can proceed with caution or correct the details. No Match: The name doesn't match the account, and the payer is advised to check the details with the beneficiary before proceeding. Unavailable: The account does not support CoP/the beneficiary has opted out of CoP. A complete list of status codes, along with their descriptions, can be found on the <a target="_self" href="/reference/confirmation-of-payee-status-codes">CoP Status Codes</a> page. Note: Even though CoP adds an extra layer of security, it is considered as an optional feature. Despite the response provided by the CoP system, the creation of a beneficiary can still proceed. The final decision lies with the OpenPayd customer, who can either take corrective action based on the CoP response or proceed further with the payment.

post/beneficiaries/verify

Request body

accountNumberstring required

Account number of the account.

sortCodestring required

Sort code associated with the account.

beneficiaryType'CORPORATE' | 'RETAIL' required

bankAccountHolderNamestring required

If beneficiary type is corporate then company name else first name + last name

verificationReferencestring

If required from previous Verify CoP request and it is not send in this request it will be autogenerated on our side

Response

200

providerRegistrationIdstring

statusstring

{"stackTrail":"paths:/beneficiaries/verify:post:responses:200:content:application/json:schema:properties:statusDescription","oasType":"schema","type":"unknown"}

{"stackTrail":"paths:/beneficiaries/verify:post:responses:200:content:application/json:schema:properties:bankAccountHolderName","oasType":"schema","type":"unknown"}

bankNamestring

Example response

{
  "providerRegistrationId": "100021",
  "status": "MATCH",
  "bankName": "ClearBank Limited"
}