Aurora Behaviour Management

Welcome to the Aurora Behaviours Management solution.

These pages explain how the Aurora Behaviours Management module operates to manage and control your card programmes responses to card payments made by your cardholders.

The Aurora Behaviour Management solution allows you to configure and manage detailed rules that govern how the following functions will operate for the cards in your programmes :

These sets of rules are set up within one or more Behaviours.

A Behaviour is a collection of settings including limits, fees, card usage controls and list based rules that can be attached to a card programme. They determine the functional characteristics of the usage of the card. In general they map to the T&Cs agreed with your cardholders.

Every card is associated with a Behaviour. Cards can be moved between Behaviours as needed e.g. promotion from Silver membership to Gold. When allowed by the Behaviour individual settings within a Behaviour can be overridden at an individual card level e.g. A parent could reduce the default number of ATM transactions allowed in a week for a childs card.

In general:

Behaviours are held at the Product level, meaning all cards within a product share the same default Behaviour.
A different Behaviour can be assigned to an individual card at any time using the Set Behaviour API call or Vista.
If you change the default Behaviour at the Product level, the change applies to new cards only. Existing cards keep their current Behaviour unless you update them individually via the API.

Note that your access to set up and manage Behaviour parameters directly may be subject to prior Issuer approval. This is because Issuers may require regulatory oversight/signoff of these parameters as they affect core programme activities and cardholder Terms and Conditions etc.