Skip to main content
Fee Packages are the base unit of the Fees Engine. Each package defines a set of fee rules and the conditions under which they apply to Transactions.
Enable the Fees Engine in Midaz module settings before you use this page.

​
What a Fee Package contains

A Fee Package lets you:
  • Define fee calculation rules — flat fees, percentage-based fees, or combined calculations.
  • Set amount ranges — apply fees only to transactions within a min/max range.
  • Link to transaction routes — target specific transaction flows.
  • Waive fees for specific accounts — exempt selected source accounts.
  • Prioritize fee application — control the order in which Fees Engine applies multiple fees.
Fee Packages combine with Accounting Routes and Segments for granular control.

​
Accessing the Fee Packages page

In the Midaz Module sidebar, expand Fees Engine. Select Fee Packages. The page lists every configured package.
If you have no Fee Packages, the list is empty and shows a prompt to create your first package.

​
Available actions

From the Fee Packages page, you can:

Create a Fee Package

Define new fee calculation rules for transactions

Edit a Fee Package

Update fee configurations and rules

Delete a Fee Package

Delete a fee package from your configuration
Select a package from the list to open its details view. There you can review the package’s configuration — type, scope, and rules — before you edit it. To preview the fees a period generates across packages, use Billing Runs.

​
Understanding Fee Package structure

When you create or edit a fee package in Midaz Module, you work with these fields:

​
Basic information

  • Fee Group Label (required) - A descriptive name for the fee package
  • Description (optional) - Explanation of the package purpose and when it applies
  • Transaction Route (optional) - Link to a specific transaction route
  • Segment (optional) - Associate with a specific segment
  • Ledger (required) - The ledger this package applies to

​
Amount range

  • Minimum Amount (required) - Lowest transaction amount for fee application
  • Maximum Amount (required) - Highest transaction amount for fee application
  • Waived Accounts (optional) - List of account aliases exempt from these fees

​
Fee rules

Each fee package can contain multiple fee rules with:
  • Fee Label - Name that identifies this fee
  • Application Rule - How Fees Engine calculates the fee:
    • flatFee - Fixed amount regardless of transaction value
    • percentual - Percentage of the transaction amount
    • maxBetweenTypes - Higher value between flat and percentage calculations
  • Calculation Type - flat or percentage
  • Calculation Value - The fee amount or percentage
  • Reference Amount - Base for percentage calculation:
    • originalAmount - Calculate on the original transaction value
    • afterFeesAmount - Calculate after Fees Engine applies other fees
  • Priority - Order of fee application (lower numbers apply first)
  • Is Deductible From - Whether Fees Engine deducts this fee from the transaction
  • Credit Account - Account that receives the fee amount

​
Common use cases

Apply a fixed fee to all transactions within an amount range:
  • Application Rule: flatFee
  • Calculation: flat with value 2.50
  • Example: 2.50feeoneverytransactionbetween2.50 fee on every transaction between 10 and $1000
Charge a percentage of the transaction amount:
  • Application Rule: percentual
  • Calculation: percentage with value 1.5
  • Example: 1.5% fee on transfers, where 100transfer=100 transfer = 1.50 fee
Create multiple packages with different amount ranges:
  • Package 1: 0−0-100 → 2% fee
  • Package 2: 100−100-1000 → 1.5% fee
  • Package 3: $1000+ → 1% fee
  • Lower fees for higher-value transactions
Apply whichever is higher between flat and percentage:
  • Application Rule: maxBetweenTypes
  • Calculations: flat: 1.00 and percentage: 2.0
  • Example: On 30transaction:max(30 transaction: max(1.00, 0.60)=0.60) = 1.00 fee
  • Example: On 100transaction:max(100 transaction: max(1.00, 2.00)=2.00) = 2.00 fee
Exempt specific accounts from fees:
  • Create package with standard fee rules
  • Add premium account aliases to Waived Accounts list
  • These accounts transact without the configured fees

​
Best practices

1

Plan your fee structure

Design your fee packages before implementation. Consider transaction types, amount ranges, and customer segments that require different fee treatments.
2

Use descriptive labels

Choose clear fee group labels and descriptions that explain when and why fees apply. This helps with auditing and customer communication.
3

Set appropriate amount ranges

Define minimum and maximum amounts carefully to avoid gaps or overlaps in your fee structure.
4

Test fee calculations

Use the Fee Estimation feature to preview fee calculations before you enable packages in production.
5

Manage priority carefully

When you use multiple fees in a package, set priorities so the fees apply in the correct order.
6

Document waived accounts

Record why you waive fees for certain accounts. This supports audit and compliance.

​
Fee calculation flow

When Fees Engine processes a transaction, it:
  1. Identifies applicable fee packages based on transaction route and segment
  2. Filters packages by amount range (transaction must fall within min/max)
  3. Checks whether the account is in the waived accounts list
  4. Applies fee rules in priority order
  5. Calculates each fee based on application rule and reference amount
  6. Credits fee amounts to designated accounts
Enable a fee package so it applies to transactions. To pause a package, disable it. A disabled package stays in your configuration.