AEPS Software Development Cost in India: What Drives the Price
There is no single price for AEPS software. A basic agent portal and a full platform with distributors, a white-label API, wallets and commissions are very different projects. This guide explains what actually drives the cost, how to separate build cost from running cost, the three ways to get an AEPS platform and what to prepare so that any vendor can give you a reliable estimate. If you are new to the topic, start with what AEPS is and how it works.
Build cost versus running cost
Two different budgets are often mixed up. The build cost is what it takes to design, develop, test and launch the software. The running cost is everything that continues after launch: hosting, monitoring, support, security testing, biometric devices for agents and the commercial terms with your bank or aggregator, such as onboarding fees and per-transaction charges.
Bank and aggregator terms are set by those partners, not by the software vendor, and access to AEPS itself is governed by NPCI rules, so ask for these separately and include them in your business case.
What drives the build cost
| Factor | What it affects | How to keep it under control |
|---|---|---|
| Panels and users | A single agent app is simpler than agent, distributor, super-distributor and admin panels plus a white-label API. | Launch with the panels you need on day one and add the rest later. |
| Services offered | Balance enquiry and cash withdrawal alone cost less than adding cash deposit, mini statement, Aadhaar Pay, micro-ATM, DMT and BBPS. | Start with the core services and add others as volume grows. |
| Bank or aggregator integration | The number of routes, the quality of their documentation and whether you need failover between routes. | Begin with one route and design for more. |
| Biometric devices | Each device model and platform (Android, Windows) needs integration through its RD service. | Support the two or three models your agents actually use. |
| Wallet, ledger and commissions | Multi-tier commissions, slabs, settlements, refunds and dispute handling add real complexity. | Define commission rules clearly before development starts. |
| Security and testing | Encryption, audit logs, access control and penetration testing before launch. | Budget for it up front; fixing issues after launch costs more. |
| Platforms | Web portal only, or web plus an Android app for agents. | Choose one platform for the first release. |
| Customisation | Building on an existing, proven core is faster than building every module from scratch. | Reuse proven components for wallets, ledgers and device integration. |
Three ways to get an AEPS platform
- Custom build: designed around your business rules and fully yours. It gives the most control and takes the longest.
- White-label platform: a ready product that is branded for you. It launches fastest, but you work within its features and its commercial terms.
- Customise a proven core: start from an existing, production-tested core for wallet, ledger and device integration and build your own workflows on top. It sits between the two in time and flexibility.
Which is right depends on how different your business rules are from the standard model and how quickly you need to launch.
What a delivery plan usually includes
- Discovery: services, panels, bank partner, devices, commission rules and launch target.
- Design and architecture: flows, data model, wallet and ledger rules, failover approach.
- Development: agent app, admin and distributor panels, bank integration and reporting.
- Testing: functional testing, load testing of the transaction path, and security testing against risks such as the OWASP Top 10. Our secure development and VAPT readiness service helps you prepare for independent security testing.
- Bank UAT and go-live support.
- Support and improvement after launch.
Ways to keep the cost under control
- Launch in phases: start with the core services on one bank route, then add services and routes as volume grows.
- Be specific about what you need on day one versus later.
- Reuse proven components for wallets, ledgers and device integration rather than rebuilding them.
- Agree acceptance criteria early so scope does not drift.
- Budget for testing and security review up front; fixing problems after launch costs more.
The reliability patterns that protect money movement, such as idempotent callbacks and strict balance locking, are worth paying for early because they prevent the most expensive class of bug: wrong balances.
How scope changes effort: three example scenarios
These scenarios show how effort grows with scope. They are illustrations of scale, not price quotes.
| Scenario | Typical scope | What increases the effort |
|---|---|---|
| Starter | One agent panel and an admin panel, balance enquiry and cash withdrawal, one bank route, one biometric device model. | Device integration and the bank UAT cycle. |
| Growing network | Agent, distributor and admin panels, cash deposit and mini statement, an Android app, two bank routes with failover. | Distributor hierarchies, commission slabs, failover logic and more reports. |
| Full platform | White-label API for other businesses, AEPS plus DMT and BBPS, multi-tier commissions, automated reconciliation and dispute handling. | Multi-tenant design, settlement automation, higher security and load-testing requirements. |
Common mistakes that raise cost
- Starting development before the bank partner and their API documentation are confirmed.
- Trying to launch every service and panel at once.
- Leaving commission and settlement rules vague until late in the project.
- Treating security testing as an optional extra.
- Changing the scope repeatedly without agreeing how changes are priced.
What to prepare before asking for a quote
The more precisely you describe the project, the more reliable the estimate. Prepare:
- The services you want to offer at launch and the ones planned later.
- Which panels you need (agent, distributor, admin, API clients).
- Your bank or aggregator partner and their API documentation, if you have it.
- The biometric devices and platforms your agents will use.
- How commissions and settlements should work.
- Your target launch date and expected transaction volume.
We do not publish a fixed price because it would be misleading: it depends on the points above. After a short discovery call we scope the work and give you a written plan and estimate before development starts. You can also manage agents, hierarchies and commissions with our fintech CRM.
Frequently asked questions
Why is there no fixed price for AEPS software?
Because projects differ widely in panels, services, bank routes, devices and security needs. A fixed public price would either overcharge a simple project or under-quote a complex one. A short discovery call lets us scope your project and give a written estimate.
Are bank and aggregator charges part of the software cost?
No. Onboarding fees and per-transaction charges are set by your bank or aggregator and by NPCI rules. They belong in your running costs and business case, separate from the software build.
Can I start small and add services later?
Yes, and we recommend it. Launch with the core services on one bank route, then add services, routes and panels as transaction volume grows.
What continues to cost money after launch?
Hosting and monitoring, support, security testing, agent devices, bank charges, and ongoing improvements. Plan for these from the start.