NACH vs. eNACH: Choosing the Right Recurring Payment Mandate
Peneu Editorial Team · 1 July 2026 · Updated 26 September 2026 · 7 min read
Any business that collects the same customer's money again and again (EMIs, insurance premiums, investment instalments, subscriptions) needs a mandate: the customer's standing authorisation for future debits. In India there are several kinds, and the difference between them is mostly how the customer authorises it and what it's debited from.
NACH and eNACH are the same mandate, signed differently
Both create a debit mandate on the customer's bank account, processed through NACH. With a physical NACH mandate, the customer signs a paper form, which is scanned and sent to their bank for approval against its records. With eNACH, the customer approves it online, authenticated by their bank, commonly with net banking or a debit card.
| Physical NACH | eNACH | |
|---|---|---|
| How it's authorised | Signed paper form, checked by the customer's bank | Online, authenticated by the customer's bank |
| Typical time to activate | Longer: paper has to travel and be checked | Shorter: approved in one online session |
| Common reasons for rejection | Signature or details don't match the bank's records | Customer abandons or fails authentication |
| Fits | Customers without net banking or a debit card; in-branch sign-ups | Digital onboarding; most new customers |
Where UPI and card e-mandates fit
UPI and cards support recurring payments too, through e-mandates under RBI's e-mandate framework. The customer registers the mandate in their UPI app or with their card, with authentication, is notified before each debit, and can cancel it. For amounts above set limits, each debit needs the customer to authenticate again, which matters for large instalments.
| Mandate | Debits | Suits |
|---|---|---|
| NACH / eNACH | A bank account | EMIs, larger amounts, long tenures |
| UPI e-mandate | A bank account through the UPI app | Subscriptions and smaller recurring amounts |
| Card e-mandate | A card | Subscriptions, especially where customers prefer cards |
What goes wrong, and what to do
Mandates fail in two places: at registration and at debit. Registration fails when details don't match or customers drop out of authentication; debits fail when there isn't enough money, the account is closed, or the mandate was cancelled.
- Registration: pre-fill details from verified data, and explain to customers why their bank is asking them to authenticate.
- Insufficient funds: schedule debits after common salary dates, and re-present only where the rules allow.
- Closed accounts or cancelled mandates: contact the customer and set up a new mandate or another payment method.
- Every return: record the reason code; it tells you what to do next.
How to choose
Choose by the customer and the amount, not by what's easiest for you to integrate.
Whichever you use, reconcile debits against your schedule every day, so a return is acted on before the next instalment is due.
- Loans and larger instalments: eNACH, with physical NACH as a fallback.
- Consumer subscriptions: UPI and card e-mandates, since customers set them up in seconds.
- A mixed customer base: offer more than one, and let the customer choose.
Go deeper
Official sources
- RBI — Digital Payments – E-mandate Framework, 2026UPI, card and PPI mandates: registration with authentication, pre-debit notice, limits.
Last reviewed . Examples, amounts and screens marked illustrative are not Peneu figures.
Questions about your own payment setup?
Talk to PeneuRelated reading
UPI vs. Cards: What Should Merchants Prioritise?
UPI and cards solve different problems for Indian merchants. How they compare on authentication, recurring payments, disputes, customers abroad and cost, and how to decide what to offer first.
A Founder's Checklist for Choosing a Payment Gateway
Methods, money flow, reliability, integration, reporting, support and cost: the questions to ask any payment gateway or aggregator before you sign, and how to compare the answers.