Mobile
Flutter
Build Android and iOS apps from one shared codebase, so you launch on both platforms faster with a consistent experience.
Used for
- Mobile apps
- Delivery apps
- E-commerce apps
- Booking apps
Wallet apps
Digital wallet app development for closed-loop and partner-issued wallets
Top-ups, payments, rewards and refunds on a double-entry ledger that is reconciled every day.
At a glance
The short version
What it is
Digital wallet apps with top-ups, QR payments, rewards and a balance ledger, for closed-loop programmes or with a licensed PPI issuer.
- What you get
- User app
- Merchant tools
- Risk and operations
- Finance
- How it works
- User app
- User app and payment gateway
- User app and merchant QR
- Rewards engine
- 2 more
- Runs on
- Android
- iOS
- Cross-platform
- Admin
- Who it's for
- Cost depends on
- Wallet model
- Ledger complexity
- Merchant side
Flutter and the related logo are trademarks of Google LLC. We are not endorsed by or affiliated with Google LLC.
How to start
Tell us what you need in your own words. You talk to the developers who would build it and get a written, line-item estimate.
Get a project estimateChoosing the right wallet model
The first decision is regulatory, not technical. A closed-loop wallet, used only for goods or services from the issuing business and without cash withdrawal, is treated differently from a wallet usable at other merchants or for transfers, which falls under RBI's prepaid payment instrument framework and needs an authorised issuer or bank partner.
Once your advisers confirm the model, we design the ledger, limits and KYC tiers around it, so moving from closed-loop to a partner-issued wallet later does not mean starting again.
Challenges
Problems a well-built wallet avoids
Balances that drift
Wallets built on a single balance column drift away from escrow or bank records over time.
Cashback abuse
Multiple accounts and self-referrals drain promotional budgets without controls.
Campaign-day load
Top-up and payment spikes during offers expose locking and performance issues.
Unclear refund paths
Refunds to the wallet versus the original source need rules customers and support staff understand.
What is included
Wallet app and back-office features
Platform: Android and iOS app
User app
- Top-up via UPI, cards and net banking
- Scan-to-pay at merchant QR codes
- Cashback, rewards and gift vouchers
- Statements and in-app KYC upgrade
Platform: Android app and web
Merchant tools
- Static and dynamic QR codes
- Collections, refunds and settlement reports
Platform: Admin dashboard
Risk and operations
- KYC-tier limits and velocity rules
- Freeze, dispute and refund workflows
- Campaign budgets and abuse monitoring
Platform: Admin dashboard
Finance
- Double-entry ledger with daily trial balance
- Reconciliation against gateway settlements and escrow statements
How it works
How money moves through a wallet, and stays reconciled
Whether the wallet is closed-loop or issued with a licensed PPI partner is decided first with your compliance advisers under RBI rules; the steps below then follow that model.
- User app
Step 1: Sign-up and KYC level
The user signs up with a verified mobile number, and the KYC level set by your partner's policy decides their wallet limits.
- User app and payment gateway
Step 2: Top-up
Money is added by UPI, card or net banking, and the ledger credits the wallet only after the gateway confirms the payment.
- User app and merchant QR
Step 3: Pay at a merchant
The user scans a merchant QR, sees the amount and merchant name, and pays from the wallet with a PIN or biometric.
- Rewards engine
Step 4: Rewards and refunds
Cashback follows campaign budgets and caps, and refunds go back to the wallet or the original source according to your rules.
- Merchant tools
Step 5: Merchant settlement
Merchants see collections and receive settlements on schedule, with reports for each outlet.
- Finance dashboard
Step 6: Daily reconciliation
The ledger is matched with gateway settlements and escrow or partner statements; any gap becomes an exception to investigate.
Platforms
Where users, merchants and operations teams use the wallet
Users and merchants use phone apps for Android and iOS; risk, operations and finance teams use an admin dashboard.
- Mobile
Android app
Apps for Android phones and tablets, tested on budget and mid-range devices and published on Google Play or privately.
- Mobile
iOS app
Apps for iPhone and iPad, built to Apple's guidelines and released through TestFlight and the App Store.
- Mobile
Cross-platform mobile app
One Flutter or React Native codebase for Android and iOS, with native modules where a feature needs them.
- Back office
Admin dashboard
Back-office panels for operations, support and finance teams: orders, users, content, reports and permissions.
Technology
Technology for accurate, secure wallets
Chosen so every balance comes from a ledger, alerts arrive instantly and apps stay secure on any phone.
Mobile
React Native
Build Android and iOS apps in the same language as a React website, so one team can share code and skills across web and mobile.
Used for
- Mobile apps
- Shopping apps
- Staff and field apps
- Mobile apps for SaaS
Backend
NestJS
A structured way to build back ends on Node.js, so large business systems stay organised, testable and easy to hand over.
Used for
- Business app back ends
- SaaS platforms
- Marketplaces
- Admin panel back ends
Data
PostgreSQL
A reliable database for the records your business runs on: orders, payments, bookings and stock, kept accurate and easy to report on.
Used for
- Orders and customers
- Payments and ledgers
- Stock and inventory
- Bookings
Data
Redis
Keeps frequently used data in fast memory, so apps stay quick on busy days and live features like order tracking feel instant.
Used for
- Faster apps
- Live order status
- Shopping carts
- Job queues and alerts
Cloud & DevOps
Firebase
Ready-made building blocks for mobile apps, such as push notifications, phone OTP login and crash reports, so you launch sooner.
Used for
- Push notifications
- Phone OTP login
- Crash reports
- Real-time updates
Flutter and the related logo are trademarks of Google LLC. We are not endorsed by or affiliated with Google LLC.
Integrations
Wallet integrations
Top-ups
Payment gateways (Razorpay, Cashfree, PayU)
UPI, card and net banking top-ups with webhooks.
Issuance
PPI issuer or bank partner APIs
Wallet issuance and limits through the licensed partner.
KYC
KYC providers
Minimum and full KYC through licensed providers.
Notifications
Firebase Cloud Messaging
Transaction alerts and campaign messages.
Security
DLT-registered SMS
OTPs and transaction SMS through registered templates.
Fraud
Device intelligence tools
Device fingerprinting to detect multiple accounts.
Privacy & security
Wallet security and compliance
PPI rules owned by your compliance team
Whether the wallet is closed-loop or a PPI, and which limits apply, is decided by your advisers and issuer partner; we implement those limits.
KYC tiers through licensed providers
Minimum and full-KYC upgrades run through licensed providers and your partner's policy.
Device binding and app protection
Device binding, PIN or biometric login, root detection, certificate pinning and encrypted storage.
Immutable ledger, audit logs and fraud rules
Every balance change is a ledger entry, admin actions are logged, and suspicious transactions are held for review.
Plain-English glossary
Wallet terms, in plain English
- Closed-loop wallet
- A wallet that can only be used for the issuing business's own goods or services, with no cash withdrawal, such as a campus canteen wallet. The rules differ from wallets usable elsewhere.
- PPI (prepaid payment instrument)
- RBI's category for wallets and prepaid cards usable beyond the issuer's own business. They need an authorised issuer; your advisers confirm whether your model is one.
- Double-entry ledger
- Every balance change is recorded twice, as a debit in one account and a credit in another, so the books always balance and any balance can be rebuilt from history.
- Escrow account
- A bank account that holds the money backing wallet balances. Matching wallet totals against it every day shows the money is really there.
- Device binding
- Tying an account to a specific phone, so a stolen password alone cannot be used to log in from another device.
- Velocity rule
- A limit on how often or how much a user can transact in a period, such as five top-ups an hour. It catches fraud and promotion abuse early.
Product preview
User app, merchant view and finance reconciliation
User app. Users see their balance, spending and rewards at a glance, and top up by UPI, card or net banking in a few taps. 
User app. Every top-up, payment, cashback and refund appears as a clear line in the statement, drawn from the same ledger that finance reconciles. 
Merchant app. Merchants see the day's collections, refunds and next settlement, and can show a QR code for each bill. 
Finance dashboard. Finance checks every day that wallet balances, gateway settlements and the escrow or partner account agree, and investigates any exception.
Illustrative preview
Sample screens: names, prices and figures are examples, not client data.
Industries
Where wallets fit
Cost drivers
Wallet development cost factors
Wallet model
Closed-loop wallets are simpler than wallets integrated with a licensed PPI issuer.
Ledger complexity
Points, holds and partial refunds add ledger and reconciliation work.
Merchant side
A merchant app, onboarding and settlements are a significant second product.
Rewards engine
Rule-based cashback with budgets and abuse controls takes careful design.
Security review
Penetration testing and fixes before launch are part of the budget.
Estimates are written from your scope, with the effort and assumptions behind each line item.
How pricing worksServices
Services involved
The disciplines a project like this draws on.
Mobile app development
Native and cross-platform Android and iOS apps, from first release through regular store updates, built by our in-house designers and engineers.
API development
Secure, documented REST and GraphQL APIs, plus integrations that connect your apps to payment, logistics, GST, messaging and business systems.
Flutter development
Android and iOS apps from one Dart codebase, built by engineers who know when Flutter is the right call and when native code is needed.
UI/UX design
Product design for web and mobile apps: research, user flows, wireframes, prototypes and design systems that engineers can build from.
Admin panel development
Back-office dashboards built around your team's daily tasks: order queues, approvals, catalogue management, payouts, reports and audit logs.
FAQ
Frequently asked questions
Do we need an RBI licence to launch a wallet?
It depends on how the wallet works, and your legal and compliance advisers should confirm it. Broadly, a closed-loop wallet used only for your own goods or services, with no cash withdrawal, is treated differently from a wallet usable at other merchants or for transfers, which needs PPI authorisation or an authorised issuer partner. We build either model.
How do you keep wallet balances accurate?
Balances are never edited directly. Every top-up, payment, refund, reward and reversal is written as balanced double-entry ledger entries, and a wallet's balance is derived from them. Payment APIs are idempotent, so a retried request or duplicate webhook is recognised rather than credited twice. A daily job reconciles ledger totals with gateway settlements and escrow or partner statements, and any mismatch becomes an exception for the finance team.
Can the wallet run cashback campaigns without being abused?
Yes, with controls built into the rewards engine rather than added after a loss. Campaigns carry budgets and per-user caps, cashback can be held for a period before release, and rules check device fingerprints, KYC status and referral patterns to spot multiple accounts. Suspicious rewards are held for review rather than paid, and operations staff can pause a campaign instantly.
Can users transfer wallet money to their bank account?
Only if the wallet model permits it. Closed-loop wallets usually do not allow withdrawal, and for PPIs, transfers to bank accounts are generally limited to full-KYC wallets under the issuer's rules. Where allowed, we integrate the partner's payout API with limits, beneficiary validation and fraud checks. Your issuer partner and compliance team set the exact rules, and the app enforces them.
Related
Keep exploring
Next step
Plan your wallet programme
Tell us who will use the wallet, where it can be spent and whether you already have an issuer partner.