Saturday, 21 November 2026 Tracking Indian retail every day
Retail Tech Explainer

UPI AutoPay for Indian retailers explained

A plain guide to UPI AutoPay mandates: how a recurring debit is set up, authorised, charged and cancelled, what the pre-debit notice requires, and where recurring payments fit for Indian retailers.

UPI AutoPay for Indian retailers explained

The short answer

UPI AutoPay is a recurring payment mandate that a customer approves once in their UPI app, allowing a merchant to debit a fixed or variable amount on a schedule. The customer gets a pre-debit notification before each charge, can pause or revoke the mandate anytime, and the merchant needs clear cancellation and failure handling.

Key takeaways

  • UPI AutoPay is a customer-approved recurring mandate with a maximum amount, frequency and validity, debited on schedule without a fresh PIN each time.
  • A pre-debit notification must reach the customer before each charge, so billing calendars and registered mobile numbers need to be accurate.
  • Plain UPI merchant payments have run without MDR, but proposed UPI MDR changes are still unresolved, with no official confirmation of dates, so confirm aggregator fees for mandates and debits.
  • AutoPay suits subscriptions, memberships, EMI, wallet top-ups and repeat grocery baskets, especially where shoppers already pay digitally.
  • Retailers must handle debit failures, revoked or expired mandates and easy cancellation, or recurring revenue turns into support cost.

UPI AutoPay is a recurring payment instruction that a customer sets up once in their UPI app, giving a merchant permission to debit their bank account on a schedule. It is a mandate — a standing authorisation with a maximum amount, a frequency and an end date — rather than a fresh payment each time. The customer approves it with their UPI PIN, and every later debit runs against that approval until the customer pauses, revokes or the mandate expires.

For a retailer, that changes the maths of repeat revenue. A subscription box, a gym membership, a milk route, a wallet top-up or an EMI plan no longer depends on the customer remembering to pay. The catch is that the customer holds the switch, and the process has rules you must build into your checkout, billing and support systems.

How does a UPI AutoPay mandate get set up and authorised?

