Digital Wallet (Wallet)
The wallet balance is not a stored number. It is read from the Financial Core. Top-up, payment and transfer are each posted as a balanced voucher in the Financial Core.
- Domain
- Wallet and internal payments
- Target customers
- fintechs, banks, the platform's consumer services (loyalty, credit)
- Main capabilities
- top-up, payment, transfer, temporary holds, wallet groups, gift card payment instrument, mobile API
Wallet is the platform's digital wallet microservice. It does not keep the balance of each wallet as a stored number; it computes it from the Financial Core. Every financial operation on a wallet, including top-up, payment and transfer, is posted to the accounting core as a balanced accounting voucher through a secure inter-service transaction.
This service is an infrastructure product and is not a standalone consumer app. It acts as the wallet layer for the platform's other services, including Customer Loyalty and Credit Card, and gives the customer a shared payment instrument.
Wallet has both a counter and operations API and a dedicated API for the customer mobile app, including statements, Excel export and transfers protected by a one-time code.
Key capabilities
Definable wallet types
Each company can define several wallet types with independent accounting settings, for example a general wallet, a cashback wallet or a gift card wallet.
Core financial operations
Top-up, payment and transfer between wallets (with a single double-entry accounting voucher), all with a voucher preview before final posting so that the balance of the accounting voucher can be confirmed before the user approves.
Single and bulk wallet opening
Temporary holds and release
Reserving part of the balance for a future commitment without posting an accounting voucher, with the usable balance equal to the total balance minus the sum of active holds.
Transaction reversal with an automatic adjusting voucher
Wallet groups
Grouping several wallets or cards belonging to one customer into a single group, with the group's aggregate balance displayed. The main use is for customers who hold several payment instruments of the same kind.
Configurable notifications
Setting SMS and in-app notifications for each wallet event, with no code change.
Mobile app API
Transaction list, balance, summary and detailed statements with Excel and PDF export, and fund transfer with one-time code confirmation.
Shared payment instrument infrastructure
The wallet acts as an “instrument provider” for gift cards and Customer Loyalty vouchers. At the moment a voucher is activated, it automatically finds or creates the customer's wallet and links the transaction to the accounting voucher that was already posted, without posting a second one.
Financial safety on retry
A mandatory unique key for top-up, payment and transfer. Retrying the same operation never creates a second accounting voucher or SMS, and the service is fully protected against concurrent requests using the same key.
Conformance with the platform transaction status standard (pending, settled, failed, reversed, expired) and automatic review of unfinished accounting vouchers
Business value
Every consumer service on the platform that needs a financial wallet for the customer uses Wallet directly, instead of rebuilding accounting logic. All of the platform's products therefore share a single, reliable source for the customer's balance, and the risk of inconsistency between several parallel financial systems is removed. The unique key mechanism and the accounting voucher preview also ensure that no duplicate financial transaction is posted on unstable networks or when a user retries.
Use cases
- A consumer digital wallet for top-up, payment and fund transfer between customers.
- A settlement wallet for merchants and shops.
- A tool for redeeming Customer Loyalty points, that is, cashback paid directly into the wallet.
- A gift card or voucher that can be activated in the customer's wallet.
- Multiple wallets for one customer, for example several prepaid cards, with an aggregate balance display.
What sets it apart
- The balance is journal-driven, meaning it always agrees with the Financial Core and is never a cached number that could diverge.
- Shared infrastructure for several of the platform's consumer services, in place of separate financial logic in each service.
- An accounting voucher preview before real posting, using exactly the same voucher-building logic as the final voucher.
- Full protection against retries and concurrency in sensitive monetary operations.
Solutions that use this module
See this module on demo data
In a demo session we walk through your organization's scenarios on Dara's demo environment and answer your technical and finance teams' questions.