Business API
Create a card
api
post
/cards

Create a card

Create a new card for an existing member of your Revolut Business team.

When using the API, you can create only virtual cards. To create a physical card, use the Revolut Business app.

note

This feature is available in the UK, US and the EEA.

This feature is not available in Sandbox.

To use the Cards API, please contact Revolut API Support.

For more information, see the guides: Manage cards.

Access Token​

Each Business API request must contain an authorization header in the following format to make a call: Bearer <your_access_token>.

The access token will be obtained the first time you set up your application and has an expiration of 40 minutes. During setup, a refresh_token will also be obtained which allows to obtain a new access_token.

danger

Never share your client-assertion JWT (JSON web token), access_token and refresh_token with anyone, as these can be used to access your banking data and initiate transactions.

Access tokens can be issued with four security scopes and require a JWT (JSON Web Token) signature to be obtained:

  • READ: Permissions for GET operations.

  • WRITE: Permissions to update counterparties, webhooks, and issue payment drafts.

  • PAY: Permissions to initiate or cancel transactions and currency exchanges.

  • READ_SENSITIVE_CARD_DATA: Permissions to retrieve sensitive card details.

    caution

    If you enable the READ_SENSITIVE_CARD_DATA scope for your access token, you must set up IP whitelisting. Failing to do so will prevent you from accessing any Business API endpoint.

    IP whitelisting means that you must specify an IP or a set of IPs which will be the only IPs from which requests to the API will be accepted. To do so:

    1. In the Revolut Business app, select the corresponding API certificate.
    2. In Production IP whitelist, provide the IP(s) which should be whitelisted, and save.

To configure your JWT and obtain the refresh and first access tokens, complete the following steps:

  1. Sign up for a Revolut Business account
  2. Prepare your Sandbox environment
  3. Make your first API request

Request​

Request body
Body object

Possible values: <= 40 characters

A unique ID of the request that you provide.

There is no strict requirement on the format of this ID, but we suggest using v4 UUIDs.

caution

This ID is used to prevent duplicate card creation requests in case of a lost connection or client error, so make sure you use the same request_id for requests related to the same card. The deduplication is limited to 24 hours counting from the first request using a given ID. For more information, see the guides: Manage cards - Idempotency.

Possible values: [true]

Specifies the type of the card. Must be set to true, as with the API, you can create only virtual cards.

tip

To create a physical card, use the Revolut Business app.

The ID of the team member who will be the holder of the card. To retrieve the holder's ID, use the GET /team-members operation.

Possible values: <= 30 characters

The label for the issued card, displayed in the UI to help distinguish between cards. If not specified, no label will be added.

The list of accounts to link to the card. If not specified, all accounts will be linked. To retrieve account IDs, use the GET /accounts operation.

Possible values: [health, general, services, airlines, transport, accommodation, utilities, shopping, financial, furniture, hardware, groceries, fuel, entertainment, software, restaurants, advertising, cash, education, government]

The list of merchant categories to be available for card spending. If not specified, all categories will be allowed.

All spending limits set for the card.

You can have at most 1 periodic (day/week/month/quarter/all-time) and 1 non-periodic (single transaction) limit at a time. If you try to specify 2 periodic limits at a time, it will result in an error.

Spending limit currency must match the default business currency. The default currency was assigned to your business during onboarding.

The limit for a single transaction.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The daily limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The weekly limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The monthly limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The quarterly limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The yearly limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The all-time limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

Response​

Information about the card

Response body
Body object

The ID of the card.

Possible values: Value must match regular expression ^[0-9]{4}$

The last 4 digits of the card's PAN.

Possible values: Value must match regular expression ^[0-9]{2}/[0-9]{4}$

The card expiration date.

Possible values: [created, pending, active, frozen, locked]

The state that the card is in.

The label of the card.

Specifies whether the card is virtual (true) or physical (false).

The list of linked accounts.

Possible values: [health, general, services, airlines, transport, accommodation, utilities, shopping, financial, furniture, hardware, groceries, fuel, entertainment, software, restaurants, advertising, cash, education, government]

The list of merchant categories that are available for card spending. If not specified, all categories will be allowed.

All spending limits set for the card.

The limit for a single transaction.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The daily limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The weekly limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The monthly limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The quarterly limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The yearly limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The all-time limit for transactions.

The value of the spending limit.

Possible values: Value must match regular expression ^[A-Z]{3}$

The currency of the transaction limit, provided as the ISO 4217 code in upper case.

The ID of the team member who is the holder of the card. If the card belongs to the business, this will be empty.

For more information, see the guides: Manage Cards - Create a virtual card.

The date and time the card was created in ISO 8601 format.

The date and time the card was last updated in ISO 8601 format.

Was this page helpful?
Loading...