UPI Autopay vs eNACH: Comparison for Indian Businesses

Indian businesses are moving from one-time collections to repeat billing as digital payments become more deeply embedded in everyday transactions. NPCI’s total transaction volumes grew 33% year-on-year in FY2025, rising from 16,100 crore transactions in FY2024 to 21,360 crore transactions in FY2025. OTT platforms, SaaS tools, lenders, insurers, gyms, and education providers all depend on timely recurring payments. When collections rely on manual reminders, delays can quickly affect cash flow. Delayed payments remain a major issue for Indian businesses, with around ₹8.1 lakh crore locked in delayed MSME payments, according to the Economic Survey 2025–26.

UPI Autopay and eNACH (sometimes called an e-mandate) are the two primary ways Indian businesses collect recurring payments with customer consent. Both let a customer approve a mandate once and have subsequent payments debited automatically. UPI Autopay runs through the customer’s UPI app and is built for speed. eNACH runs through bank-based authentication and is built for larger or longer-term collections.

This guide compares both options on mandate limits, settlement mechanics, setup time, customer experience, and use cases, so you can pick the method (or combination of methods) that fits your billing model. For a broader look at how PayU supports recurring billing across both rails, see the recurring payments suite.

What Is UPI Autopay?

UPI Autopay lets customers approve future debits directly through their UPI app. Businesses often search for “what is UPI Autopay” when they want a simple way to collect repeat payments without asking customers to pay each cycle manually.

Once a customer approves the mandate, payments follow the agreed amount, date, and frequency automatically. This makes UPI Autopay a good fit for subscription payments, app plans, donations, memberships, and utility bills.

Because customers already use UPI for daily payments, the approval experience feels familiar, and businesses that already accept UPI find the move to repeat collections straightforward. It also supports real-time payment processing during mandate setup.

UPI Autopay mandate limits are set by NPCI and revised periodically. As commonly published, routine recurring payments (OTT, SaaS, gym memberships, utility bills) are generally supported up to roughly ₹15,000 per transaction without additional authentication, while select categories such as insurance premiums, mutual fund subscriptions, and credit card bill payments have had a higher AFA-free ceiling. Limits change from time to time, so confirm the current threshold with your bank or payment partner before going live.

What is the eNACH Mandate?

eNACH is an electronic mandate system that authorises a business to debit funds from a customer’s bank account on a set date, without a fresh approval for every transaction. It’s often described as an e-mandate, and businesses evaluating recurring billing usually compare it directly against UPI Autopay.

An eNACH mandate is typically authorised through bank channels such as net banking, a debit card, or another bank-supported authentication method. Once approved, the business can collect payments as specified in the mandate.

eNACH supports a wider transaction range than UPI Autopay, starting from very small amounts and, depending on the authentication method and mandate category, extending well beyond UPI Autopay’s ceiling for high-value use cases such as loan EMIs or large insurance premiums. As with UPI Autopay, these thresholds are set by RBI and NPCI guidelines and are revised periodically; treat any specific figure as indicative and confirm current limits with your bank or payment gateway before setup.

eNACH is commonly used for EMIs, insurance premiums, education fees, rent, and loan repayments. The bank-verified mandate provides a clear record of customer consent, which matters for regulated or higher-value collections.

Types of Mandates: UPI Autopay vs eNACH

Both methods support more than one mandate configuration, and picking the right type affects both approval rates and the customer experience.

1. UPI Autopay mandate types

• Fixed-amount mandates: the customer authorises one recurring amount, such as a flat subscription fee. Most subscription billing uses this type.
• Variable-amount mandates: the debit amount can change within a pre-approved ceiling, useful for usage-based billing where the exact charge isn’t known in advance.

2. eNACH mandate types

• API-based (electronic) mandates: authorised digitally through net banking or a debit card, with faster turnaround than paper-based mandates.
• Aadhaar-based e-mandates: authenticated via Aadhaar OTP or biometric verification, common for lending and insurance onboarding.
• Physical NACH mandates: the traditional paper-based mandate, still used where digital authentication isn’t available, but slower to activate.

For most digital-first subscription businesses, a fixed-amount UPI Autopay mandate paired with an API-based eNACH mandate for higher-value customers covers the majority of billing scenarios.

How UPI Autopay Works

The flow is simple: the customer chooses UPI, receives a mandate request in their UPI app, reviews the details, and approves it using a UPI PIN.

Once approved, future debits happen automatically within the set limit and schedule, without the customer needing to take action again until the mandate needs to be renewed or the amount changes.

This makes UPI Autopay a good fit for recurring billing where the amount is fixed or predictable, and it generally gives digital-first customers a faster setup journey than bank-based alternatives.

How eNACH Works

The eNACH journey begins when the business creates a mandate request. The customer approves it through a bank-supported method; the bank validates the details, and the mandate is activated.

