Authorization controls allow you to specify rules around how and where the cards you issue may be used. You can specify them at the time of creating a new card or later when you update the card.
Choose authorization controls that best suit your needs. Note that some are mandatory.
|I want to...||Recommended authorization control||Parameter||Supported endpoints|
|Specify whether the card is a ||Transaction count||Create a card API|
|Specify the currencies that can be used to process transactions on the card. If you do not specify this field, all currencies will be allowed.||Currency||Create a card API/Update a card API|
|Specify the allowed merchant categories codes where the card can be used. Merchant Category Code (MCC) is a unique identifier for the type of goods or services provided by merchants. If you do not specify this field, all merchant categories will be allowed. See list of merchant category codes in the ISO 18245 standard.||Merchant category code||Create a card API/Update a card API|
|Specify the activity range for the card. Authorizations before and after the time period will be rejected.||Time period||Create a card API /Update a card API|
|Specify transaction limits for the card based on amount and intervals. This control is mandatory -- you can configure multiple transaction limits based on a single currency. For more information, see Transaction limits.||Transaction limit||Create a card API / Update a card API|
|Configure advanced authorization control where the authorization request from the merchant’s bank is sent to my nominated endpoint and I can decline or accept the authorization based on my own fraud rules. For more information, see Remote authorization.||Remote authorization||Get issuing config API / Update issuing config API|