Change Card Controls

Updates card controls for a single card. If the card control does not exist, it will be created. If the card control exists, it will be updated with the given values. Thus when updating, you have to provide all the values for the card control you want to set. Missing or not provided values are deleted if they exist.

Path Params
uuid
required

The unique identifier of the card.

Body Params
categories
object | null
merchants
object | null
dates
object | null
times
object | null
locations
object | null
countries
object | null

Optional object defining country-based transaction restrictions.
You can configure cards to either allow transactions only in specified countries (whitelist)
or block transactions in specified countries (blacklist).
Country codes must be valid ISO 3166-1 alpha-3 codes (e.g., DEU, AUT, USA).
This control is not available for US-issued cards.

currencies
object | null

Optional object defining currency-based transaction restrictions.
You can configure cards to either allow transactions only in specified currencies (whitelist)
or block transactions in specified currencies (blacklist).
Currency codes must be valid ISO 4217 codes (e.g., EUR, GBP, USD).

acceptanceMethods
object | null

Optional object defining which acceptance methods are permitted.
This control is an allow-list only. restriction must be ALLOWED.
The methods in values are the only ones permitted; every other method is declined.
There is no block-list. Do not send BLOCKED: it is not applied, and the methods in values are stored as the allowed set.

Responses
204

No Content. The card controls are saved when this response is returned.

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Choose an example:
application/json