UPI AutoPay
Definition
UPI AutoPay is NPCI's mandate-based recurring debit framework for UPI — enabling scheduled collections from bank accounts without per-transaction authentication up to ₹15,000.
UPI AutoPay (also called UPI Recurring Payments) is NPCI's framework for automated recurring debits from UPI-linked bank accounts in India. Launched in 2020, it allows merchants to collect scheduled payments — subscriptions, EMIs, insurance premiums, SIP investments — by creating a mandate against a customer's UPI ID. The customer authorises the mandate once; subsequent debits execute automatically within mandate parameters. Transactions above ₹15,000 require per-transaction customer authentication (OTP/PIN); transactions at or below ₹15,000 are processed without additional friction after mandate setup.
UPI AutoPay is India’s answer to the structural challenge of recurring billing at scale: how do you collect subscriptions and instalment payments from 350+ million active UPI users without per-transaction authentication friction? NPCI’s mandate framework solves this by front-loading customer consent at setup and automating debits thereafter — with authentication required only for higher-value transactions.
How UPI AutoPay Works
Mandate creation: The merchant presents a mandate request to the customer at subscription setup. The customer receives the mandate details on their UPI app (PhonePe, Google Pay, BHIM, Paytm, or their bank’s UPI app), reviews the parameters, and authenticates with their UPI PIN to authorise. The mandate is registered with NPCI and both the customer’s and merchant’s banks.
Mandate parameters:
- Amount type: Fixed (exact amount each time), maximum (up to a ceiling), or variable
- Frequency: One-time, daily, weekly, fortnightly, monthly, bi-monthly, quarterly, half-yearly, annual, or as-presented
- Duration: Set start and end date, or perpetual
Recurring execution: On the scheduled date, the merchant’s PSP or bank sends a debit request to NPCI referencing the active mandate. NPCI routes to the customer’s bank. The customer receives a pre-debit notification ≥24 hours before the debit. For amounts ≤₹15,000, the debit executes without additional customer action. For amounts above ₹15,000, the customer must authenticate with UPI PIN.
The ₹15,000 Threshold
The ₹15,000 per-transaction authentication threshold is set by RBI (Reserve Bank of India). It balances consumer protection against friction:
- Below threshold: Seamless recurring debit, highest conversion, appropriate for subscriptions and small EMIs
- Above threshold: Explicit per-transaction authentication required — adds friction but ensures customer intent for larger amounts
For operators with subscription prices above ₹15,000/month, the per-transaction authentication requirement materially affects conversion. Splitting billing cycles (e.g., weekly debits below the threshold) is sometimes used operationally, but requires mandate restructuring.
Pre-Debit Notification Requirement
RBI mandates that customers receive a pre-debit notification at least 24 hours before any UPI AutoPay debit. This notification must include:
- Merchant name
- Amount
- Debit date
- Mandate reference
Merchants and PSPs must implement this notification flow. Failure to send pre-debit notifications is a compliance violation and can result in the debit being disputed as unauthorised.
Mandate Management
Customers can manage (pause, modify, or revoke) UPI AutoPay mandates through their UPI app. Revocation is immediate — a debit initiated after revocation fails cleanly.
Merchants should handle mandate revocation events (delivered via webhook by NPCI-connected PSPs) by triggering dunning or offboarding flows, not by retrying the debit.
UPI AutoPay vs. Card Recurring
| UPI AutoPay | Card MIT Recurring | |
|---|---|---|
| MDR | 0% (most UPI transactions) | 0.5–2.0% |
| Authentication at setup | UPI PIN | 3DS2 / SCA |
| Per-transaction auth | Only above ₹15,000 | No (MIT exemption) |
| Expiry risk | No (bank account) | Yes (card expiry) |
| Chargeback | No (dispute via NPCI/bank) | Yes |
| Coverage | UPI-enabled accounts (~80% of Indian banking customers) | Cards (~35% penetration) |
For Indian subscription businesses, UPI AutoPay reaches a broader customer base than card-on-file at lower cost. The mandate setup UX requires integration via a UPI-enabled PSP (Razorpay, PayU, Cashfree, Juspay, Paytm Payments).
Dominant Use Cases
UPI AutoPay has seen fastest adoption in:
- Mutual fund SIPs: SEBI-regulated systematic investment plans; largest volume category
- Insurance premiums: LIC, HDFC Life, SBI Life
- Loan EMIs: Digital lending NBFC segment
- OTT subscriptions: Netflix, Disney+ Hotstar, Spotify India
E-commerce subscription merchants are the growth segment — software SaaS, consumer app subscriptions, and education platforms are migrating recurring billing from card-on-file to UPI AutoPay for the cost and coverage advantages.
Related terms
Card on File
Card on file (CoF) refers to the storage of a customer's card credentials — card...
e-Mandate
An e-Mandate is a digitally authenticated authorization from a customer permitti...
Real-Time Rail
A real-time rail (also called an instant payment system) is a payment infrastruc...
Recurring Payment
A recurring payment is a pre-authorised, repeating charge made by a merchant aga...
Variable Recurring Payments (VRP)
Variable Recurring Payments (VRP) is an open banking payment mechanism that allo...
Subscribers get the PSP Selection RFP Kit — 60+ structured questions, evaluation scorecard, and negotiation playbook — delivered to your inbox instantly.