UPI AutoPay vs e-NACH for SIP mandates

UPI AutoPay, in mechanism

UPI AutoPay is NPCI's recurring-payments product, launched in 2020. The investor approves a single mandate in their UPI app for an amount, a frequency and a duration. A pre-debit notification goes out ahead of the SIP date, the debit fires automatically on the date, and settlement into the collection account lands within minutes.

What the October 2025 rule actually changed. With effect from 1 October 2025, SEBI requires SEBI-registered, investor-facing intermediaries to collect investor money only through standardised UPI IDs carrying the exclusive @valid handle issued via NPCI, with a category suffix — .mf for mutual funds, .brk for brokers — and a visual verification marker in the payment app. This is a rule about the payee: it tells you the money is going to a registered intermediary and not to an impersonator. It does not require anything of your own UPI ID, and it does not impose extra KYC on you. Existing SIP mandates were allowed to continue on the old collection details; new SIPs, renewals and extensions use the new ones.

e-NACH, in mechanism

e-NACH is the digital evolution of the paper NACH (National Automated Clearing House) mandate. The investor signs an e-NACH form via Aadhaar OTP or net banking; the mandate is registered with NPCI's NACH; debits are pulled on the SIP date via the inter-bank clearing rail. Settlement can take 1–2 hours; debit failures (insufficient balance, mandate suspension) are reported back by T+1.

Comparison

• Setup: UPI AutoPay is approved inside your UPI app in one prompt. e-NACH needs an Aadhaar OTP or a net-banking authentication and takes a few minutes.
• Per-debit cap: UPI AutoPay is capped at ₹1 lakh per debit for mutual fund SIPs under NPCI's category limits. e-NACH supports substantially higher instalments, with the ceiling set by your bank rather than by a single national limit — check with the bank before assuming a figure.
• Authentication on each debit: under the RBI e-mandate framework, no UPI PIN is needed on recurring debits up to ₹15,000; above that you approve each one.
• Settlement: UPI AutoPay settles in minutes. e-NACH runs through inter-bank clearing and typically takes hours, with failures reported back the next day.
• Revocation: both are revocable digitally — UPI from inside the UPI app, e-NACH through your bank or your distributor.
• Bank coverage: e-NACH reaches essentially every NACH-member bank. UPI AutoPay needs an issuing bank that supports recurring UPI, which most major banks do and some co-operative banks still do not.
• Success rates: not published here. See the FAQ — we have no auditable source for a per-rail figure.

Which one we suggest

Our view, not a rule: UPI AutoPay for ordinary monthly SIPs from a bank that supports recurring UPI, because the setup and the debit both happen without a branch. e-NACH where the instalment exceeds the UPI cap, or where the bank does not support recurring UPI — which is still the case at some co-operative banks in the North East. Where both are available we ask rather than silently defaulting you to one.

Failure handling

This part is our process rather than a regulation. On a failed debit we send an immediate SMS and email. The order is retried once. After repeated consecutive failures a bank will typically suspend the mandate at its end, at which point we surface a re-registration prompt in your dashboard — the mandate cannot be revived from our side alone.