Because the bank has to verify the mandate, eNACH setup can take longer than UPI Autopay; that additional validation step is part of why eNACH is often preferred for higher-value or longer-term collections.

Once active, the eNACH mandate continues to authorise repeated debits automatically, without requiring the customer to re-approve each individual payment.

Key Differences Between UPI Autopay and eNACH

These are two ways of making recurring payments, but they’re not equal. Here is a quick comparison:

Settlement Mechanics: How and When Funds Reach Your Business

For merchants, the mandate type is only half the picture: what happens after a debit succeeds matters just as much for cash flow planning.

With both UPI Autopay and eNACH, a successful mandate debit is settled to the merchant’s account according to the settlement cycle agreed with their payment gateway, not instantly at the moment of debit. Settlement timing depends on the payment partner’s processing schedule, the payment mode, and any risk or compliance checks applied to the transaction.

Because settlement timelines and cut-offs can vary by payment gateway, merchant category, and mandate type, businesses should confirm current settlement schedules directly with their payment partner rather than assuming a fixed timeline applies across all recurring payment modes. For PayU merchants, settlement behaviour for recurring collections is documented as part of the recurring payments suite and the PayU developer documentation.

Reconciliation is another practical consideration: recurring billing at scale means matching thousands of individual mandate debits back to specific invoices or subscription cycles. A payment partner that provides clear reporting and reconciliation tools for recurring transactions reduces the manual finance-ops work involved in tracking settlements against billing records.

Handling Failed Payments and Retries

Recurring billing at any scale will run into failed debits: insufficient balance, an expired mandate, a bank-side decline, or a customer who has switched banks. How that failure is handled affects both recovered revenue and customer experience.

• Automatic retries: Many payment gateways support configurable retry logic, attempting a failed debit again after a set interval rather than requiring the business to manually re-trigger collection.
• Customer notifications: Timely notifications (SMS, email, or in-app) before and after a failed debit give customers a chance to top up their balance or update payment details before the account falls further behind.
• Mandate health monitoring: Tracking mandate status (active, paused, expired, revoked) helps businesses catch a lapsed mandate before it causes a string of failed collections.
• Manual fallback: For high-value eNACH failures in particular, having a manual payment link as a fallback avoids a full loss of the transaction when an automated retry also fails.

UPI Autopay failures are typically visible to the customer immediately within their UPI app, which can prompt faster self-correction. eNACH failures are usually communicated by the bank and may take longer for the customer to notice, which is one reason some businesses pair eNACH with proactive reminder messaging.

Security and Compliance Safeguards

Both UPI Autopay and eNACH are consent-based mandate systems, and both operate under RBI and NPCI frameworks for recurring payments, including requirements such as pre-debit notification and defined mandate limits for transactions above certain thresholds.

UPI Autopay mandates are authenticated using the customer’s UPI PIN, and payments run within the National Payments Corporation of India’s UPI infrastructure. eNACH mandates are authenticated through bank-supported channels (net banking, debit card, or Aadhaar-based verification) and are governed by NACH rules administered by NPCI.

For businesses, this means neither method should be treated as “set and forget.” Mandate limits, authentication requirements, and pre-debit notification rules are periodically updated by the regulator, and payment gateways typically update their systems to stay compliant. Rather than relying on a fixed understanding of the rules, businesses should verify current requirements with their payment partner, particularly before launching a new recurring billing product or entering a higher-value use case such as lending or insurance.

Using UPI Autopay and eNACH for Lending and EMI Collections

Lenders, NBFCs, and insurers have some of the most demanding recurring collection needs: high compliance requirements, a mix of ticket sizes, and customers who may be less digitally native than a typical SaaS subscriber.

eNACH is generally the primary rail for EMI and loan repayment collections because it supports higher transaction values and bank-verified consent, which matters for regulated lending products. Aadhaar-based eNACH mandates, in particular, are widely used in lending onboarding flows because they can be completed digitally without requiring net banking access.

UPI Autopay is increasingly used alongside eNACH for smaller-ticket lending products, for example, short-tenure personal loans or BNPL-style repayments, where faster mandate setup and a familiar UPI approval experience can improve completion rates during onboarding.

A hybrid setup (eNACH for larger or longer-tenure loans, UPI Autopay for smaller or shorter-tenure products) lets lenders match the collection method to the risk and ticket size of each loan category. Payment gateways that support both mandate types through a single integration, like PayU’s recurring payments suite, reduce the engineering effort needed to run this kind of hybrid collection strategy.

How to Choose the Right Option for Your Business

There’s no single “better” option between UPI Autopay and eNACH: the right choice depends on your ticket size, billing frequency, customer base, and how much setup friction you can accept at onboarding.

