UPI AutoPay vs NACH: Which Recurring Payment System to Implement First?

The Indian Recurring Payments Landscape

In India, executing recurring payments is strictly governed by the Reserve Bank of India's (RBI) e-mandate directives. Unlike the US or European markets where credit card vaults allow merchants to auto-charge accounts at will, Indian customers must explicitly sign up for a structured recurring billing mandate. For product managers, choosing between the National Automated Clearing House (NACH) and UPI AutoPay dictates how fast users activate, how much transaction friction they experience, and how reliable payment success rates are on subscription renewal cycles.

While third-party aggregators like Razorpay, Cashfree, and PayU simplify API integrations for both systems, the fundamental clearing infrastructure, user authentication flows, and transaction limits are completely distinct. Let's break down the technical differences and product implications to help you decide which system to implement first.

Detailed Comparison: UPI AutoPay vs NACH

Deep Dive: UPI AutoPay

Introduced by the NPCI to capture micro-subscriptions, UPI AutoPay leverages the massive adoption of UPI in India. When a user checks out, instead of completing a one-time transaction, the payment gateway requests a Mandate_Created event. The user is redirected to their preferred UPI application (e.g. PhonePe, GPay) where they view the mandate details (amount caps, frequency, validity period) and authorize it with their UPI PIN.

Under the RBI e-mandate framework (updated in 2026), subsequent debit calls are executed programmatically AFA-free up to ₹15,000 for general subscriptions, and up to ₹1,00,000 for specific categories like mutual fund SIPs, insurance premiums, and credit card bills. For transactions exceeding these respective thresholds, the UPI network triggers a notification requiring the user to authenticate the transaction with their UPI PIN, which introduces checkout friction and reduces renewal success rates.

UPI AutoPay Integration Example

A typical API payload for registering a UPI AutoPay mandate with a gateway like Razorpay requires specifying the recurring billing rules:

{
  "customer_id": "cust_828392",
  "type": "link",
  "amount": 250000, // ₹2,500.00
  "currency": "INR",
  "description": "Premium monthly plan subscription",
  "subscription_registration": {
    "method": "upi",
    "auth_type": "pin",
    "max_amount": 500000, // maximum allowable single debit
    "expire_by": 1893456000 // UNIX timestamp
  }
}

Deep Dive: NACH e-mandate

NACH is India's legacy bulk clearing system operated by the NPCI, modernized to support digital "e-mandates". To link a bank account for recurring debits, the user must input their bank account number and IFSC, and then complete an authentication flow on their bank's Net Banking portal or by entering their Debit Card PIN and OTP. This verification process creates a formal debit instruction against the user's primary bank account.

Because it acts as a direct bank-to-bank settlement system, NACH is the standard choice for financial operations that require high security and large-ticket transactions, such as lending apps (e.g., KreditBee, Navi) demanding EMI collections, and premium wealth managers (e.g., Zerodha Coin, Groww) handling SIPs above ₹1,00,000.

The PM's Decision Framework: Which to Implement First?

To choose the best payment option for your product launch, evaluate these three key dimensions:

1. Average Order Value (AOV): If your service costs less than ₹15,000 per billing cycle (or up to ₹1,00,000 for mutual fund SIPs or insurance), start with UPI AutoPay. The friction of logging into net banking to set up a NACH mandate will cause a 30% drop-off at checkout. If your AOV exceeds these limits (e.g. B2B contracts over ₹15,000 or SIPs over ₹1,00,000), NACH is your only viable path.
2. Customer Cohort and Demographics: UPI AutoPay requires a mobile-first user who is comfortable navigating UPI applications. For enterprise SaaS users, B2B buyers, or older cohorts, net-banking-authorized NACH e-mandates align better with corporate accounting policies and user preferences.
3. Activation Velocity: UPI AutoPay mandates are authorized and active within seconds. In contrast, NACH e-mandates can take 24 to 48 hours for certain public sector banks to approve, delaying activation and increasing drop-offs.

Friction Points & Failure Modes to Watch

Both recurring payment systems have specific failure modes that product managers must design around:

• The Pre-Debit Notification Rule: By RBI mandate, both systems require sending a pre-debit alert to the user 24 hours before charging their account. For UPI AutoPay, this notification is triggered automatically by the UPI app. Users sometimes see this notification and manually pause or revoke the mandate, resulting in billing failures. Ensure your system triggers automated recovery emails if a mandate is cancelled.
• Insufficient Balance Failures: Salary-day sweeps are common in recurring billing. If a NACH charge fails due to insufficient funds, the bank may charge the user a penalty fee (bounce charge) ranging from ₹250 to ₹500. This friction can damage customer trust. Implementing a pre-debit check or allowing users to adjust their debit date reduces these failures.
• Bank Compatibility: While all major private and public sector banks support NACH e-mandates, some smaller cooperative banks or rural regional banks only support legacy paper mandates. Similarly, older UPI accounts may not support recurring payments. Provide a clear fallback flow (like a manual one-time payment link) to prevent account suspension.

Frequently Asked Questions