How a Micro ATM cash withdrawal works
A Micro ATM turns a retailer's counter into a small ATM. The customer inserts or swipes a debit card in a portable card reader and enters their PIN, and the retailer hands over the cash once the card-issuing bank approves the withdrawal.
- Card and PIN. Unlike AePS, the customer authenticates with a debit card and PIN rather than Aadhaar biometrics.
- The bank sets the limits. There is no single public per-transaction cap. The card-issuing bank and your acquiring partner set the limits for card-and-PIN withdrawals.
- The device is certified. Card readers must meet your sponsor bank's and NPCI's specifications. An SBI Micro ATM tender annexure, for example, asks for PCI PED certification, EMV Level 1 and Level 2 certification, and certified biometric scanners.
- Your partner provides the SDK. The card reader talks to your acquiring partner's SDK, and your app talks to that SDK.
Ways to offer Micro ATM with Payonclick India
| Route | What it means | Status |
|---|---|---|
| White-label platform | Micro ATM inside your own branded Android app, with your acquiring partner's SDK | Available |
| Custom development | The Micro ATM module added to your existing Android app | Scoped per project |
| Payonclick partner Micro ATM API | Call Payonclick's Micro ATM from your servers | Not offered |
| Distributor account | Onboard retailers who offer Micro ATM on the Payonclick app | Available on payonclick.in |
What the Micro ATM module does
Native Android
Micro ATM runs in the Android app through your partner's card-reader SDK. It doesn't run in a web browser or on iPhone.
Bluetooth readers
Works with readers from PAX, MoreFun and NewLand, paired over Bluetooth.
Three transaction types
Cash withdrawal, balance enquiry and mini statement.
One merchant onboarding
Micro ATM reuses the merchant's AEPS onboarding, so a retailer onboards once for both services.
Logged before it starts
Every attempt is written to the transaction log before the SDK opens, so an attempt that breaks off halfway still leaves a record.
Operations console
Operations staff can settle, or mark as failed, any attempt left without a final result.
Guards on every result
The transaction result comes back from the SDK on the retailer's device. Before it becomes a wallet credit, the module applies guards:
- Amount band. The credited amount must sit within the expected band for that transaction.
- Credited once. The combination of the bank's reference number (RRN) and the provider's transaction ID can be credited only once.
- Replay block. A result that has already been used can't be submitted again.
- Nightly reconciliation. Micro ATM transactions join the nightly reconciliation upload with AEPS and UPI cash withdrawal.
The module doesn't claim real-time verification of each result with the provider. Reconcile against your acquiring partner's settlement reports every day, and review high-value exceptions before they age.
Choosing and managing devices
- Buy what your partner certifies. Your acquiring partner decides which reader models its SDK supports. Confirm the model before you buy in bulk.
- Map devices to retailers. Keep each reader's serial number against the retailer who holds it, so a lost device can be traced and blocked.
- Pair before the first customer. Retailers pair the reader over Bluetooth in the app, and run a balance enquiry on their own card first.
- Train for card safety. A retailer should never keep a customer's card, look at the PIN being typed or ask for it aloud.
Getting started
Line up your acquiring partner
Sign with a bank or aggregator that offers a Micro ATM SDK and certified readers for your model.
Scope the build
We map the partner's SDK, onboarding and settlement reports onto the module.
Build and brand
Your Android app with the SDK integrated, plus the admin console for your operations team.
Test and go live
Acceptance testing with real devices and your partner's credentials, then training and launch.