Card Usage

Welcome to the Aurora Behaviours Card Usage Solution.

These pages explain how Card Usage parameters work within the Aurora Behaviours module, how to configure them for your programme, and how they are enforced when your cardholders make transactions.

Card Usages typically give you control over which transaction types and actions a cardholder can perform. For example; allowing ecomm transactions, allowing ATM PIN changes etc

Card Usages are managed through the Vista administration portal or via the API.

A set of Card Usage parameters will form a part of the Behaviours rules linked to the Product level for the programme. When a card is created, it is automatically associated with the default Behaviour configured for that Product. You can define multiple Behaviours for a Product and assign them to individual cards as needed.

Card Usage values can be managed at two levels:

• Product / Behaviour level - Changes apply to all cards associated with that Behaviour, except where a card-level override has been set.
• Card level - A bespoke value set directly on a specific card, which takes precedence over the Behaviour-level setting for that card.

If you change the value of a Card Usage within a Behaviour for a Product, this applies to newly created cards only. Existing cards retain their current Card Usages settings and must be updated individually using the Set Behaviour API.

At the point of authorisation, CLOWD9 evaluates each relevant Card Usage parameter against the incoming authorisation request. Based on the configured value, CLOWD9 will either approve the transaction (subject to all other authorisation rules) or decline it as not permitted.

All authorisations are subject to all authorisation rules within a Behaviour and so passing a Card Usage check doesn't guarantee an approved authorisation it means the transaction type is permitted and will proceed on through the normal authorisation flow.