Update card invitation settings

Update settings for a specific card invitation, based on its ID. You can update successfully created invitations that have not been claimed yet (state=created).

Note
  • This feature is not available in Sandbox.
  • To use the Card invitations API, please contact Revolut API Support.
Caution

Some spend control parameters can affect one another. When updating spend controls, review the resulting settings in the response to ensure they reflect the configuration you intended.

For more information, see the guides: Manage card invitations.

Request​

Path parameters
Path parameters

The ID of the card invitation.

Request body
Body any

Possible length: non-empty and <= 30 characters

Default value: Default label according to card's type

The label of the card.

Cards without labels are not allowed. If set to null, the default label will be set according to the card's type.

Default labels

For virtual cards, the default label is Virtual. For physical cards, depending on the type, it can be, for example, Standard or Metal.

As these values depend on available card types, they are subject to change over time.

Example: {"single":{"amount":200.22,"currency":"GBP"},"week":{"amount":200.44,"currency":"GBP"}}

All spending limits to be 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.

Use null as the value for a specific limit to erase that limit. Use null as the value for the spending_limits object to erase all limits.

The limit for a single transaction.

The value of the spending limit.

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

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

The daily limit for transactions.

The value of the spending limit.

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

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

The weekly limit for transactions.

The value of the spending limit.

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

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

The monthly limit for transactions.

The value of the spending limit.

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

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

The quarterly limit for transactions.

The value of the spending limit.

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

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

The yearly limit for transactions.

The value of the spending limit.

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

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

The all-time limit for transactions.

The value of the spending limit.

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

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

The controls for the card's spending period.

They let you set or modify the dates when the card should become available or unavailable for spending, and define what happens after the end date.

If specified, you must provide at least one of these:

  • start_date
  • end_date together with end_date_action

The spending period dates must be in the future.

The dates are inclusive. This means that:

  • If you set the start_date to 2026-03-31, the card will become active on that day.
  • If you set the end_date to 2027-12-31, the card will be active through that day, and will be locked/terminated starting on 1st Jan 2028.
Note

You can update the spending period settings in a few ways, depending on your use case:

  • To remove the start date, but keep the end date settings, provide the current spending_period settings without the start_date.
  • To remove the start date when no end date is set, provide the spending_period.start_date set to null.
  • To remove all spending period settings, provide spending_period set to null.

If you wish to erase a spending period end date, you can do this in a similar way, applying the steps to spending_period.end_date and spending_period.end_date_action.

Example: "2025-09-26"

The start date (inclusive) of the spending period, in ISO 8601 format (YYYY-MM-DD). Uses the timezone set by the business, or defaults to Europe/London.

Example: "2030-12-31"

The end date (inclusive) of the spending period, in ISO 8601 format (YYYY-MM-DD). Uses the timezone set by the business, or defaults to Europe/London.

Possible values: [lock, terminate]

The action to take after the end date of the spending period.

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. Use null to erase the value and reset to empty (all categories will be allowed).

Note

The categories and merchant_controls parameters have the following restrictions:

  • If you set categories, you cannot set merchant_controls.control_type to allow.
  • You can set merchant_controls.control_type to block.
  • You may also set either categories or merchant_controls independently, or set neither.
  • Both parameters can be used together only if merchant_controls.control_type is block.

The merchant-level controls for card spending.

They let you block or allow the card to only transact with specific merchants:

  • allow: permits only the specified merchants (cannot be used if the categories parameter is set).
  • block: blocks the specified merchants (can be used with or without categories).

Possible values: [block, allow]

The type of control to apply.

Possible number of items: non-empty and <= 20 items

The list of IDs of merchants to which the control applies.

Tip

To find merchant IDs, check transaction details (→ merchant.id). You can fetch transaction details for a specific transaction or for all transactions.

Pattern: Value must match regular expression ^[A-Z]{2}$
Example: "GB"

The list of countries where the card can be used, provided as 2-letter ISO 3166 codes.

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.

Response​

Information about the updated card invitation

Response body
Body object

The ID of the card invitation.

Possible values: [created, expired, failed, redeemed]

The current state of the card invitation:

  • created: Invitation has been created but not yet claimed.
  • expired: Invitation has expired due to expiry date being reached or manual cancellation.
  • failed: Invitation claim attempt failed.
  • redeemed: Invitation has been successfully claimed.

To learn more about card invitation lifecycle, see the guide: Manage card invitations → Card invitation state.

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

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

Example: "2025-10-20T15:09:24Z"

The date and time after which this card invitation expires if not claimed or cancelled before then. Specified in ISO 8601 format.

Note

Only returned for invitations in state created.

Tip

For other states, to find out when a card invitation transitioned to its final state, check the updated_at value.

The ID of the team member to be assigned as the holder of the card after the invitation is claimed.

Specifies whether the issued card will be a virtual (true) or physical (false) one.

The label of the card.

The spend program assigned to the card.

Note

To use this property, please contact Revolut API Support.

Possible length: <= 30 characters

The name of the spend program.

Example: {"single":{"amount":200.22,"currency":"GBP"},"week":{"amount":200.44,"currency":"GBP"}}

All spending limits set for the card.

The limit for a single transaction.

The value of the spending limit.

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

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

The daily limit for transactions.

The value of the spending limit.

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

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

The weekly limit for transactions.

The value of the spending limit.

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

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

The monthly limit for transactions.

The value of the spending limit.

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

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

The quarterly limit for transactions.

The value of the spending limit.

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

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

The yearly limit for transactions.

The value of the spending limit.

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

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

The all-time limit for transactions.

The value of the spending limit.

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

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

The controls for the card's spending period.

They specify the dates when the card will become available or unavailable for spending, and define what happens after the end date.

Example: "2025-09-26"

The start date (inclusive) of the spending period, in ISO 8601 format (YYYY-MM-DD). Uses the timezone set by the business, or defaults to Europe/London.

Example: "2030-12-31"

The end date (inclusive) of the spending period, in ISO 8601 format (YYYY-MM-DD). Uses the timezone set by the business, or defaults to Europe/London.

Possible values: [lock, terminate]

The action to take after the end date of the spending period.

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 will be available for card spending.
If this parameter is not specified, categories are not restricted.

The merchant-level controls for card spending.

They block or allow the card to only transact with specific merchants:

  • allow: permits only the specified merchants (cannot be used if the categories parameter is set)
  • block: blocks the specified merchants (can be used with or without categories)

Possible values: [block, allow]

The type of control to apply.

Possible number of items: non-empty and <= 20 items

The list of IDs of merchants to which the control applies.

Tip

To find merchant IDs, check transaction details (→ merchant.id). You can fetch transaction details for a specific transaction or for all transactions.

Pattern: Value must match regular expression ^[A-Z]{2}$
Example: "GB"

The list of countries where the team member will be able to use the card. Specified as 2-letter ISO 3166 codes.

The list of accounts that will be linked to the card.
Was this page helpful?