UPI AutoPay for Indian Businesses: How to Set Up Recurring Payments

Every gym owner in India has faced the same conversation at the end of the month: members who "forgot" to pay, a WhatsApp reminder that went unread, and an hour spent chasing down fees that were already supposed to be collected. Every SaaS founder sending invoice emails has watched payment success rates hover around 60–70% because customers need to actively initiate each transaction.

UPI AutoPay changes this equation. It lets Indian businesses collect recurring payments automatically — directly from a customer's UPI-linked bank account, without requiring any action from the customer after the initial setup. For subscription businesses, EMI providers, insurance companies, and utility operators, it is one of the most significant payment infrastructure improvements India has seen in years.

This guide explains exactly how UPI AutoPay works, how to set it up as a merchant, and the practical details that determine whether your recurring revenue actually arrives on time.

What UPI AutoPay Is — and How It Differs from NACH

Before UPI AutoPay, Indian businesses running subscription models had two main options for automatic debits: NACH (National Automated Clearing House) mandates and credit card auto-pay. Both work, but both have friction. NACH requires customers to fill out a physical or scanned form, submit bank account details, and wait days for the mandate to be activated. Credit card auto-pay works only for customers who have a card — which excludes a large portion of India's population.

UPI AutoPay, launched by NPCI in 2020, is an e-mandate system built natively on the UPI rails. A customer authorises a recurring payment mandate directly through their UPI app — no paperwork, no waiting period, no separate bank form. The entire setup takes under two minutes on a smartphone, and the mandate is active immediately.

The underlying technology is the UPI e-mandate (also called UPI recurring payments). Unlike a one-time UPI transaction, a mandate is a standing instruction registered against a customer's VPA (Virtual Payment Address) that allows the merchant to initiate debits on a defined schedule without requiring the customer to approve each payment individually.

How UPI AutoPay Mandates Work: The Technical Flow

Step 1: Mandate Registration

The merchant creates a mandate request specifying the amount, frequency (daily, weekly, monthly, quarterly, yearly, or as-presented), start date, and end date (or perpetual). This request is sent to the customer's UPI app via a notification or a deep link/QR code. The customer opens their UPI app, reviews the mandate terms, and authorises it using their UPI PIN. The mandate is then registered with the customer's bank (called the payer PSP) and NPCI.

Step 2: Pre-Debit Notification (Mandatory)

This is a requirement many merchants overlook. At least 24 hours before each debit is executed, the merchant must send a pre-debit notification to the customer. This notification goes to the customer's UPI app and informs them of the upcoming charge — the amount, date, and merchant name. Customers have the right to pause or revoke the mandate during this window. The pre-debit notification is not optional; NPCI mandates it for every debit under UPI AutoPay.

Step 3: Debit Execution

On the scheduled date, the merchant's payment gateway initiates a debit request through the NPCI infrastructure. If the customer's account has sufficient funds and the mandate is active, the debit is processed and funds settle into the merchant's account. Settlement typically happens within T+1 business days.

Step 4: Notification to Both Parties

After a successful debit, both the merchant and customer receive transaction confirmation notifications. If a debit fails — due to insufficient funds, a frozen account, or a revoked mandate — the merchant receives a failure notification with a reason code, which allows for automated retry logic.

Transaction Limits, Rules, and Categories

UPI AutoPay has specific limits set by RBI and NPCI that you must design your billing around:

• Transaction limit: Up to ₹1,00,000 per transaction for most categories. For certain specified categories (mutual funds, insurance, credit card bill payments, loan repayments, and a few others), this limit was raised to ₹2,00,000 per transaction as of 2023. For generic subscriptions, the ₹1 lakh cap applies.
• UPI PIN requirement: For mandates where each debit is ₹15,000 or less, no UPI PIN is required at debit time (only at mandate creation). For debits above ₹15,000, customers may need to authenticate with their UPI PIN for each debit.
• Pre-debit notification: Mandatory, minimum 24 hours before the debit. Most payment gateways handle this automatically if configured correctly.
• Mandate frequency types: Daily, weekly, fortnightly, monthly, bimonthly, quarterly, half-yearly, yearly, and "as-presented" (one-time or irregular amounts within a cap).
• Variable amount mandates: You can set up mandates with a maximum cap rather than a fixed amount, allowing for usage-based billing up to the authorised cap. The customer must consent to the maximum amount at mandate creation.

Setting Up UPI AutoPay as a Merchant

You cannot directly integrate with NPCI as a small merchant. You need a payment gateway or payment aggregator that has built UPI AutoPay support into their API. The major options in India are:

Razorpay

Razorpay's "Subscriptions" product supports UPI AutoPay natively. You create a subscription plan, the customer checks out via Razorpay, and the mandate registration flow is handled entirely by Razorpay's checkout. Pre-debit notifications, retry logic, and webhook callbacks for payment events are all managed through the Razorpay dashboard and API. Razorpay charges a percentage per transaction (typically 2% for domestic payments) plus plan fees for subscription management.

Cashfree Payments

Cashfree has strong UPI AutoPay support and is particularly well-regarded for its API documentation and webhook reliability. Their "Auto Collect" and subscription APIs support mandate creation, modification, and cancellation with granular control. For tech-forward businesses building custom billing systems, Cashfree is a competitive option.

