Agents can use the Exchange Rate option to configure exchange rates between currencies that are set up during system installation, which provide a default rate for transactions. In addition to setting up exchange rates, agents can view previous exchange rates. For example, if you change the exchange rate from USD to EUR, you see the old exchange rate in the exchange-rate history search results.

Fees and commissions are calculated for payers and payees in financial transactions, per subtransaction. However, fees and commissions are processed differently: fees are applied and charged during transaction processing; commissions are collected and settled offline in batch mode.

Financial limits are evaluated during transaction processing. During transaction initialization, payer and payee limits are checked individually.

Use the Privileges option to define the required privileges for dual approval. For example, use the Create Customers option to create a new customer-type approval configuration. Depending on the customer type, you can configure maker-checker privileges.

The Global Configuration option displays the current configuration settings for the organizational unit, customer type, and risk category. Global configurations are created during initial setup. You cannot create additional configurations; you can only edit existing configurations.

Dual approval is configured during the initial system setup; however, agents can change or add a new configuration anytime. Dual approval is a system-level configuration, so changes can affect many dual-approval processes, such as customer registration, wallet entries, and transactions. Use the Find Pending Approval option to see any pending tasks associated with the dual-approval configuration.

Use the Restrictions option to configure rules that restrict transaction processing for payers and payees, based on their transaction history. A restriction first determines whether it applies to the current transaction, then it accumulates historical transaction data and checks for restriction violations.

Service packages enable features for a specific customer type or class. Customers can inherit roles and privileges through service packages, as well as through their customer type and risk category. A service package is valid for an organizational unit and customer type. Service packages are assigned when a consumer is registered, either self-assignment in the portal, or through a call-center agent. Some service packages can be assigned multiple times to a single customer.

Credential policies define the rules for composing credentials, such as the minimum and maximum length of a password or PIN. Credential policies also define the number of times a credential can be used, the number of allowable authentication failures, and the time range during which the credential is valid. You can add new policies, and edit and remove existing policies.

Interest Configuration is used to apply interest to balances on stored value accounts (SVAs), which is similar to how interest is calculated for regular bank accounts. Interest is calculated for each SVA, based on the balance at the end of a calculation period. You can configure various interest schemes, and group them into products; products can be mapped to an SVA, based on the organizational unit, customer type, and payment instrument type.

The general ledger (GL) account tree can replicate the GL account structure of an enterprise.