Creating tiered pricing by assigning counting and summing groups to transaction fee types in the particular price list is a new and preferred method for this activity. If you are about to create a new price list with tiered pricing, please use this method.
To add a counting group and/or summing group for transaction fee type in price list, go to:
Cards > Settings > Price lists.
Find the price list where you want to define a counting and summing groups for tiered pricing.
Click the Price list code to access the price list details.
Select the counting and/or summing group to be assigned with the fee type.
Once you have finished creating the needed counting and summing groups, you are ready to set up the tiered prices. To learn more, please refer to the following card pricing examples.
Find the fee type, scroll to the right and click the edit icon .
.
.
.
Price list code
Text
Price list name. This is predefined value.
Fee type
Text
Name of the fee. This is predefined value.
Counting group
List
Select the counting group to set up price tiers for:
count range-based pricing, or
amount range-based pricing with a count threshold.
Leave it unselected if you are about to create amount range-based pricing.
Summing group
List
Select the summing group to set up price tiers for:
amount range-based pricing, or
amount range-based pricing with a count threshold.
Leave it unselected if you are about to create count-based pricing.
The Tuum system also allows the creation of tiered prices where the price in the card price list is calculated based on cumulative reference parameter value.
Count-based tiers allow prices to be calculated depending on the cumulative number of transactions.
Amount-based tiers allow prices to be calculated depending on the cumulative amount of transactions.
Amount and count-based tiers allow prices to be calculated depending on the cumulative amount of transactions and cumulative count of transactions simultaneously.
To take advantage of the tiered pricing capability in the card price lists you need to make the following two activities.
Create summing and/or counting groups for the particular transaction type for which you would like to apply the tiered prices.
Assign summing and/or counting groups to fee type in the price list.
Creating tiered pricing by assigning counting and summing groups to transaction types is an old method that is still supported. If you create new price lists with tiered pricing, please consider using the new method, where the counting and summing groups are assigned to the fee types in the particular price list.
To assign counting and summing groups, please follow the instructions below.
Go to Cards > Settings > Transaction types.
Find the transaction in question. In our example, it is the ATM_WITHDRAWAL transaction type and enter the name of:
Counting group - for setting up a count range price list.
Summing group - for setting up a amount range price list.
Here, we highlight some critical aspects of operating with tiered prices.
When you have created the counting and/or summing group so that counting and/or summing starts from reservations (includeReservations = true), then be aware that adjustments of counting and summing amounts happen on the following occasions.
The aggregated counting and/or summing value will be decreased when the authorisation reversal related to the already counted authorisation request is approved.
The aggregated counting and/or summing value will be decreased when the account reservation is released manually or by an overdue process.
This explanation is about to clarify the following scenario.
When aggregated counting and/or summing value has exceeded the threshold, it triggers the fee calculation from the next price tier.
After that, an adjustment would decrease the aggregated counting and/or summing value below the threshold.
Consequently, the fees calculated in the events noted in point one will stand and will not be recalculated.
Creating summing and counting groups is available only through the APIs. Please refer to the in the API cookbook.
We do not provide an option in the BackOffice to find any counting or summing group's current aggregated counting and/or summing value. Please refer to the examples in the API cookbook about finding current and values.