PayU

PayU supports UPI AutoPay through their recurring payments API. It is widely used by larger enterprises and established businesses. The integration is more complex than Razorpay's but offers more customisation for high-volume use cases.

CCAvenue

CCAvenue supports recurring billing including UPI AutoPay mandates. It is one of the older gateway options in India with wide bank compatibility. The dashboard is less modern than Razorpay's but it remains a solid choice for businesses that already use CCAvenue for their one-time payment processing.

Use Cases Where UPI AutoPay Makes the Most Sense

• SaaS and software subscriptions: Monthly or annual plan billing without manual renewal. Particularly effective because your customer base is already comfortable with digital payments.
• Gym and fitness memberships: Monthly fee collection without the chase. Members set up the mandate once; you collect on the 1st of every month automatically.
• EMI-based lending and BNPL: Fintech companies use UPI AutoPay extensively for loan repayment schedules. Predictable debit dates improve cash flow forecasting for lenders.
• Insurance premiums: Health, life, and vehicle insurance companies use it to collect monthly or quarterly premiums instead of relying on annual lump-sum payments.
• Utility bills: Electricity, water, and broadband providers are adopting UPI AutoPay for autopay registration, reducing late payment incidents.
• Coaching centres and tuition fees: Monthly fee collection for education businesses — one of the highest-friction collection scenarios in India.
• Newspaper and magazine subscriptions: Daily, weekly, or monthly content subscriptions with small per-transaction amounts (sub-₹15,000, so no PIN required at debit time).

Handling Mandate Failures and Retries

Even well-configured UPI AutoPay mandates will experience failures. Common failure reasons include insufficient funds (the most frequent), account frozen or dormant, technical errors at the payer's bank, and customer-initiated mandate suspension.

Every payment gateway provides failure reason codes via webhooks. Your system should handle failures with the following logic:

• Insufficient funds: Retry after 2–3 days. Most gateways allow a configurable retry schedule. Sending a customer notification via SMS or email before the retry improves success rates.
• Mandate revoked by customer: Do not retry. Trigger a re-registration flow — send the customer a new mandate creation link. Combine this with a support touchpoint to understand why they revoked it.
• Technical errors: Retry automatically after a short delay. These typically resolve without customer action.
• Grace periods: Define a grace period (e.g., 7 days after failed debit) during which the customer retains service access while you attempt recovery. Cutting off service immediately on failure dramatically increases churn.

UPI AutoPay vs Credit Card Subscriptions vs NACH

Note that UPI has a 0% MDR (Merchant Discount Rate) for person-to-merchant transactions as per NPCI and government policy. This makes UPI AutoPay significantly cheaper than credit card subscriptions for businesses where margins matter.

RBI Compliance Requirements

UPI AutoPay falls under RBI's framework for recurring online transactions. Key compliance points for merchants:

• The pre-debit notification to the customer is legally required and must go out at least 24 hours before the debit date.
• Customers must have a clear and easy mechanism to modify or cancel their mandate. This cannot be buried in a support ticket flow.
• Mandate creation must include explicit consent — auto-enrollment without customer action is not permitted.
• For mandates above ₹15,000 per debit, additional authentication (AFA — Additional Factor of Authentication) is required by the customer's bank at the time of each debit execution.
• Keep records of mandate registration and debit history. These may be required in dispute resolution processes.

Best Practices to Reduce Churn from Mandate Failures

Payment failure is one of the leading causes of involuntary churn — customers who wanted to continue but were dropped because a payment didn't go through. Here's how to minimise it:

• Send a pre-debit reminder via WhatsApp or SMS, not just the NPCI notification. Many customers don't check their UPI app notifications. A WhatsApp message saying "Your monthly payment of ₹499 will be deducted tomorrow — ensure sufficient balance" dramatically improves success rates on first attempt.
• Schedule debits mid-month. The 1st and 5th of the month are when everyone's rent and EMIs hit. Scheduling your debit on the 10th or 15th means customer accounts are more likely to have cleared salary credits.
• Build a dunning flow. Dunning is the process of communicating with customers after a failed payment. A sequence of 3–4 touchpoints (notification + retry + personal outreach) recovers significantly more revenue than a single retry.
• Offer multiple payment methods at re-registration.If a UPI AutoPay mandate fails permanently, offer the customer the option to pay via credit card, net banking, or a fresh mandate. Each additional option increases recovery probability.
• Track your payment failure rate by payment gateway.If your failure rate is consistently above 5–8%, it may indicate a gateway-specific issue, not a customer behavior issue.

Getting Started

For most Indian SMBs, Razorpay Subscriptions is the fastest path to live UPI AutoPay collection. Their dashboard-driven setup requires minimal technical knowledge, and their documentation covers the full mandate lifecycle. If you need more API control or are building a custom billing system, Cashfree is worth evaluating for its developer experience.

The fundamental shift UPI AutoPay represents is this: instead of hoping customers will pay, you create the conditions for payment to happen automatically. For any business that has struggled with monthly fee collection, this infrastructure change can meaningfully improve cash flow predictability and reduce the administrative burden of chasing receivables.

If you're building a subscription billing workflow into your broader business operations — alongside invoicing, inventory, and customer management — see how Friendly brings these together: Explore Friendly for Indian SMBs →