API Reseller
AePS API
The AePS rail exposed directly, for products that supply their own operator interface. Withdrawal, balance enquiry, mini statement and Aadhaar Pay, with the biometric encrypted at the device and passed through untouched.
What you get
- Withdrawal, balance enquiry, mini statement and Aadhaar Pay
- Registered-device biometric payload passed through end to end
- Consent artefact captured and retained per transaction
- Works against any Aadhaar-seeded account at any bank
- Per-operator transaction and commission reporting
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Operations
- Withdrawal, balance enquiry, mini statement, Aadhaar Pay.
- Biometric
- Registered-device payload passed through end to end. We never decrypt or store it.
- Consent
- A consent artefact is captured and retained per transaction.
- Timeout
- Returns an explicit unknown state. Never auto-resolved to success or failure.
- Webhook
- Signed, with replay protection. Retried until your endpoint returns 2xx.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About aeps api
A withdrawal timed out. Was the customer's account debited?
Possibly, and that is exactly why it is not reported as a failure. The call returns an unknown state; the transaction stays open until the rail confirms an outcome. Treating it as failed and handing over cash is how an operator ends up short, so the resolution comes from the confirmed status, never from elapsed time.
Do you store the biometric?
No. The registered-device payload is encrypted at the device and passed through untouched, so there is nothing in our systems to decrypt or retain. The consent artefact for the transaction is retained; the biometric itself is not.