Card usage groups are used to control what the Cardholder is able to do with the card, as well as the various card usage fees that are charged to the cardholder. Your Card Usage Group must be entered on your Product Setup Form (PSF); your Thredd Implementation Manager will ensure these are configured on the system.
You can use the API to assign a card to card usage groups at the time of card creation and also to change the card usage group assigned to the card at a later stage if needed.
Below are the card usage groups:
|Limit Groups||Velocity limit group which restricts the frequency and/or amount at which the card can be loaded or unloaded. You can view your current Limit Groups in Smart Client.|
|Authorisation Fee Groups||Controls the card transaction authorisation fees.|
|Recurring/Scheduled Fee Groups||Controls whether a card is charged a recurring fee, such as a monthly platform fee.|
|Web Service Fee Groups||Controls the fees charged for Web service usage. Different web services can have different fees associated with them.|
|MCC Groups||Merchant Category Code (MCC) Group. The MCC is a four-digit number used by the Card Schemes to define the trading category of the merchant.|
|Usage Groups||Controls where a card can be used; for example, POS or ATM.|
|Linkage Groups||The Linkage Group set up in Smart Client controls various parameters related to linked cards; for details, check with your Implementation Manager.|
|FX Groups||Controls the rates for FX currency conversions if the purchase currency is different from the card's currency.|
|Auth Calendar Groups||Controls when authorisations on a card are allowed. You can use this option to control when the card can be used; for example, to prevent usage on weekends or out of hours.|
|Payment Token Usage Groups||Defines configuration options specific to the provisioning of a digital payment token. For details, see the Tokenisation Guide.|
Updated about 1 month ago