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.

Common fees

The tables below list the fees most tenants configure, grouped by mechanism. Example values are illustrative — set your own for each fee. Some fees are configured with the simple fees.amount.config string syntax; others need a small piece of custom Java logic attached to a wallet type or a retail billing event. The See column links to the section that explains the relevant mechanism.

Wallet funding fees

Wallet withdrawal fees

Card transaction fees

Recurring & lifecycle fees

These are configured with a small piece of custom Java logic attached to a wallet type, rather than the fees.amount.config string syntax.

📘

Note:

Several rows share the same configuration attribute (sendTransferLogicSetId/receiveTransferLogicSetId) — the attribute only attaches a wallet logic set to a wallet type. What that logic set actually does (charge a P2P fee, a cross-tenant fee, a KYC fee, or something else) is determined entirely by the custom Java logic written into it.

Card lifecycle & notification fees

These are triggered by a retail billing event rather than a transaction.

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:

1. Fixed cost fee - e.g. 5A
2. Fee based on % of base amount e.g 2P
3. 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.

self service fees can also be configured based on any event generated by Eclipse with similar logic above.

fees.wallet.config.{EventType} - this is the wallet ID where the fees should be collected

fees.amount.config.{EventType} - this determines the fee logic

📘

Note:

To use event type fees, a matching entry must be created in the retail billing config for each event type. Contact your EFT Corporation account manager to configure event-based fee entries.

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.

📘

Note:

Per-transaction-type limits (monthly, per-transaction, daily, and daily velocity) are also configurable for these card transaction types — see Limit Configuration for the postilion.{transaction_type}.domestic.debitCard*Limit attributes.

All corresponding transaction types require a configuration to be set for the destination wallet and fees wallet to credit when transactions are successful:

FX markup fee

For card transactions where the transaction currency differs from the wallet's currency, Eclipse can apply an additional FX markup fee on top of any standard transaction fee. This is configured with the wallet type attribute:

internationalMarkUpFees - the fee logic (using the same fixed/percentage/combined syntax as other fees) applied to cross-currency card transactions

This is a separate mechanism from fees.amount.config, and only applies when the transaction is identified as international and the transaction currency differs from both the wallet currency and the settlement currency.

Fees on reversed transactions

By default, a fee charged on a transaction is not automatically reversed if the transaction itself is reversed. To allow fee reversal, set the following wallet type attribute:

feesReversalAllowed=true

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.

Permissions Required