Behaviours

CLOWD9 builds products that will exhibit one or more Behaviours.

A Behaviour is a set of Criteria and their associated Actions that define, control, limit or trigger various operations/functions against an activity initiated by a card or account. For example a Behaviour may be set up to enforce the T&Cs associated with the card product they are using, max loading value, max number of ATM, regional restrictions etc.

A Criteria is a rule against which an event can be measured or tested and which may trigger an Action. For example a Criteria may be set to allow a maximum number of ATM transactions within a set period.

An Action is the operation to be taken in the event that a Criteria rule is met or exceeded. For example if the maximum number of ATM transactions within a set period is exceeded the Action triggered is to Decline the authorisation request.

In general a Behaviour is a set of Criteria and associated Actions that are designed to ensure that the card product operates in line with the Terms and Conditions that have been agreed between the individual Customer, the Programme Manager and the Issuer or in line with controls and restrictions that the Issuer may require of the product.

For example a Behaviour might comprise the following set of Criteria and Actions:

• Criteria 1
  • Criteria: Number of ATM transactions allowed within a predetermined period : 3 ATM per day
  • Action: Decline authorisation request if >3 ATM during the day
• Criteria 2
  • Criteria : Value of POS transactions within a predetermined period : GBP250 per week
  • Action : decline authorisation if amount would exceed GBP250 during the week
• Criteria 3
  • Criteria : charge fee if an authorisation is for an International ATM
  • Action : assess a GBP3:00 fee
• Criteria 4
  • Criteria : Do not allow e-comm activity
  • Action : Decline
• Criteria 5
  • Criteria : Maximum value of value loading within a predetermined period : GBP1000 per month
  • Action : Decline load request if amount would exceed GBP1000 during the month.
• Criteria 6
  • Criteria : Prevent spend in specified countries : Russia
  • Action : Decline authorisation request if originated in Russia

It is possible to create multiple Behaviours within a Product. For example within a Product there may be Standard cardholder and VIP cardholder Use Cases. The Criteria and Actions might be different for the different Use Case Behaviours. For example:

Standard Cardholder Behaviour

• Criteria 1
  • Criteria: Number of POS transactions allowed within a predetermined period : 3 POS per day
  • Action: Decline authorisation request if >3 POS during the day
• Criteria 2
  • Criteria : Do not allow ATM
  • Action : Decline

VIP Cardholder Behaviour

• Criteria 1
  • Criteria: Number of POS transactions allowed within a predetermined period : 15 POS per day
  • Action: Decline authorisation request if >15 POS during the day
• Criteria 2
  • Criteria : Allow ATM
  • Action : no action required