Recurring payments remove the need for customers to manually pay every invoice, subscription renewal, premium, or installment. For an Indian business, two common bank-account-based options are UPI AutoPay and eNACH. Both use a customer-approved mandate, but they differ in how that mandate is created, how customers interact with it, and which collection scenarios they suit.
UPI AutoPay often works well for mobile-first, relatively frequent payments. eNACH is commonly considered for account-based collections, including higher-value or long-running mandates. The right choice depends on your customers, ticket size, billing frequency, bank coverage, and operational needs—not on one rail being universally better.

Table of contents

• What are UPI AutoPay and eNACH?
• UPI AutoPay vs eNACH at a glance
• How mandate setup and collection differ
• Which factors should a business compare?
• Which method fits common business use cases?
• Should you offer both methods?
• How PayU can support recurring payments
• FAQs

What are UPI AutoPay and eNACH?

• UPI AutoPay

UPI AutoPay is NPCI’s recurring-payment capability on the Unified Payments Interface. A customer creates an electronic mandate through a supported UPI app and approves its amount, frequency, and validity. The business can then initiate eligible recurring debits according to that mandate.
NPCI provides customer controls such as pause, unpause, modification, and revocation through supported UPI apps. A pre-debit notification is generally sent before execution, subject to current rules and exceptions.

• eNACH

eNACH is the electronic mandate capability within the National Automated Clearing House ecosystem. NACH is designed for high-volume, repetitive, and periodic interbank transactions. Instead of signing and submitting a paper mandate, a customer can authenticate an electronic mandate through supported channels such as net banking, debit card, or Aadhaar-based flows, depending on the bank and implementation.
Once the mandate has been accepted, the business presents debit instructions through its bank or payment partner. eNACH is widely associated with loan installments, insurance premiums, investments, education fees, and other account-based collections.

UPI AutoPay vs eNACH at a glance

Factor	UPI AutoPay	eNACH
Customer setup	Approves a mandate in a supported UPI app	Authenticates an electronic bank mandate through a supported channel
Best-known experience	Mobile-first and app-led	Bank-account-led and suitable for structured collections
Customer identifier	UPI ID and linked account	Bank account and mandate details
Common use cases	Subscriptions, bills, memberships, premiums, investments	EMIs, premiums, SIPs, fees, subscriptions, other repetitive debits
Amount treatment	Thresholds vary by category and authentication requirement	Limits vary by authentication variant, bank, and current scheme rules
Customer controls	Mandates can be managed in supported UPI apps	Amendment or cancellation follows the bank/NACH process offered
Operational consideration	UPI-app and issuer support, notifications, execution rules	Sponsor/destination-bank coverage, mandate acceptance, return handling

This table is directional. A merchant should confirm current limits, eligible categories, live banks, debit timing, and authentication requirements with its payment provider before launch.

How mandate setup and collection differ

With UPI AutoPay, the customer usually selects UPI during subscription setup, chooses or opens a UPI app, reviews the mandate, and authorizes it with the required UPI credential. This can be a relatively short journey for an active UPI user. After registration, the customer can see the mandate within the supported app and may pause or revoke it.
With eNACH, the customer provides mandate information and moves into a bank-authentication journey. The exact flow depends on the available mode and participating bank. NPCI’s procedural guidance describes internet banking, debit-card authentication, and Aadhaar-based variants. The mandate must be accepted before a debit can be initiated.
For both methods, registration and collection are separate events. A registered mandate permits a debit within the agreed terms; it does not guarantee success. Insufficient funds, an expired or revoked mandate, bank controls, or technical issues can cause failure.

Which factors should a business compare?

1. Customer preference and device behavior

Start with how customers already pay. A consumer subscription product may benefit from a UPI-native journey. A lender, insurer, school, or B2B service may need account-based coverage aligned with eNACH.
Measure mandate-start, approval, and first-debit success separately. A familiar option is useful only if customers can complete the flow across the banks and apps that matter to your business.

2. Transaction value and category

