What Is AEPS? How the Aadhaar Enabled Payment System Works

AEPS is a payment model operated through NPCI (the National Payments Corporation of India). A customer links their bank account to their Aadhaar number, then authenticates a transaction with biometrics, usually a fingerprint, on a registered biometric device. Identity is verified by UIDAI, the authority that issues Aadhaar. No debit card, PIN or smartphone is needed on the customer side.

Because the model is interoperable, a customer of one participating bank can transact at an agent who is connected through a different bank. The customer simply selects their own bank at the start of the transaction.

The services available through an AEPS agent typically include:

• Balance enquiry
• Cash withdrawal
• Cash deposit
• Mini statement

Exactly which services and transaction limits apply depends on NPCI rules and on the bank or service provider the agent works through, and these rules change over time. Always confirm against the current NPCI circulars and your bank partner before you design product features around them.

• The customer, who provides their Aadhaar number and biometric.
• The agent or business correspondent, who operates the AEPS application and the biometric device.
• The AEPS software (portal or mobile app) that captures the request and talks to the bank side.
• The acquiring bank or aggregator that the agent network is onboarded with.
• NPCI, which routes the transaction between banks.
• UIDAI, which authenticates the customer's identity from the Aadhaar number and biometric.
• The customer's own bank (the issuer), which debits or credits the account.

• The agent selects the service (for example cash withdrawal) and enters the amount.
• The agent enters the customer's Aadhaar number (or Virtual ID) and selects the customer's bank.
• The customer places a finger on a UIDAI-registered biometric device. The device captures the fingerprint and encrypts it at the point of capture through its registered device (RD) service.
• The AEPS application packages the encrypted biometric data and transaction details and sends them to the acquiring bank or aggregator.
• The request goes to NPCI, which sends the authentication to UIDAI and the debit or credit request to the customer's bank.
• The response travels back along the same path. The application shows success or failure and prints or sends a receipt.
• The software updates the agent's wallet and ledger and records the transaction for reconciliation.

Each step can fail or time out independently, which is why robust AEPS software treats every transaction as something that must be recorded, retried safely and reconciled, not just displayed.

• Fingerprint capture fails: the application checks the device status, explains the problem and lets the agent retry without creating a duplicate request.
• A bank is slow or unavailable: the switch routes to another available route where the commercial setup allows it, and the transaction is shown as pending rather than failed.
• The request times out after the customer was debited: the software records the transaction as pending, runs a status enquiry and reconciles it, instead of guessing.
• The same request is submitted twice: an idempotency key makes sure it is processed once.
• The agent's wallet does not match the bank's records: the ledger records every movement so differences can be traced and settled.

These are the same problems solved in other payment systems. Our guides on idempotent payment webhooks and on preventing double spends with PostgreSQL row-level locking cover the engineering detail.

• Micro-ATM: a handheld device where the customer uses a debit card and PIN at an agent, instead of Aadhaar and biometrics.
• Aadhaar Pay: a merchant payment method where a customer pays a shop using Aadhaar and biometrics.
• DMT (domestic money transfer): sending money to a bank account through IMPS, often offered by the same agent network.
• BBPS bill payments: paying electricity, gas, water and other bills through the Bharat Bill Payment System.

Many agent platforms combine several of these in one application, with a shared wallet, ledger and commission engine. A fintech CRM and agent network platform manages onboarding, hierarchies and commissions across all of them.

• Integrate biometric devices through their RD service (for example Mantra, Morpho and Startek devices) on Android or Windows.
• Connect securely to the bank or aggregator APIs and handle timeouts, retries and callbacks.
• Keep an accurate agent wallet and ledger, with every movement recorded and reconcilable.
• Support agent onboarding and KYC, commission slabs and distributor hierarchies.
• Provide reports, dispute handling and settlement reconciliation.
• Protect sensitive data with encryption, access control, audit logs and regular security testing against common risks such as the OWASP Top 10.

If you are working out a budget, read what drives AEPS software development cost.

A software company does not connect to NPCI on its own. Access to AEPS comes through a licensed bank or aggregator, and onboarding, commercial terms, transaction limits and approvals are set by them and by NPCI. Software built for AEPS should follow NPCI and UIDAI guidelines, but approval to go live is granted through your bank partner, not by the software vendor.

If you are planning an AEPS platform, start by agreeing your bank or aggregator partner and getting their technical documentation. That determines the integration work, the supported services and the timeline.