Onboarding with two KYC tiers
Phone verification, a basic tier with low limits and a full tier with document and selfie checks through one provider.
Solutions · Stored-value wallet
A stored-value wallet holds customers’ money as a balance they can top up, send to someone else and spend, without being a full bank account. The licence usually sits with a partner bank or e-money institution, and the build turns on three things that partner will inspect: who each customer is, where every unit of money sits in the ledger, and which limits stop the wallet moving money it should not.
Professional plan. Enterprise customization is quoted on scope.
KYC tiers that set balance and transfer limits
A double-entry ledger reconciled to safeguarded funds
Top-ups, P2P transfers and withdrawals
V1
Phone verification, a basic tier with low limits and a full tier with document and selfie checks through one provider.
Double-entry postings, transaction history and downloadable statements for customers.
One card or bank top-up method, transfers by phone number and withdrawal to a bank account.
Limit settings, screening alerts, case notes, freezes and daily reconciliation reports.
Operating loop
A customer verifies a phone number, then supplies identity details for the tier they need. A low tier may allow a small balance after basic checks; higher tiers need a document, selfie and address check, and raise the limits once approved.
Money enters by card, bank transfer, a local instant payment scheme or cash at an agent. The balance is credited only once funds are confirmed, and each top-up is recorded against the pooled or safeguarded account held at the partner bank.
Customers send money to other users by phone number or QR code, pay merchants who accept the wallet, or request money from friends. Every movement is a balanced pair of ledger entries, checked against limits and screening rules before it posts.
Balances leave by bank payout or card refund. Each day, the total of all customer balances is matched against the money actually held in the safeguarded account, and any difference is investigated before the next business day starts.
Roles
Wants the balance and each movement shown instantly, transfers that land in seconds and a plain reason when one is held. A top-up stuck on pending with no explanation loses trust fast.
Accepts wallet payments in a shop or online, sees settlements and refunds, and receives payouts to a bank account on an agreed schedule.
Works through failed identity checks, sanctions and watchlist hits and monitoring alerts, files suspicious activity reports where the law requires and can freeze a wallet.
Runs the daily reconciliation, chases failed top-ups and payouts, handles chargebacks on card-funded balances and reports positions to the licence holder.
Hard parts
Balances must be derived from immutable double-entry postings, never kept as a number that code overwrites. Each transfer is one transaction with balanced entries, idempotency keys stop a retry posting twice, and corrections are new entries rather than edits.
Unless you become licensed yourself, a partner bank or e-money institution owns the regulatory relationship. Its rules shape onboarding, limits, monitoring and reporting, so agree the operating model and the data it expects before designing flows.
A fraudster tops up with a stolen card, sends the balance on, and the card is charged back weeks later. Hold card-funded money for new users before it can be sent, cap first top-ups and require 3-D Secure.
Balance caps, daily and monthly transfer limits and withdrawal conditions vary by verification tier and by country. Store them as configuration tied to the tier and evaluate them in one place before every posting, so a regulatory change does not need a release.
Rules that flag every unusual transfer bury analysts and annoy honest users. Begin with clear scenarios such as money passing straight through or many senders paying one wallet, tune them on real data and track how many alerts lead to action.
Operator controls
Each tier’s required checks, balance cap and transfer limits, versioned with the date they take effect.
Alerts, identity reviews and complaints in one queue with evidence, decisions, freezes and a full audit trail.
Customer balances against the safeguarded account, unmatched bank lines and failed payouts, day by day.
Charges for top-ups, withdrawals, cross-border sends and merchant payments, with promotional waivers that end on a set date.
Revenue
A percentage on wallet payments taken by merchants, usually set below their card costs to win acceptance.
Free sends between users, with charges on instant bank withdrawals, cross-border transfers or currency conversion.
Where the partner arrangement permits, a share of interest earned on safeguarded money; many regimes forbid paying interest to e-money holders.
Later
A physical or virtual card spending the balance brings card-scheme programme management; add it once usage is steady.
Popular in many markets, but every biller is a separate integration; choose the top few after launch.
Holding and converting currencies multiplies ledger accounts and reporting; start with one currency.
Next decision
Weighing a wallet against a digital current account or core banking software? The banking overview lines up the regulated options.
Open registerIf customers need account numbers, salaries paid in and debit cards from day one, the digital banking front-end suits better than a wallet.
Open registerInstitutions that need configurable account products, servicing and transfer operations should look at the banking operations platform.
Open registerThe fintech development service shows how we work alongside your licence partner, compliance lead and auditors on a regulated build such as a wallet.
Open registerLive demo
Open each app or panel in a new tab and sign in with the demo login shown. The demos run on shared sample data, carry our demo product names, and show the ready-made product before any customization.
Customer App
user@demo.com | User_321Customer Website
user@demo.com | User_321Branch Staff & Admin
shared on a guided callArtifact register
Reference screens illustrate workflows, not a contracted feature list. Sample prices, data, and responses are demonstration content; confirm the current scope during a walkthrough.
Deployable Product Architecture
Product development workstation / system register
Product delivery loop
Engineer working on laptop for product development
Discover
Blueprint
Build
Operate
Deployable Product Architecture
Technical systems review / system register
Delivery team
Engineering team reviewing technical systems
Define
Assemble
Deliver
Review
Deployable Product Architecture
Technical planning environment / system register
Live operations
Technical planning environment for engineering delivery
Request
Assign
Track
Settle
Deployable Product Architecture
Engineering workstation / system register
Financial control loop
Engineer using technology workstation for software systems
Verify
Authorize
Record
Reconcile
Screens can change every sprint; the ledger cannot. Settle account types, how fees and holds post, how reversals work and how the books map to the bank statement before any interface is drawn. A wallet on a sound ledger can add features for years, while one that stores balances as numbers usually needs rebuilding after its first audit.
Run reconciliation from the first test transaction, not after launch. Unexplained differences are far easier to trace across a hundred postings than across a million.
The bank or e-money institution behind the wallet will approve onboarding rules, limits, monitoring scenarios and complaint handling, and may audit the system. Bring its compliance team into design reviews early and agree how alerts and reports reach it, rather than meeting new requirements during go-live checks.
Wallets that last usually own one habit first: paying a particular merchant network, splitting bills or receiving wages. Choose that use case, make it quicker than cash or cards for that group, and widen to bills, cards and other currencies once balances are being held and spent.
FAQ
Not always. Many wallets go live on the licence of a partner bank or e-money institution, which safeguards the funds while you run the product. Closed-loop wallets spendable only with one merchant group may fall outside some regimes, but take legal advice for every country.
A closed-loop wallet can only be spent with the issuer or a defined group of merchants, like a coffee chain’s app. An open-loop wallet pays anyone who accepts it and sends money between users, which brings fuller licensing, identity checks and monitoring duties.
Every balance must trace back to postings that add up, and the total must equal the money actually held. Balances stored as editable numbers make reconciliation impossible, and that is among the first things a partner bank’s due diligence examines.
A basic tier with phone and data checks can finish in under a minute. Automated document and selfie checks usually return within minutes, with a manual queue for failures. Let users start on a limited tier while the higher check completes.
In many e-money regimes, including the EU’s, issuers may not pay interest on stored balances. Rewards or cashback structured differently may be allowed. Confirm with your licence partner before promising any return.
Primary sources
Dated official documentation, standards, and research that support the factual claims on this page.
EU rules on issuing e-money, safeguarding funds and the ban on paying interest.
Framework for payment services, including strong customer authentication.
International standards on customer due diligence and anti-money-laundering controls.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.