• Subscription and SaaS businesses billing small, predictable amounts (OTT, apps, memberships): UPI Autopay is usually the better fit: fast setup, mobile-first approval, and low friction for digital-first customers.
• Lenders, NBFCs, and insurers collecting EMIs or premiums: eNACH is usually the better fit: bank-verified consent, support for higher transaction values, and a stronger audit trail for regulated collections.
• Education providers and landlords collecting fees or rent on a fixed schedule: eNACH is common, though UPI Autopay can work well if amounts fall within its limits and the payer base is comfortable with UPI.
• Businesses with a mixed customer base or a product line spanning both small and large ticket sizes: a hybrid setup (supporting both mandate types through one payment gateway integration) usually serves the business better than committing to a single rail.

In practice, many merchants end up running both. An auto-debit-capable payment gateway that supports UPI Autopay and eNACH side by side, handles failed-payment retries, and gives consolidated reporting removes the need to choose one method exclusively. Before committing, confirm current mandate limits, settlement timelines, and pricing for recurring transactions with your payment partner. See PayU’s pricing page for current rates and the developer documentation for integration details.

Conclusion

Both UPI Autopay and eNACH solve the same underlying problem: collecting repeat payments without relying on customers to pay each cycle manually. But they do it differently. UPI Autopay is fast and mobile-first, which suits everyday digital subscriptions. eNACH is bank-verified and built for larger or longer-term collections, which suit lending, insurance, and other regulated use cases. For many businesses, the most practical setup uses both: UPI Autopay for smaller, frequent payments, and eNACH for higher-value or longer-tenure billing, through a single payment gateway integration that supports both mandate types.

FAQs

1. What is UPI Autopay?

UPI Autopay lets customers approve scheduled debits from their UPI app. Businesses often explore what is UPI autopay for faster repeat collections.

2. What is eNACH mandate?

An eNACH mandate is a digital approval that allows scheduled debits from a customer’s bank account. It is useful when a formal bank mandate is preferred.

3. How does UPI Autopay work?

For anyone asking how does UPI autopay work, the customer approves a mandate in a UPI app. Future debits follow the approved schedule.

4. How does eNACH work?

Businesses that ask how does eNACH work should know that it runs through bank authentication. Once the eNACH mandate is verified, collections can begin.

5. Which option is better for subscription payments?

UPI is usually better for smaller and frequent plans. eNACH may be better for larger or long-term collections.

6. Can both options support recurring billing?

Yes. Both can support recurring billing, but their setup process and use cases are different.

7. Should my business choose one or both?

A business can choose UPI Autopay if it needs fast, mobile-first recurring collections for smaller payments. eNACH may be better for higher-value or longer-term bank-linked payments. Many businesses may benefit from using both through an auto debit payment gateway.

8. What are the transaction limits for each?

The maximum amount allowed for recurring payments with UPI Autopay is ₹15,000. The limit for certain categories, like paying credit card bills, insurance premiums and mutual fund subscriptions, can be up to ₹1 lakh without additional verification. The eNACH limits are subject to change depending on the bank, the type of the mandate, the authentication path, and the payment gateway configuration.

9. How long does it take to activate a mandate?

UPI Autopay mandates can usually be activated faster because customers approve them directly through a UPI app. eNACH mandates may take longer because the customer’s bank has to verify and approve the mandate.

10. What happens if a payment fails due to insufficient funds?

If a payment fails due to insufficient funds, the debit may not go through on the scheduled date. Depending on the payment gateway and mandate setup, the business may be able to retry the payment, notify the customer, or ask the customer to complete the payment manually.

11. What types of mandates are available under UPI Autopay and eNACH?

UPI Autopay supports fixed-amount and variable-amount mandates. eNACH supports API-based (electronic) mandates, Aadhaar-based e-mandates, and traditional physical NACH mandates, depending on the authentication method used.

12. When are funds from a UPI Autopay or eNACH debit settled in my business?

Settlement follows the schedule agreed with your payment gateway rather than happening instantly at the moment of debit. Because timelines vary by payment partner, mandate type, and merchant category, confirm the current settlement schedule directly with your payment gateway.

13. Is UPI Autopay or eNACH safe for recurring collections?

Both are consent-based mandate systems governed by RBI and NPCI frameworks, authenticated through a UPI PIN or bank-supported verification, respectively, with regulatory requirements such as pre-debit notification for recurring transactions.

14. Which option works better for loan EMI or NBFC collections?

eNACH, particularly Aadhaar-based mandates, is generally preferred for EMI and loan collections because of bank-verified consent and support for higher transaction values. UPI Autopay is increasingly used for smaller-ticket lending products where faster setup improves onboarding completion.

15. How much does it cost to set up UPI Autopay or eNACH for my business?

Costs vary by payment gateway, transaction volume, and mandate type. Check your payment partner’s current pricing page rather than relying on a general figure.