Wallet System
Your app is growing. Keep every balance clear.
A delivery-platform example: create user wallets, authorize an internal transfer, then check updated balances and history. Wallet service activation is required.
Wallet infrastructure for developers
Your application. Your experience. Clear user balances.
Build wallet features into your own platform. Create user wallets, authorize internal transfers and keep balances and transaction records in view with the MeSomb Wallet API.
Wallet service activation and provider credentials are required. Contact us to confirm your setup.
Built into your product
The wallet engine behind your application.
You design the customer experience and business rules. Your server uses the Wallet API to manage user wallets and record their activity.
Create user wallets
Create and retrieve wallets for the users of your service, with wallet identifiers and account details.
Move value internally
Initiate transfers between wallets in your service after your application checks and authorizes the operation.
Keep balances traceable
Retrieve wallet balances and transaction history, including transaction status and balance after an operation.
A delivery-platform example
One delivery. Two wallets. A clear record.
A customer has a funded wallet. Once your application authorizes payment for a completed delivery, it requests an internal transfer to the courier’s wallet and checks the result.
Illustrative balances for an internal transfer. Funding, external collections and withdrawals are separate workflows to configure for your service; this example is not a pricing quote.
Example internal transfer
3,000 FCFA
| Wallet | Before | After |
|---|---|---|
| Customer | 10,000 FCFA | 7,000 FCFA |
| Courier | 2,000 FCFA | 5,000 FCFA |
Server-side integration
Connect the API. Keep your rules in control.
- 1
Activate your wallet service
Discuss your use case with MeSomb and obtain the provider credentials for your configured service.
- 2
Build and authorize on your server
Use the SDK or API to create wallets and request transfers. Keep credentials private and validate permissions and business rules before sending requests.
- 3
Check results and keep records
Read transaction results, retrieve balances and review wallet history to support your application’s follow-up and reconciliation.
JavaScript SDK · illustrative server-side excerpt
// Server-side excerpt: configured WalletOperation client
await walletClient.transferMoney(customerWalletId, courierWalletId, 3000);
const wallet = await walletClient.getWallet(customerWalletId);
const history = await walletClient.listTransactions(1, customerWalletId);Uses @hachther/mesomb with an already configured WalletOperation client. The wallet IDs are placeholders. Do not expose provider credentials or secret keys in browser code.
Before you integrate
Is this a wallet app my customers must install?
No. This is an API-based wallet service for developers. You build the user experience inside your own application and connect it to the Wallet API from your server.
Does an internal transfer also move mobile money?
The transfer shown moves value between wallets within your service. Collecting external payments, funding wallets and paying out to mobile money require separately configured workflows. Confirm the intended flow with MeSomb before implementation.
How do I get access?
Contact MeSomb to discuss your service, activation requirements, credentials and applicable terms. Wallet service access is not automatically enabled by watching the demo or creating an account.
Building a product with user balances?
Tell us how your application should create, move and track value. We’ll help you clarify the wallet service setup and integration path.