Appendix C: Usage Groups

The table below describes the different types of Card Acceptance Methods available in the form of Usage groups. Rules can be set to dictate levels of Card Acceptance, such as MCC Group acceptance.

You can edit the card usage groups using the APIs.
- For the REST APIs, this is the List Card Control Groups and Update Card Control Groups endpoints.
- For the Web Services SOAP APIs, this is the Ws_Card_Change_Cardacceptor_List and Ws_Card_Change_Groups.
For more information, read Managing Card Usage Groups in the Cards API website and Card Change Acceptor List and Card Change Groups in the Web Services Guide.

Group Type	Purpose
Card Acceptor List	You can specify at the merchant ID level where authorisations are accepted (based on DE42). For example, you can allow a card to be used only in specific shops or locations. This can be applied via web services. Note: If you select a merchant ID level from the Card Acceptor List drop-down, you cannot select one from the Card Disallow List drop-down. Merchants not listed in the Allow list are automatically classified as Disallowed.
Card Disallow List	You can specify at the merchant ID level where authorisations are declined (based on DE42). For example, you can prevent a card from being used in specific shops or locations. This can be applied via web services. Note: If you select a merchant ID level from the Card Disallow List drop-down, you cannot select one from the Card Acceptor List drop-down.
Card FX Group	You can upload and manage your own Foreign Exchange rates which can be applied to authorisations and presentments.
Calendar Group	You can restrict card acceptance based on specific time and date parameters. For example, a trucking company may restrict card use to weekdays from 9 until 5 to allow employees to pay for fuel. Some usage cases include religious observances or working hours.
Card Linkage	Used to link primary and secondary cards. You can apply card linkage on a shared balance or a separate balance.
Group Usage	You can apply the specific “Card Usage Rules” which dictate card behaviour such as PAN entry method rules, cardholder verification, regional based rules and transaction types. Check the usage rules if a card has been declined. For example, to show if transactions are prevented from going through on an unknown acceptance method.
Group MCC	You can allow or disallow card acceptance (auths) based on one or more merchant category codes (MCC). For example, you can disallow gambling sites.
Group Limit	Displays specific limits assigned to that card. For example, the maximum balance permitted to be held on the card.
Group Web	You can charge a fee for specific web services such as a PIN change request.
Recurring Fee	You can apply fees based on rules or actions you set on the card. For example: inactivity fees and / or dormancy fees. These are configured by Thredd.
Group Auth	You can apply a fee to Authorisations based on the processing code. For example, an authorisation to check a balance.
Limited Network	You can restrict card acceptance to a limited network only. For example, a gift card may be limited to merchants in a particular shopping centre only. This rule is based on 3 different data elements: DE42 – Merchant ID DE43 – Address, text field for the merchant ID DE61 – Postcode
Payment Token Usage Group	Defines configuration options specific to the provisioning of a digital payment token. For more information, read the Tokenisation Guide.