Quota-like attributes are split into two major groups:
- “#transactions_xxx_xxx_xxx": attributes that will deal with the number of transactions
- "#transactions_amount_xxx_xxx_xxx“#": attributes that will deal with the amount of transactions
These attributes may be more or less precise, which means they can be completed by status, entities, and by temporality (none of these aspects are mandatory).
Status
Eenables to differentiate successfully performed and aborted transactions.
The syntax of this aspect is as follows: succeeded or not_succeeded.
Examples:
- #transaction_amount_not_succeeded represents the sum amount of aborted transactions.
- #transaction_succeeded represents the number of successful transactions.
Entity
Enables to divide the attribute by entity. An entity is a card, a customer or an IP address.
The syntax is as follows: per_card, per_customer, per_ip.
Examples:
- #transactions_per_card represents the number of transactions by card
- #transactions_succeeded_per_customer represents the number of successful transactions by customer
- #transactions_amount_not_succeeded_per_ip represents the sum amount of aborted transactions by IP address
Temporality
Enables to add a temporality indicator to attributes.
The syntax is as follows: hourly, daily, weekly, monthly, rolling_hour, rolling_day, rolling_week or rolling_month.
Example:
- #transaction_hourly represents the number of transactions per hour
- #transaction_amount_rolling_day represents the sum amount of transactions by rolling days
- #transaction_succeeded_rolling_month represents the number of successful transactions by rolling months
- #transaction_amount_succeeded_per_customer_rolling_hour represents the sum amount of successful transactions by customer by rolling hours