Do not build a billing policy around an old headline limit. NPCI currently describes ₹15,000 as the standard UPI AutoPay auto-debit threshold without additional authentication, with enhanced treatment up to ₹1 lakh for specified categories such as mutual-fund subscriptions, insurance premiums, and credit-card bill payments. eNACH limits differ by authentication variant and scheme rules.
Your provider may also apply supported-use-case, bank, or risk controls. Confirm the precise mandate and debit limits for your merchant category before deciding which customers see each option.

3. Mandate flexibility

Consider whether the amount is fixed or variable, how often it changes, the approved maximum, and the mandate duration. A fixed monthly plan is simpler than a variable utility bill or installment schedule.
Make the mandate terms easy to understand. Show the frequency, amount or maximum amount, start and end dates, cancellation method, and what happens after a failed debit.

4. Bank and app coverage

Check live issuer, destination-bank, UPI-app, and authentication-mode coverage through your provider. Compare it with the bank and payment preferences in your customer base.
Create a fallback path when a customer’s preferred bank or app does not support the required flow. That could mean offering the other mandate rail, a card mandate, or a manual payment option.

5. Collection and recovery operations

Recurring revenue depends on more than mandate registrations. Your team needs reliable status updates, pre-debit communication where required, idempotent debit initiation, return-reason handling, retries that follow scheme rules, and reconciliation back to the customer and invoice.
Track mandate approval, first-debit and renewal success, failures, recovery, cancellations, and support contacts by rail.

Which method fits common business use cases?

UPI AutoPay may be a strong first option for OTT services, software subscriptions, memberships, utility payments, and other mobile-first recurring purchases where the amount and frequency are easy to understand.
eNACH may be a better fit for structured bank-account collections such as loan installments, insurance premiums, education fees, and long-duration mandates—particularly when the required value, customer segment, or institutional process does not fit a UPI-first journey.
These are not rigid categories. Mutual funds and insurance, for example, may support multiple mandate routes. A business should evaluate actual customer completion and debit performance within its permitted use case.

Should you offer both methods?

For many businesses, the practical answer is yes. A hybrid strategy lets customers choose a suitable mandate route and gives the business a fallback when bank, app, category, or amount constraints affect one option.
However, adding a method also adds testing and support work. Build a common internal mandate model with clear states such as initiated, pending, active, paused, revoked, expired, and failed. Store provider references, process webhook updates safely, and prevent duplicate debit requests. Present customers with a simple choice rather than the complexity of the underlying rails.

How PayU can support recurring payments

PayU’s recurring-payments capabilities support subscription collections through payment instruments including cards, Net Banking and UPI AutoPay. Businesses can evaluate API integration, dashboard-based options, or subscription automation based on their technical and operational needs.
A consolidated setup can help teams manage mandate creation, payment status, and recurring collection workflows without designing a separate integration for every rail. Support still varies by bank, app, merchant category, payment instrument, and approval. Review the latest PayU recurring-payment documentation and confirm current requirements before implementation.

FAQs

1. Is UPI AutoPay the same as eNACH?

No. Both enable mandate-based recurring debits, but UPI AutoPay uses the UPI ecosystem and a supported UPI app, while eNACH uses NPCI’s NACH mandate and bank-account infrastructure.

2. Which method supports higher-value recurring payments?

It depends on the use case, authentication requirement, bank, and current rules. eNACH is often evaluated for higher-value account-based mandates, while UPI AutoPay has category-specific thresholds. Verify live limits with your provider rather than relying on a universal figure.

3. Can a customer cancel a recurring mandate?

Yes, mandate-management mechanisms exist for both rails. UPI AutoPay supports controls such as revocation through supported apps. eNACH cancellation or amendment follows the available bank and NACH process. Businesses should make cancellation instructions easy to find.

4. Can a business offer UPI AutoPay and eNACH together?

Yes. Offering both can improve coverage for a mixed customer base, provided the business can manage mandate states, notifications, failures, reconciliation, and support consistently.

5. Does an active mandate guarantee payment?

No. A debit can fail because of insufficient funds, account restrictions, an expired or revoked mandate, validation errors, bank controls, or technical issues. Businesses need a compliant retry and customer-communication process.