Set Card BIN Spend Controls

post

https://api-sandbox.interlace.money/open-api/v3/consumption-scenarios

Sets or updates spend controls that define whitelist/blacklist consumption scenarios and MCC rules for determining which transactions are permitted or restricted.
The configured controls apply to all applicable cards once updated.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Scope of Application

When only cardBinIds are specified, the whitelist/blacklist restrictions apply to all cards under the corresponding BINs.
When only cardIds are specified, the whitelist/blacklist restrictions apply only to the specified cards.
When both cardBinIds and cardIds are specified, the whitelist/blacklist restrictions apply to the union of the cards matched by the specified BINs and the specified card IDs.

In MOR mode, whitelist/blacklist restrictions are configured at the account level by default.
In GATEWAY mode, whitelist/blacklist restrictions can be configured at the sub-account level by specifying the accountId field. If accountId is not provided, the restrictions are configured at the master account level by default.

Body Params

Card Consumption Label Upsert Blacklist Or Whitelist Item

usage

string

required

usage: MCC,SCENARIO,TRANSACTION_CURRENCY, if id is null then usage can not be null

keywords

string

required

keywords, if usage is MCC, then keywords must be 4 digits string,
if usage is TRANSACTION_CURRENCY, then keywords must be 3 digits currency code
if usage is SCENARIO, then keywords must be substring of transaction detail info

int64

id ,if null then insert ,if not null then update

listType

string

required

list type: BLACKLIST,WHITELIST

cardBinIds

array of strings

card bin id list, if null then all card bin will be applied

cardBinIds

cardIds

array of strings

card id list

cardIds

accountId

string

account id

Headers

Idempotency-Key

string

required

Universally unique identifier idempotency key. This key is utilized to ensure exactly-once execution of mutating requests.

Responses

Scope of Application

200OK

400Bad Request