Manage cards for your business

The Business API lets you issue and manage cards for your business.

Create or delete: Create a new virtual card, or terminate a card when you want to cancel your card permanently.
Update: Update card settings, such as the card's label, linked accounts, or spending controls, update contacts or update references for a specific card.
Get details: Retrieve the list of cards issued for your team, retrieve a specific card by its ID, or retrieve sensitive details for a specific card.
Block or unblock: Freeze a card to make it temporarily unavailable for spending or lock a card as admin; to revert, unfreeze or unlock it to re-enable spending for the card.

Different types of cards

You can create the following types of business virtual cards:

Team member cards: Cards issued in the individual's name, where the individual team member is the cardholder. To create this card, specify team member in holder_id.
Company cards: Cards issued in the business’s name, where the business is the cardholder, and up to 5 team members are added as card contacts. Card contacts can access card details and make payments on behalf of the business.
As these cards aren’t issued to a single team member, holder_id is not present. Instead, they have contact_ids, which lists the IDs of 1–5 team members added as contacts for the card.
Unlike cardholders for team member cards, card contacts can be reassigned throughout the lifetime of the card. However, there must always be at least 1 card contact assigned at any given time.
Auto-issued cards: Available only to travel intermediaries at this time, these cards are issued in the business's name and intended for server-to-server transactions. As such, they do not require card contacts to be assigned and may pass through frictionless 3DS verification. To create an auto-issued card, leave holder_id and contact_ids empty.

note
To use auto-issued cards, please contact Revolut API Support.

Create a virtual card

To create a new card, you must provide the following information:

Optionally, you can also specify additional details, such as a distinct label, linked accounts, and spending limits and categories.

Optional details

Holder ID: Specify the ID of the team member to assign as the holder of the card. Provide for team member cards. For virtual cards (virtual=true), this field is optional. If not provided, the type of the issued card depends on the presence of contact IDs:
- If contact IDs are provided, the card will be a company card.
- If contact IDs are not specified, the card will be an auto-issued card.
Contact IDs: Specify IDs of 1-5 team members to assign to the card as contacts. Provide for company cards.
Label: Give the card a label that will be displayed in the UI and in transaction reporting, to help with recognition and reconciliation.
References: Provide references for the card for easier transaction tracking. You can assign up to 5 name-value pairs, where the names must be unique. They can be amended up to 10 times.
note
References are supported only for auto-issued or company cards . They're not allowed for team member cards.
Spending limits: Set one of the periodic (day/week/month/quarter/year/all time) limits and/or a non-periodic (single) spending limit.
Spending period: Set dates after which the card becomes available or unavailable for spending and define what happens when the end date is reached.
Categories: Limit the merchant categories available for spending. By default, all are available. For a full list of categories, see the API reference.
note
If you restrict merchant categories, you cannot use merchant controls to allow specific merchants. However, you can still use merchant controls with categories to block specific merchants.
If you set only categories or only merchant controls, each works independently.
Merchant controls: Block or allow the card to only transact with specific merchants.
note
If you restrict merchant categories, you cannot use merchant controls to allow specific merchants. However, you can still use merchant controls with categories to block specific merchants.
If you set only categories or only merchant controls, each works independently.
For more details, see the API reference.
Countries: Restrict card use to specified countries, provided as 2-letter ISO 3166 codes.
Accounts: Limit which accounts the card should be linked to, by providing their IDs. By default, all are linked.

Travel intermediaries using our travel solution also have access to a dedicated field.

For sample requests and responses:

See the API reference: Create a card

Idempotency

To ensure that a card creation is not processed multiple times if there are network or system errors, we deduplicate requests made with the same request ID within a 24-hour interval (counting from the first request). This is why you should use the same request ID for requests related to the same card.

This also means that if the first request fails, this state is saved and returned in response to all the subsequent requests with the same request ID within the 24-hour deduplication period.
An exception is when the initial request fails for an unexpected reason. In such a case, you still get an error saying that the first execution was not successful, but you don't get the exact error message and code that might have been returned for that first execution, you only see that the idempotent replay failed.

While there is no specific requirement regarding the format of the request ID that you should use, we recommend using v4 UUIDs.

Update a card

Depending on what you need to update, you have a few endpoints at your disposal. You can:

Update card settings, such as the label, accounts, or spending controls
Update card contacts
Update card references

Update card settings

For each active card issued for your business, you can update its label displayed in the app, the merchant categories and countries available for spending, the spending limits, merchant-level controls and spending period, and the accounts the card is linked to. You can update a single parameter or multiple parameters at once.

Note that you cannot restrict categories and allow specific merchants at the same time. For more information, see: Create a virtual card → Optional details.

To reset the categories to default or erase a spending limit, provide null as the value for the respective parameter.

A sample request looks like this:

curl -X PATCH https://b2b.revolut.com/api/1.0/cards/{card_id} \
  -H 'Content-Type: application/json' \
  -H "Authorization: Bearer <your access token>" \
  -d '{
  "label": "New label",
  "categories": [
    "services",
    "shopping",
    "furniture"
  ],
  "spending_limits": {
    "single": null
  }
}'

For more details and example requests and responses:

See the API reference: Update card settings

Update card contacts

