---
api: 'Business API'
---

# Validate an account name (CoP/VoP)

Validate a counterparty's account name against their account details when [adding a counterparty](/docs/api/business#add-counterparty) or [making a transfer](/docs/api/business#create-payment) to a new or existing counterparty.

:::warning
The CoP check is **not** a complete fraud-prevention tool, and it does **not** guarantee the person is who they claim to be.
It only confirms that the name and account details your provide match the bank's records.

Even if the counterparty's details match, you should still exercise due caution when transferring funds.
:::

:::note[Availability & Sandbox behaviour]
- This feature is only available to businesses in the [supported regions](/docs/guides/manage-accounts/counterparties/confirmation-of-payee#supported-regions-and-services).
  Additionally, to get access to CoP in the UK, eligible businesses must contact [Revolut API Support](mailto:api-requests@revolut.com).
- In Sandbox, this feature is only available for **testing**.
  While **incomplete or invalid requests** will return production-like error responses, **complete and valid requests** in Sandbox do **not** undergo real validation and will always return `cannot_be_checked`.
:::

The validation relies on different underlying services, depending on the recipient's payment scheme (region and currency).
These factors determine which fields you must provide and what response you get.
- For examples, refer to the request body samples.
- For more information, see the guides: [Validate an account name (CoP/VoP)](/docs/guides/manage-accounts/counterparties/confirmation-of-payee).

## Endpoint

POST `/account-name-validation`

## Request body

Counterparty account details

### Attributes

## Returns

### 200

Account name validation result

:::note
- The actual results returned in the response come from the CoP services, not from Revolut.
  The Business API passes them on as received.

  Because of this, the descriptions below should be treated as an approximation rather than complete documentation.
- The responses differ depending on the CoP service, even when the schema appears the same.
  Make sure that you refer to the appropriate response variant.
:::

#### Response attributes


## Error responses

| HTTP status code | Description |
| --- | --- |
| 400 | Bad request  Returned, for example, when the data you provided is invalid or required data is missing. |
| 401 | Unauthorized  Returned, for example, when the credentials you used to make the request are invalid. For more information, see the **Authorization** section. |
| 404 | Not found  Returned, for example, when your account does not have access to CoP. |