--- title: "Execute CoP Checks" slug: "execute-cop-checks" updated: 2026-07-09T15:09:32Z published: 2026-07-09T15:09:32Z canonical: "www.documentation.paynetics.digital/execute-cop-checks" --- > ## Documentation Index > Fetch the complete documentation index at: https://www.documentation.paynetics.digital/llms.txt > Use this file to discover all available pages before exploring further. # Execute CoP Checks ## CoP request For every outgoing transaction via Faster Payments which your customers attempt to make, you need to perform a CoP request via Paynetics. The CoP request must happen prior to the transaction and the transaction must not be executed until the results of the CoP request are presented to the customer and subsequently the customer has confirmed proceeding with the transaction. It is possible that multiple CoP requests could be performed for a single transaction in cases where after performing a CoP request, the user subsequently edits the recipient details. Upon an edit of the recipient details, a new CoP request must be performed. ## CoP response For every incoming transaction via Faster Payments, Paynetics, on your behalf will provide CoP response to the requesting party. Your duty is to maintain updated customer details with Paynetics – such as names, account number and account type (business or personal). ## CoP API endpoint API endpoint: [https://developers.paynetics.digital/#copDetails](https://developers.paynetics.digital/#copDetails) The CoP endpoint is used only for performing CoP requests. For performing a CoP response, there is no need for an endpoint. The current version of the API endpoint is expected to evolve. This endpoint has exposed the attribute **token**, the token of the CoP request, which corresponds to a Paynetics-generated unique ID of the CoP request. Paynetics will store each CoP request. We recommend that you also store each CoP request, using the same token. This will enable Paynetics to roll out additional functionality in the future. ## Transfers API endpoint API endpoint: POST /v2/transfers Currently, the Transfers endpoint does not consume the attribute **token** described above (and available via the CoP endpoint). In the upcoming version of the Transfers endpoint, Paynetics will expose the attribute **token**, which will enable Paynetics to associate a transaction with a CoP request. ## API Integration ## Testing Via your existing Sandbox environment with Paynetics, you have access to the endpoint ([https://developers.paynetics.digital/#copDetails](https://developers.paynetics.digital/#copDetails)). You can test your integration using the file: [CoP Test Data.xlsx] ## Design Guidance ## Figma Paynetics has developed several design mockups for iOS which highlight the different user flows based on the CoP response code. For each user flow the most important considerations are the message shown to the user explaining the result of the CoP check and the primary action button, which is relevant for the respective CoP response code, see section [Mapping CoP response codes to design](/docs/execute-cop-checks#_Mapping_CoP_response) below. Link to [Figma mockups](https://www.figma.com/design/NfmtPgprAavr6veQGIrGsV/Confirmation-of-Payee?node-id=0-1&t=BSU7TvB9KVK7EOAL-0). ## Additional Information ## List of CoP response codes Response codes returned by the CoP provider: | **Reason code** | **Code description** | **Full Match** | **Long description** | **Account name passed back** | | --- | --- | --- | --- | --- | | N/A | N/A | TRUE | The CoP Responder has performed the matching and confirms it is a match | No | | ANNM | Account name does not match | FALSE | The CoP Responder has performed the matching and confirms it is not a match | No | | MBAM | There may be a match on the account name | FALSE | The CoP Responder has performed the matching and it is a close match | Yes | | BANM | Business account, name matches | FALSE | The CoP Requester indicated that the Payer intends to pay a personal account, but the actual account is a business account and the name matches. | No | | PANM | Personal account, name matches | FALSE | The CoP Requester indicated that the Payer intends to pay a business account, but the actual account is a personal account and the name matches | No | | BAMM | Business account, name may be a match | FALSE | The CoP Requester indicated that the Payer intends to pay a personal account, but the actual account is a business account and the name is a close match | Yes | | PAMM | Personal account, name may be a match | FALSE | The CoP Requester indicated that the Payer intends to pay a business account, but the actual account is a personal account and the name is a close match | Yes | | AC01 | Incorrect account number | FALSE | Account does not exist in the CoP Responder's books | No | | IVCR | Invalid Customer Reference | FALSE | The CoP Responder was unable to locate the customer account based on the secondary reference data contained within the Secondary Identification field | No | | ACNS | Account type Not Supported for CoP | FALSE | Account not supported for CoP by the CoP Responder. This code should also be used by a sponsor bank if the account relates to a collection account held by an ASPSP that is not reachable for CoP and they instruct payers to enter the SRD account level name for inbound payments as the sponsor will not be able to match based on the collection account name | No | | OPTO | Opted out of CoP Scheme | FALSE | Payee has been opted out of the CoP service by the CoP Responder | No | | CASS | Account has been switched | FALSE | The Payee's account has been switched using the Current Account Switch Service (CASS) | No | | SCNS | Sort code not supported at endpoint | FALSE | The CoP Responder has incorrectly received a CoP request for a sort code that does not belong to them | No | ## Mapping CoP response codes to design Design recommendations for each response code by the CoP provider: | **Reason code** | **Primary** **action** | **Primary message** | **Secondary action** | **Tertiary** **action** | | --- | --- | --- | --- | --- | | N/A | Yes - continue with payment | The account name is a match | No - cancel payment | | | ANNM | No - cancel payment | The name you gave us is not the same as the name held on the account | Edit payment details | Yes - continue with payment | | MBAM | No - cancel payment | The name you gave us is not the same as the name held on the account. It's a close match, the name is ... | Edit payment details | Yes - continue with payment | | BANM | No - cancel payment | The account name matches for a business account | Edit payment details | Yes - continue with payment | | PANM | No - cancel payment | The account name matches for a personal account | Edit payment details | Yes - continue with payment | | BAMM | No - cancel payment | The account name is a close match for a business account | Edit payment details | Yes - continue with payment | | PAMM | No - cancel payment | The account name is a close match for a personal account | Edit payment details | Yes - continue with payment | | AC01 | No - cancel payment | Account not found | Edit payment details | | | IVCR | Yes - continue with payment | Reference not found | No - cancel payment | | | ACNS | Yes - continue with payment | Unable to confirm name | Edit payment details | No - cancel payment | | OPTO | Yes - continue with payment | Unable to check name | Edit payment details | No - cancel payment | | CASS | Yes - continue with payment | Account has been switched | Edit payment details | No - cancel payment | | SCNS | Yes - continue with payment | Unable to check name | Edit payment details | No - cancel payment | ## FAQs ## Name matching - **Salutations** (Mr., Mrs., etc) – salutations are optional and they do not impact the result of the check. - **Capitalisation** (John vs JOHN) – letter capitalisation does not impact the result of the check. - **Business name abbreviations** (Ltd, Limited, LLC, etc) – business name abbreviations are stripped out and do not impact the results of the check. There is a broad list of such abbreviations, which is available upon request. - **Middle names** – middle names are excluded from the check. Only first and last names are verified. - **Reversed names** (Smith, John instead of John Smith) – if the first and last names are switched (last name, then first name) the check will return a partial match, but the response will not fail. A UK payment scheme operated by Pay.UK that enables near real-time account-to-account GBP transfers, typically settling within seconds. Paynetics accesses Faster Payments via its partner settlement banks (ClearBank and LHV UK) for inbound and outbound UK payments. Paynetics' isolated test environment that mirrors the production platform. Partners use the sandbox during the Technical Integration Phase to build, test, and validate their integration before going live. The sandbox supports the full API surface including card issuance, transactions, and webhooks. An **Account** is a payment or e-money account used to hold funds and execute transactions. Accounts are created under a specific instance and program and are associated with either a user or a merchant. They provide the logical structure under which balances, cards, and transactions are organised. Common account purposes include: - executing card payments and transfers - holding settlement funds - pre-funding services such as OCT An account acts as a container for balances rather than holding funds directly.