The flow has four parties: the customer, the merchant (or the merchant's payment aggregator), the customer's bank (the issuer), and NPCI, which runs UPI. A typical setup looks like this:

  1. Customer chooses AutoPay at checkout. Your app shows the amount or cap, the frequency (daily, weekly, monthly, as-and-when), and the period.
  2. Merchant creates a mandate request. Your payment partner sends it to NPCI with a unique mandate reference, the payee, the maximum debit amount and the validity.
  3. Customer authorises in their UPI app. They see the merchant name, cap and schedule, and approve with their UPI PIN. No PIN, no mandate.
  4. Mandate is registered and confirmed. The issuer bank registers it and NPCI confirms back to the merchant, often with a mandate ID you store against the customer record.
  5. Debits run on schedule. On each due date, the merchant or aggregator raises a debit against the mandate, within the approved cap.

Two details matter in practice. First, the maximum amount is a ceiling, not a promise — a variable-amount mandate lets you charge less, but never more than the cap. Second, the mandate has a validity period, so a 12-month plan needs renewal or a fresh authorisation.

What is the pre-debit notification and why does it matter?

Before each debit, the customer must receive a pre-debit notification — a message, usually by SMS or in-app, telling them the merchant, the amount and the date of the coming charge. This is the customer's chance to check the amount and pause or cancel if something looks wrong.

The notification is not a formality. It is the main protection against surprise charges, and it is why a customer who forgets a subscription still gets a reminder. For retailers, it means your billing calendar must be planned ahead: raise the debit only after the notice window, keep the amount consistent with what was notified, and make sure the customer's registered mobile number is current. If your system debits without a valid notice, expect disputes and chargebacks.

What does UPI AutoPay cost a retailer?

Plain person-to-merchant UPI has run without a merchant discount rate (MDR) — the fee a merchant pays to accept a digital payment — which is why UPI became the default rail for small shops. The pricing picture is moving, though. According to media reports, a proposed MDR on select high-value UPI transactions was first set for 15 October 2026 and then deferred, with no new date confirmed; no official confirmation of either date has been issued. Separately, media reports say NPCI's UPI and Services Steering Committee cleared a flat ₹5 MDR on merchant-to-merchant UPI payments, though it has not been formally notified, and no rollout date has been announced.

For AutoPay specifically, costs usually come from your payment aggregator or bank as a platform or per-mandate fee rather than a plain UPI charge. Ask your provider for three numbers: the mandate creation fee, the per-debit fee, and the fee for a failed debit or a revoked mandate. Small per-debit charges add up fast on low-ticket daily debits.

Where does UPI AutoPay fit for Indian retailers?

Recurring payments suit any business where the same customer pays again on a predictable rhythm:

  • Subscriptions: monthly boxes, OTT-style content, SaaS tools, curated kits.
  • Memberships: gyms, clubs, loyalty programmes with a paid tier.
  • EMI and instalments: large-ticket electronics or furniture split into monthly parts.
  • Wallet top-ups: automatic reload when a balance falls below a threshold.
  • Repeat grocery orders: a standing weekly basket for milk, eggs, staples.

The festive data points one way. MobiKwik reported an 80% year-on-year rise in Diwali-period GMV to ₹3,018 crore for 6-9 November 2026, with Tier 2 cities and beyond generating over 78% of location-tagged GMV on Diwali day, 8 November 2026, according to a company filing reported by media on 20 November 2026. Shoppers outside metros are paying digitally in volume. If you sell a recurring service there, AutoPay removes the monthly friction of a fresh UPI transfer.

Worked example (hypothetical): Say a Bengaluru dairy brand sells a monthly staple box at ₹1,200 and signs up 2,000 customers on a variable-amount UPI AutoPay mandate with a ₹1,500 cap. Monthly collections are ₹24 lakh if every mandate debits cleanly. If 6% fail — expired cards, insufficient balance, revoked mandates — that is 120 customers and ₹1.44 lakh at risk each month. At a per-debit fee of ₹2, the brand pays ₹4,000 a month in debit charges, plus a mandate-creation fee of, say, ₹5 per new sign-up. The real cost is the failed 6%, not the fees.

What failure and cancellation cases must retailers handle?

Recurring payments fail more often than one-time checkouts because the customer is not watching. Build for these cases:

  • Insufficient balance or debit failure: retry within the mandate rules, but do not spam. Send a clear message and a one-tap link to pay manually.
  • Mandate revoked or paused by the customer: your next debit will be rejected. Detect it early and offer a re-authorisation flow instead of a dunning email chain.
  • Expired mandate: validity ends, so plan a renewal nudge well before expiry.
  • Amount disputes: if a customer says they were charged more than expected, check the cap and the pre-debit notice first.
  • Cancellation requests: customers can revoke in their UPI app, but many will ask you. Make cancellation easy in-app and confirm it in writing, or you invite complaints.

Common mistakes: hiding the recurring nature of the payment at checkout, setting a cap far above the real price, debiting without a valid pre-debit notice, and treating a failed debit as a churned customer without a recovery attempt.

What it means for Indian retailers

UPI AutoPay turns a one-time buyer into a predictable revenue line, and it does so on the rail Indian shoppers already trust. The trade-off is operational: you inherit a billing calendar, a notification obligation, a failure-recovery process and a cancellation path. Retailers who build those well get lower collection costs and better retention. Those who treat AutoPay as a set-and-forget button get disputes, revoked mandates and support tickets. Start with one recurring product, measure the failure rate for three cycles, then scale.

In this story

Frequently asked questions

Is UPI AutoPay safe for customers?

Yes, within limits. The customer approves the mandate with a UPI PIN, sets a maximum amount, and gets a pre-debit notification before each charge. They can pause or revoke the mandate anytime in their UPI app, which stops future debits.

Can a merchant change the AutoPay amount?

Only up to the approved cap. A variable-amount mandate lets the merchant debit less than the maximum, but never more. Charging above the cap will fail, and inconsistent amounts invite disputes.

What happens if a UPI AutoPay debit fails?

The debit is rejected, usually for insufficient balance or a revoked or expired mandate. The merchant should retry within mandate rules, notify the customer and offer a manual payment link rather than treating the customer as churned.

How does a customer cancel a UPI AutoPay mandate?

They can revoke it in their UPI app under the mandates section, or ask the merchant. Retailers should make in-app cancellation easy and confirm it in writing to avoid complaints.

Does UPI AutoPay cost the merchant an MDR?

Plain UPI merchant payments have run without MDR, but the fee picture is in flux. According to media reports, a proposed UPI MDR has been deferred with no officially confirmed date, and a flat ₹5 B2B MDR was reportedly cleared but not notified, with no rollout date announced. Check your aggregator's mandate and per-debit fees.

WiseRetail

The week in Indian retail, ecommerce and D2C — in one short email every Friday.