Appearance
Wallets Setup
Wallet setup controls which wallet balances exist, what they can be used for, and how they are scoped by tenant, service, currency, and payment rail.
Open Wallets -> Setup or the wallet administration workspace available to your role.
Workspace Reference
| Workspace | Open From | Main Action | Main Record |
|---|---|---|---|
| Wallet Setup | Wallets -> Setup | Create or maintain wallet | Tenant, service, currency, or rail wallet used for collections, holds, top-ups, payouts, and reconciliation. |
| Wallet Alerts | Wallets -> Setup where available | Configure alert | Low-balance, large-movement, stale-hold, or reconciliation alert. |
| Wallet Accounting | Wallets -> Setup where available | Maintain accounting behavior | Posting and control-account behavior for wallet movements. |
What To Configure
A wallet should be configured for the business context it supports.
Important attributes include:
| Attribute | Required | Meaning |
|---|---|---|
| Service or business scope | Yes | Whether the wallet belongs to the whole tenant or a specific service. |
| Currency | Yes | Currency the wallet holds. |
| Rail or provider | Required for rail-specific wallets | Mobile money, wallet rail, provider float, or other funding context where applicable. |
| Active status | Yes | Whether the wallet can be used for new activity. |
| Minimum balance alert | Recommended | Threshold used to warn finance before payouts are blocked. |
| Large movement alert | Recommended | Threshold used to flag unusually large collections or disbursements. |
| Notification behavior | Recommended | Who should receive balance, hold, or status alerts. |
| Approval behavior | Recommended | Whether top-ups, adjustments, or other wallet actions require review. |
| Accounting behavior | Recommended where posting is enabled | Whether wallet movements create accounting entries and which setup controls them. |
Tenant Wallets And Service Wallets
| Wallet Scope | Use It When |
|---|---|
| Tenant wallet | Funds are managed centrally for the whole tenant. |
| Service wallet | Funds must be separated by operating service, business line, or reconciliation owner. |
| Rail wallet | Funds must be separated by provider rail, such as Airtel Money or MTN MoMo. |
If a tenant has service-specific operations, avoid using one combined wallet unless finance has explicitly approved consolidated funding.
Currency And Rail Matching
Wallet-funded payments require matching context.
Before activating a wallet, confirm:
- wallet currency matches expected payout or collection currency
- mobile money rail matches the provider used by payment instruments
- service scope matches the payment batch or collection workflow
- top-up currency matches wallet currency
- settlement review will use the same channel and rail context
Alerts And Notifications
Wallet alerts help prevent operational failures.
Useful alert types include:
- low balance
- large collection
- failed disbursement
- stale hold
- hold expiry
- settlement completed
- reconciliation drift
Configure alerts so finance users know about funding problems before large payout runs begin.
Top-Up Readiness
Before users request wallet top-ups, define:
- who can request a top-up
- who can approve a top-up
- what evidence is required
- which wallet or service wallet receives the funds
- which currencies are allowed
- how duplicate requests are detected
- how reconciliation will confirm the funds
Accounting Readiness
Wallet movements can affect accounting when configured.
Before enabling automatic posting, confirm:
- wallet funding account is mapped
- provider or rail float account is mapped
- fee or commission treatment is clear
- reversal and adjustment treatment is clear
- control-account tracking is available where required
- finance has tested top-up, hold, settlement, and reversal scenarios
Setup Checklist
Before wallet-funded payouts are used:
- Create the wallet for the correct tenant or service.
- Confirm currency and rail.
- Confirm the wallet is active.
- Configure alerts and notification owners.
- Confirm top-up approval responsibilities.
- Confirm accounting mappings.
- Test a small controlled payout or top-up flow.
- Review reconciliation output before high-volume use.