Configuring Retail Fees
Recovery of fees is an important aspect of any fintech proposition: what a tenant charges their customer can differentiate their services. Eclipse has a highly flexible fees engine that supports a range of fee options.
Self service simple fee configuration
Eclipse supports a range of simple to configure fees for all withdrawal, payment and top up services. Tenant configs related to fees that can be configured through the admin portal are:
fees.wallet.config.{Wdr|Pay}.{TransactionType} - this is the wallet ID where the fees should be collected
fees.amount.config.{Wdr|Pay}.{TransactionType} - this determines the fee logic
Self service fee logic covers:
- Fixed cost fee - e.g. 5A
- Fee based on % of base amount e.g 2P
- A combination of fixed cost + % fee e.g. 2A,0.3P
Fees can also be rounded UP, DOWN or Bankers Round (round half-even). To specify rounding, add| where Mode is D for down, U for up and B for Bankers. E.g. 2A,0.3P|2U would mean 2 + 0.3 percent rounded up to 2 decimal places.
These can be configured directly in the admin portal or with the assistance of the EFT Corporation technical team. See the Tenant Config Reference, for full details of each fee configuration.
Card specific fees
Fees and limits can be configured for a range of transaction types:
- pur: Purchase
- cwd: ATM
- pra: Pre-Auth
- pwc: Purchase with Cashback
- chb: Cashback
- cad: Cash Advanced
- bai: ATM Balance Enquiry
The following attributes can be set as tenant attributes, wallet type or wallet level.
Attributes | Description |
---|---|
fees.amount.config.{transaction_type}.{domestic/international} | Fees charged for different transaction types and for domestic and international transactions |
postilion.{transaction_type}.{domestic/international}.debitCardMonthlyTransactionLimit | Monthly transaction limit per transaction type |
postilion.{transaction_type}.{domestic/international}.debitCardPerTransactionLimit | Per transaction limit per transaction type |
postilion.{transaction_type}.{domestic/international}.debitCardDailyTransactionLimit | Daily transaction limit per transaction type |
postilion.{transaction_type}.{domestic/international}.debitCardDailyTransactionVelocityLimit | Daily velocity limit per transaction type |
debit.decline.transaction.fee | Fees are charged for different transaction types when a decline occurs |
Note:
Transaction Limits must be set as individual Wallet Type Configuration Parameters. The limits can not exceed any limit that may be set at the Wallet Type level or Tenant level.
All corresponding transaction types require a configuration to be set for the destination wallet and fees wallet to credit when transactions are successful:
Attributes | Description |
---|---|
source.wallet.config.postilion.ref | Wallet to debit when a refund (REF) is done |
destination.wallet.config.postilion.{transaction_type} | Wallet to credit when a transaction is successful |
fees.wallet.config.postilion.{transaction_type} | Wallet to credit with fees when a transaction is done |
Advanced fee configuration
In addition to this, custom fee models can be configured including:
- tiered models
- Inter tenant and cross tenant transfers dependent on wallet types β e.g. a tenant want to charge to transfer from digital to card wallets, but not from digital to digital wallets.
- Monthly wallet fees and activation or KYC fees.
- Complex fee augmentation β e.g. once a fee is determined a tenant want to split it across different wallets for transaction fees and tax fees.
- Event based charging for ad hoc events
For more details on advanced fee configuration please refer here.
Fee hierarchy
Fees can be set on the following levels:
- Wallet
- Wallet Type
- Tenant
Fee Priority
When determining which fee configuration applies, Eclipse follows a priority order:
Wallet β Wallet Type β Tenant. The table below outlines the logic.
Tenant | Wallet Type | Wallet | Fee Based On |
---|---|---|---|
Yes | No | No | Tenant |
Yes | Yes | No | Wallet Type |
Yes | Yes | Yes | Wallet |
Updated 4 days ago