Card contacts are team members assigned to company cards. They can access card details and make payments on behalf of the business. Unlike cardholders for team member cards, card contacts can be reassigned, and there can be more than 1 card contact (up to 5 at a time).

You can only update contacts for a card that already has some contacts assigned, and you cannot remove contacts from a card completely – a company card must always have at least 1 card contact assigned at any given time.

curl -X PUT https://b2b.revolut.com/api/1.0/cards/{card_id}/contacts \
  -H 'Content-Type: application/json' \
  -H "Authorization: Bearer <your access token>" \
  -d '[
  "3ea984a5-d599-4c97-b2b3-c6c12bb9b5e9",
  "02b969cb-b984-4a70-873d-f93220805e5e",
  "36d9604d-4821-45fc-bf1a-a2881f6336c0"
]'

For more details and example requests and responses:

See the API reference: Update card contacts

Update card references

Card references are additional information that can be added to company or auto-issued cards to facilitate tracking transactions made with those card.

They take the form of key-value pairs, where each key (name) and value (value) can have up to 30 characters. You can add up to 5 such pairs to a card. References can be amended up to 10 times.

To remove existing references, simply provide an empty list.

curl -X PUT https://b2b.revolut.com/api/1.0/cards/{card_id}/references \
  -H 'Content-Type: application/json' \
  -H "Authorization: Bearer <your access token>" \
  -d '[
  {
    "name": "Budget",
    "value": "Engagement"
  },
  {
    "name": "Department",
    "value": "Business"
  }
]'

For more details and example requests and responses:

See the API reference: Update card references

Retrieve cards

The Business API lets you retrieve the cards issued for your business.

When you retrieve the cards, for each card, you get its details, such as the card ID, the last 4 digits of its PAN, expiry date, current state, its type, and more.

You can:

Retrieve all the cards in your account
Retrieve a specific card

Retrieve a list of cards

You can list all the cards issued for your business. You can also filter the cards by their creation date.

The results are paginated and sorted by the created_at date in reverse chronological order.

For more details and example requests and responses:

See the API reference: Retrieve a list of cards

Filtering and pagination

When retrieving cards, you can also include the optional query parameters to:

Modify the maximum number of cards returned per page (by default, it's 100)
Retrieve only the cards which were created before a date/date-time that you specify

For example, these parameters limit the number of cards to three and retrieve only the cards created before 13th June 2023:

/cards?limit=3&created_before=2023-06-13

To get to the next page, make a new request and use the created_at date of the last returned card as created_before.

Retrieve a specific card

You can also retrieve a single specific card by its ID to look up its details.

For more details and example requests and responses:

See the API reference: Retrieve card details

Retrieve sensitive card details

To retrieve sensitive details of a card, such as its PAN (Primary Account Number), CVV (Card Verification Value) and expiry date, use this dedicated endpoint.

In your request, provide the ID of the card for which you want to retrieve the sensitive details.

For more details and example requests and responses:

See the API reference: Retrieve sensitive card details

Freeze or unfreeze cards

You can freeze an active card to make it temporarily unavailable for spending, or you can unfreeze a frozen card to re-enable spending for that card.

Freeze a card

To freeze a card, provide its ID in the request to the freeze endpoint. On success, the card's state changes to frozen and no content is returned in the response.

For more details and example requests and responses:

See the API reference: Freeze a card

Unfreeze a card

To unfreeze a card, provide its ID in the request to the unfreeze endpoint. On success, the card's state changes to active and no content is returned in the response.

For more details and example requests and responses:

See the API reference: Unfreeze a card

Lock or unlock cards

You can apply an admin lock to a card to make it temporarily unavailable for spending, or you can unlock an admin-locked card to re-enable spending for that card.

Lock a card

To apply an admin lock to a card, provide the card's ID in the request to the lock endpoint. On success, the card's state changes to locked and no content is returned in the response.

For more details and example requests and responses:

See the API reference: Lock a card

Unlock a card

To unlock an admin-locked card, provide its ID in the request to the unlock endpoint. On success, the card's state changes to active and no content is returned in the response.

For more details and example requests and responses:

See the API reference: Unlock a card

Terminate a card

When you want to cancel your card permanently, you can terminate it.
Once the card is terminated, it will no longer be returned by the API or appear in your cards.

To terminate a card, provide its ID.

On success, the card is removed from your cards and no content is returned.

For more details and example requests and responses:

See the API reference: Terminate a card

Different types of cards​

Create a virtual card​

Idempotency​

Update a card​

Update card settings​

Update card contacts​

Update card references​

Retrieve cards​

Retrieve a list of cards​

Filtering and pagination​

Retrieve a specific card​

Retrieve sensitive card details​

Freeze or unfreeze cards​

Freeze a card​

Unfreeze a card​

Lock or unlock cards​

Lock a card​

Unlock a card​

Terminate a card​

Different types of cards

Create a virtual card

Idempotency

Update a card

Update card settings

Update card contacts

Update card references

Retrieve cards

Retrieve a list of cards

Filtering and pagination

Retrieve a specific card

Retrieve sensitive card details

Freeze or unfreeze cards

Freeze a card

Unfreeze a card

Lock or unlock cards

Lock a card

Unlock a card

Terminate a card