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.
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.