In this set of examples, you can learn how to create a counting and summing group to set up tiered pricing in card price lists. You will find the excerpt of transaction group parameters to know when managing the counting and summing groups, followed by links to associated example API calls.
Transaction group parameters
transactionGroupingCode: Unique transaction grouping code.
Note: Must contain only upper case letters, numbers and underscores. Must start with a letter and not end with underscore. Double underscores are not allowed.
groupingType: Possible values SUM, COUNT
SUM - transaction amounts are aggregated
COUNT - transactions are counted
aggregationLevel: Defines the length of the aggregation period. Possible values MONTHLY, YEARLY
MONTHLY - Aggregation is restarted when the first transaction is received at the beginning of the new calendar month.
YEARLY - Aggregation is restarted when the first transaction is received at the beginning of the new calendar year.
aggregationScope: Possible values ACCOUNT, CARD
ACCOUNT - aggregated amount is calculated based on all cards related to one and the same account
CARD - Aggregated amount per card. Calculation is reset when card is replaced or renewed.
includeReservations: Flag indicating whether transaction is counted already when authorisation message is received or not.
true - Transactions are aggregated when authorisation is approved.
false - Transactions are aggregated when clearing data is processed.
enabled: A flag indicating whether this transaction grouping rule is currently active or not.
transactionTypeCodes: A list of transactions types that needs to be aggregated.
