UPI mandate: how recurring debits work
 

How a UPI mandate works for recurring debits

A UPI mandate separates consent from collection. The customer approves the recurring payment arrangement once inside a UPI app, and later debits can run within the approved amount, frequency, and validity.

That distinction matters at UPI's current scale. NPCI product statistics show 720 banks live on UPI in May 2026, with 23.20 billion transactions worth ₹29.90 lakh crore. When subscriptions move onto that rail, the renewal experience depends less on checkout design and more on how the mandate lifecycle is managed.

What a UPI mandate permits

UPI Autopay is the customer-facing feature for recurring payments on UPI. NPCI's UPI Autopay guidelines describe the feature as a way to create a mandate for recurring payments and note that customers can pause or revoke the mandate anytime from the UPI app.

At setup, the merchant or payment gateway initiates a mandate request. The customer's UPI app shows the merchant, amount, frequency, validity period, and debit account. The customer enters the UPI PIN to authenticate the mandate. After that, future debits do not need repeated approval when they stay within the mandate and regulatory limits.

A mandate is not a standing instruction with unlimited room. It is a bounded permission. If a subscription plan moves above the approved maximum amount, the merchant needs fresh customer authentication rather than silently increasing the debit.

The lifecycle from setup to cancellation

The lifecycle has five stages that operations and engineering teams need to track together.

1. The merchant creates a mandate request through a PSP (Payment Service Provider), payment gateway, subscription system, or API integration.

2. The customer authenticates mandate registration in their UPI app using the UPI PIN.

3. Before a scheduled debit, the issuer or payment ecosystem sends the customer a pre-transaction notification.

4. On the debit date, the merchant or gateway executes the debit request, and the result flows into subscription, invoice, and payment settlement workflows.

5. If the customer pauses, modifies, or revokes the mandate, the merchant treats that event as a subscription-state change, not only as a failed payment.

This is where recurring debit operations differ from one-time UPI collections. A one-time payment ends once it succeeds or fails. A mandate stays alive, so the system needs status, next debit date, notification, execution result, and cancellation state.

Debit rules decide renewal outcomes

The RBI's Digital Payments-E-mandate Framework,2026 applies to recurring transactions using cards, prepaid payment instruments, and UPI. It requires additional factor authentication at mandate registration, gives customers a facility to withdraw the e-mandate, and requires pre-transaction notification at least 24 hours before debit.

The same framework sets the core limits. Recurring transactions may be processed without additional AFA (Additional Factor of Authentication) up to ₹15,000 per transaction. Insurance premiums, mutual fund subscriptions, and credit card bill payments may be processed without additional AFA up to ₹1,00,000 per transaction. Transactions above the applicable limit require customer authentication.

Earlier RBI circulars give the history. The 2019 card e-mandate circular set the original AFA (Additional Factor of Authentication), notification, and withdrawal pattern; the 2020 recurring e-mandate circular noted its extension to UPI. The 2026 framework is the current reading.

Where UPI Autopay fits best

UPI Autopay fits India-native recurring collections where the customer is comfortable approving a UPI mandate: SaaS subscriptions, memberships, education fees, utility bills, insurance premiums, mutual fund SIPs, and EMIs. It is strongest when the amount is predictable and the customer expects app-level mandate control.

It is not the only recurring payment rail. e-NACH can still fit some high-value bank-account mandates, and card mandates remain important for card-led or cross-border subscriptions. The practical choice depends on customer preference, debit value, notification expectations, and cancellation flow.

Managing mandates inside Zoho Payments

Zoho Payments supports UPI mandates for subscription-based businesses, including mandate creation, scheduled payment execution, and mandate tracking. For API-led teams, the Mandates developer documentation explains the enrollment and execution flow for collecting recurring payments through UPI.

The useful operating layer is visibility. The Mandates module shows created mandates and recurring payments collected through them, while mandate events can be connected to invoice, subscription, and payment API workflows. That keeps the debit record close to the billing record.

Conclusion

A UPI mandate works because the customer approves before the debit runs. The merchant's job is to preserve that pattern: create the mandate clearly, notify before debit, execute within the limit, record the result, and react quickly when the customer pauses or revokes. Recurring debits are reliable only when consent, timing, and status stay in sync.