Create a counterparty

To make a funds transfer or payment, add the counterparty that you intend to transact with.

Depending on which country a counterparty account is based in, the fields that you need to specify are different. You can check the supported countries and currencies, and/or check the required fields dynamically before creating a counterparty. Additionally, some payment rails may have stricter requirements regarding the address field – for example, by also requiring the region field.

Ensure that you use the correct field to define the counterparty's name, which depends on how you add it:

• Revtag: name
• Other account details: individual_name (personal accounts) or company_name (business accounts)

See the API reference: Create a counterparty

See also how to validate an account name (CoP/VoP) when adding a counterparty.

You can add:

• Revolut counterparties using Revtags
• UK counterparties using account number and sort code
• International counterparties using required account details as per the counterparty's region

Before adding a counterparty, you can check which countries and currencies are supported, and/or check which fields are required for the desired country and currency.

Check supported counterparty countries and currencies​

When to check supported countries and currencies​

Before creating a counterparty, you may need to discover which bank countries and currencies are supported. Use the /counterparties/countries endpoint to get the full list of available country and currency combinations.

This is useful for dynamically building country/currency selection UIs, or for validating that a destination is supported before calling the Check counterparty field requirements endpoint.

Check supported countries and currencies​

Send a GET request to the /counterparties/countries endpoint.

The response contains a countries array where each item describes a supported country:

• Country: The country code where the counterparty's bank account is located.
• Currencies: The list of currencies available for counterparty creation in that country.

A sample response looks like this:

{
  "countries": [
    { "country": "GB", "currencies": ["GBP"] },
    { "country": "US", "currencies": ["USD"] },
    { "country": "DE", "currencies": ["EUR"] }
  ]
}

See the API reference: Check supported countries and currencies

Check counterparty field requirements​

When to check field requirements​

Depending on the counterparty's country, currency, and profile type (a.k.a recipient type), certain fields in the Create a counterparty request — such as tax_id, route, account_type, or specific name fields — become required or applicable.

Use the /counterparties/fields endpoint to dynamically discover these contextual fields before creating a counterparty. This is especially useful for multi-country payout systems where the required fields vary across destinations.

Check field requirements​

Send a GET request to the /counterparties/fields endpoint providing the following query parameters:

• Country: The country where the counterparty's bank account is located.
• Currency: The currency of the counterparty's bank account.
• Recipient type: Whether the counterparty is a personal or business account.

For corridors with multiple routing methods (e.g. ACH and Fedwire for USD to US), an optional route query parameter is available. When omitted, the response includes fields for the default route.

The response contains a fields array where each item describes a conditionally required or applicable field:

• Name: The field name, matching the Create a counterparty endpoint request body (e.g. sort_code, account_no, tax_id, route, account_type).
• Required: Whether the field must be provided when creating the counterparty.
• Regex: Validation rules with a pattern. In some cases, a human-readable description is also returned.
• Options: Allowed values for the field, if applicable. Each option has a value and an optional default flag.

Fields with options must use one of the listed values when provided to the Create a counterparty endpoint. Fields with regex must satisfy the specified constraints (e.g. character length, regex pattern).

{
  "fields": [
    {
      "name": "first_name",
      "required": true,
      "regex": {
        "pattern": "^[-'\\p{L} ]{1,40}$",
        "description": "Letters, hyphens and apostrophes only, up to 40 characters"
      }
    },
    {
      "name": "last_name",
      "required": true,
      "regex": {
        "pattern": "^[-'\\p{L} ]{1,40}$",
        "description": "Letters, hyphens and apostrophes only, up to 40 characters"
      }
    },
    {
      "name": "sort_code",
      "required": true,
      "regex": {
        "pattern": "^\\d{6}$",
        "description": "6-digit number"
      }
    },
    {
      "name": "account_no",
      "required": true,
      "regex": {
        "pattern": "^\\d{8}$",
        "description": "8-digit number"
      }
    },
    {
      "name": "address",
      "required": true
    }
  ]
}

{
  "fields": [
    {
      "name": "company_name",
      "required": true,
      "regex": {
        "pattern": "^.{1,140}$",
        "description": "Up to 140 characters"
      }
    },
    {
      "name": "route",
      "required": true,
      "options": [
        { "value": "ach", "default": true },
        { "value": "fedwire" }
      ]
    },
    {
      "name": "routing_number",
      "required": true,
      "regex": {
        "pattern": "^\\d{9}$",
        "description": "9-digit number"
      }
    },
    {
      "name": "account_no",
      "required": true,
      "regex": {
        "pattern": "^\\d{6,17}$",
        "description": "6 to 17 digits"
      }
    },
    {
      "name": "address",
      "required": true
    }
  ]
}

See the API reference: Check counterparty field requirements

Add a Revolut counterparty​

If a counterparty has a Revolut account, you can provide their Revtag and name.

curl -X POST https://b2b.revolut.com/api/1.0/counterparty \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <your access token>' \
  -d '{
        "profile_type": "personal",
        "name": "John Doe",
        "revtag": "johndoe"
      }'

To see more example requests and responses:

See the API reference: Create a counterparty

Alternatively, add a Revolut counterparty by providing their full details.

Test accounts for Sandbox​

In the Sandbox environment, you cannot add real people and businesses as Revolut counterparties. To simulate Create a counterparty requests, use one of the test accounts.

Add a UK counterparty​

If a counterparty has a UK bank account, the following details are required:

*The address field is optional; however, if you provide it, the address subfields below are required.

{
  "city": "London",
  "street_line1": "20 Upping St",
  "country": "GB",
  "postcode": "SW1A 2AB"
}

curl -X POST https://b2b.revolut.com/api/1.0/counterparty \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <your access token>' \
  -d '{
        "company_name": "John Smith Co.",
        "bank_country": "GB",
        "currency": "GBP",
        "account_no": "12345678",
        "sort_code": "223344",
        "address": {
          "city":"London",
          "street_line1":"20 Upping St",
          "country":"GB",
          "postcode":"SW1A 2AB"
        }
      }'

To see more example requests and responses:

See the API reference: Create a counterparty

Add an international counterparty​

If a counterparty has a non-UK bank account, depending on the country that the account is based in, you must specify the required fields.

See an example for an IBAN bank account.

curl -X POST https://b2b.revolut.com/api/1.0/counterparty \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <your access token>' \
  -d '{
        "company_name": "John Smith Co.",
        "bank_country": "FR",
        "currency": "EUR",
        "iban": "FR1420041010050500013M02606"
      }'

To see more example requests and responses:

See the API reference: Create a counterparty

Required details depending on the country {#add-counterparty-full-details}​

Check the following tables for the different required fields depending on the country.

Fields for US USD accounts​

Fields for IBAN countries​

Fields for SWIFT​

Fields for SWIFT MX​

Fields for IN INR accounts​

Fields for AU AUD accounts​

*The address field is optional; however, if you provide it, the address subfields below are required.

{
  "city": "Sydney",
  "street_line1": "21 Woolfe St",
  "country": "AU",
  "postcode": "NSW 2000"
}

What's next​

Now that you've added counterparties to transact with, learn how to send money.