It represents a balance in a specific currency and serves as the foundation for all money movement within Monime. Each account is uniquely identifiable, has a human-friendly display name (e.g., βMain Walletβ), and is always tied to a single currency such as SLE or USD. In APIs, Financial Accounts act as the source or destination of funds for transfers, payouts, or collections.
Use Cases
-
Embedded Finance
With Embedded Finance on Monime, fintechs can create dynamic wallet accounts hosted directly on Monimeβs infrastructure.
Incoming collections from cards, Mobile Money, or banks are deposited into these accounts, which can then be used for spend, cash-out, or peer-to-peer (P2P) transfers by moving funds between accounts. Example : Payments received through Checkout Sessions are credited to a userβs wallet account and can later be transferred to another userβs wallet, enabling seamless P2P experiences. -
Settlement Account
Businesses separate collected funds from the account used to settle merchants or subsidiaries.
Example: A PSP routes daily Mobile Money collections into a Settlement Account before initiating payouts. -
Disbursement Float
A pre-funded account maintained to ensure outgoing transfers and payouts can always be covered.
Example: Your platform maintains a Disbursement Float account; when it runs low, you top it up via an Internal Transfer. -
Dedicated Currency Account
Multi-currency platforms maintain one account per supported currency.
Example: A customer has both a USD Account and an SLE Account, ensuring currency isolation and easier reconciliation.
Unique identifier of the financial account.
UVAN (Universal Virtual Account Number) β a unique, checksum alias used for secure, error-resistant inbound transfers across Monime and external providers.
Human-readable label for the financial account, such as βMain Walletβ or βOperations Reserveβ.
ISO 4217 currency code (e.g., βSLEβ, βUSDβ) indicating the accountβs currency.
Optional external reference ID for this account (e.g., the accountβs identifier in your internal system). Must be unique across accounts. Useful for reconciliation, tracking, or cross-system mapping.
Optional description of the accountβs purpose or usage context.
Current available balance of the financial account.
Timestamp when the financial account was created.
Timestamp when the financial account was last modified.
Updated metadata for storing additional context about the account.