UPI AutoPay for Global SaaS: Setup, Limits and Rules
UPI AutoPay for Global SaaS: Setup, Limits and Rules
Global Payments

Published on 20/11/2026

UPI AutoPay for Global SaaS: Setup, Limits and Rules

Collect recurring payments from Indian subscribers

Talk to Xflow about UPI AutoPay, settled to you abroad.

A SaaS company based outside India can use UPI AutoPay for SaaS renewals from Indian customers by working with a cross-border payment aggregator that onboards merchants based abroad. Your customer approves the mandate once in their UPI app, each renewal is debited in rupees, and the provider pays you out abroad in your own currency.


The key limit is per charge. A renewal of up to Rs 15,000 can be debited without the customer approving it again, while anything above that needs their fresh authentication each time. That one line decides whether UPI AutoPay suits your monthly, annual or usage plans, which is why it shapes most of your setup choices.


To use it well, you need to know how a mandate is created and run and how to price plans around the per-debit limit. You also need to know when renewals can be debited, what happens when one fails, and how to set everything up without an Indian company.


How a UPI AutoPay mandate is created and how each renewal runs

A UPI AutoPay mandate is a standing permission your customer gives once, inside their own UPI app, so you can debit renewals later without asking each time. Your provider shows the request at checkout, and the customer's bank holds the mandate. Here is what happens from first click to each renewal:


  1. Checkout - your provider shows a UPI intent button on mobile or a QR code on desktop, since providers must offer both for mandate registration, with the first debit amount shown separately.
  2. Approval - the customer opens their UPI app, checks the merchant name and amount, and approves with their UPI PIN, which counts as the extra authentication step.
  3. Amount type - the mandate is either a fixed amount or a variable amount, and for variable mandates the customer sets the most any single renewal can be.
  4. First debit - the first charge is authenticated too, and it can run alongside registration, within five minutes, if it is Rs 15,000 or less.
  5. Renewals - later debits run on schedule, each preceded by a notice that carries the Unique Mandate Number (UMN) your customer can match to the plan.


Your customer is notified at every step, from registration and each debit to any pause or cancellation. The customer sets the end date at registration, and the National Payments Corporation of India (NPCI) caps a mandate at 30 years.


UPI AutoPay limit per debit and how to design plans around it

The UPI AutoPay limit per debit is the single rule that decides whether UPI recurring payments work for your plans. It applies to each charge, not to the mandate as a whole, so a plan priced under the line renews quietly while a plan above it turns every renewal into a manual approval for the customer.


That makes the limit a pricing question as much as a payments one. Before you switch UPI AutoPay on, list every plan you sell in India in rupees, including tax, and check which side of the line each renewal falls on. Plans under the line need no change, while plans above it need a different billing pattern.


What the Rs 15,000 line covers and what sits above it


Under the Reserve Bank of India (RBI) e-mandate framework, any recurring debit of up to Rs 15,000 per transaction can run without the customer authenticating again. Above that, the customer's bank must ask them to approve that specific charge with the extra authentication step, so the renewal is no longer automatic. You can read how the wider RBI e-mandate rules apply to cards and UPI separately.


A higher Rs 1 lakh line exists, but it is not open to software subscriptions. RBI reserves it for insurance premiums, mutual fund subscriptions and credit card bill payments only. A mutual fund subscription is an investment, not a software plan, so your SaaS renewals sit under the Rs 15,000 line whatever your customer's bank or account type.


The NPCI UPI Consolidated Circular of 18 September 2026 applies the same line to UPI AutoPay and sets no separate cap on the mandate. The only other ceiling is the maximum your customer chose when approving a variable mandate. To stay clearly inside the line, price at Rs 14,999 or less rather than exactly Rs 15,000.


Example of monthly, annual and usage plans against the limit


Common plan types are priced here in rupees, as debited from the customer. The same line applies to individual and business customers, and your payout still arrives in your own currency, whichever one you settle in.

Plan (amount debited)Customer typeAgainst the Rs 15,000 lineWhat renewal looks like
Rs 999 monthlyIndividualWell insideRenews without the customer approving again
Rs 9,999 yearlyIndividualInside, Rs 5,001 to spareRenews without the customer approving again
Rs 24,000 yearlyBusinessRs 9,000 overCustomer must approve each renewal, or you split it into four Rs 6,000 quarterly debits
Rs 10,000 monthly on a Rs 1,20,000 yearly contractBusinessInside each monthMonthly debits renew quietly; one yearly debit would need approval
Rs 500 to Rs 20,000 usageBusinessMixedCharges up to the line pass; anything above needs approval

Annual, enterprise and usage-based plans that cross the limit


If a plan sits above the line, you have four practical ways to keep renewals working:


  • Split the billing - charge an annual price as quarterly or monthly debits that each stay at Rs 14,999 or less, so renewals keep running without the customer stepping in.
  • Accept approval each time - keep a single yearly debit above the line and plan for your customer approving it in their app, with reminders built into your renewal emails.
  • Invoice large contracts - for enterprise deals, a one-off payment against an invoice often suits a finance team better than a mandate they must approve every year.
  • Cap usage charges - ask the customer to set the variable mandate maximum at or under the line, and bill any usage above it as a separate charge the customer approves.


A price rise above the maximum the customer agreed is not something you can push through alone. Your provider must give customers a way to modify the amount, and the customer approves the change in their UPI app, so give them notice and a clear prompt well before the new price takes effect.

Card mandate or e-NACH for annual plans

A card mandate (including RuPay cards) or an e-NACH bank mandate are other ways to collect annual or high-ticket plans, each with its own rules. The same Rs 15,000 per-debit rule applies to cards.


Pre-debit notification timing and NPCI peak hours for AutoPay renewals

Two timing rules shape every renewal: the notice your customer receives before the debit, and the hours in which a debit may be sent. Both are handled by your provider and the customer's bank, but your billing schedule has to leave room for them, or renewals start failing for reasons that have nothing to do with the customer.


Your provider must start the notice at least 24 hours before the debit, and must send the debit itself outside peak hours. Send each renewal to your provider at least a day before the charge date, and expect the debit time to follow India-time windows rather than your own.


The 24-hour rule and which party owns each step


The customer's bank and UPI app send the pre-debit notification at least 24 hours before each charge. It names you, the amount, the date and time, the UMN and the reason for the debit, through a channel the customer picks, such as SMS or email.


Your provider has to start that notice at least 24 hours before the debit, which means your billing system must hand over the amount and date in good time. You do not send the notice yourself. After the debit, the customer gets a second message with the same details plus how to raise a complaint.

StepWho handles itWhat you need to do
Schedule the renewalYouSend the amount and date to your provider early
Start the pre-debit noticeYour providerConfirm it is started at least 24 hours ahead
Deliver the noticeCustomer's bank and appNothing; the customer gets it directly
Debit and post-debit noticeProvider and customer's bankMark the renewal paid or failed

Peak hours and the windows left for renewal debits


NPCI defines peak hours as the busy periods currently observed between 10:00 and 13:00 and between 17:00 and 21:30, India time. Renewal debits must be sent outside those hours and at a moderated pace, so your provider runs them before 10:00, between 13:00 and 17:00, or after 21:30.


These rules bind your provider, not you directly, and they cover the debit only, not the customer setting up a mandate. Convert the India-time windows in your billing tool rather than fixing an offset by hand, since daylight saving changes it for much of the year. A renewal you expect at midnight in your time zone may land at a different hour.


What happens when a renewal debit fails or the customer revokes

A failed renewal does not end the mandate, but the number of tries is fixed and the customer stays in control throughout. Knowing both rules lets you plan dunning emails and grace periods that match what your provider can actually do, instead of promising a retry that will never run.


Ask your provider to return the failure reason for each try, because the follow-up differs. A revoked or missing mandate means you stop billing and remove it on your side, while a debit that missed its notice or window can still use the tries left in that cycle.


Why NPCI allows one attempt and three retries per renewal


For each billing cycle, NPCI permits one attempt and up to three retries, so four tries in all, and retries also have to run outside peak hours. A debit does not go through when the mandate has been revoked, when the notice was not started 24 hours ahead, or when it is sent outside the allowed window.


If all four tries fail, the renewal for that cycle is over. Your next step sits outside UPI AutoPay, such as an email asking the customer to pay the open invoice by another method. Ask your provider how they space the three retries, because the timing they choose affects how quickly you can follow up with the customer.


When the customer pauses, changes or revokes the mandate


Your customer can pause a single renewal or revoke the mandate at any time from their UPI app. Your provider must also let them revoke from your own website or app, and that request goes to the UPI AutoPay system rather than only removing the record on your side.


  • Pause - you must support it, so skip that cycle's debit and keep the subscription status clear in your account area.
  • Revoke - once a debit fails because the mandate no longer exists, remove it on your side, stop billing and mark the plan as lapsed.
  • Move apps - customers can move a mandate between UPI apps up to three times in 90 days, and the mandate keeps working.
  • Refunds - a refund on a renewal debit goes back to the customer's account through your provider, so ask for the timeline in writing.

Can a foreign SaaS company offer UPI AutoPay without an Indian entity?

Yes, through a payment aggregator for cross-border payments (PA-CB), a firm authorised by RBI. A PA-CB can onboard merchants based abroad directly and accept Indian payment methods for them, so you keep selling from your home company. Check which methods each one supports, including UPI AutoPay.


An Indian subsidiary gives you a local entity and a domestic payment account, at the cost of registration, tax filings and local staff. If some customers will pay once rather than subscribe, you can also accept UPI payments from India for one-off charges, often through the same provider. For UPI AutoPay for SaaS sold from abroad, a cross-border provider is the lighter option.

RouteWho sells to the customerWho holds the mandate setupWhat you set up
Cross-border provider (PA-CB)Your companyThe provider, with Indian banksA merchant account with the provider
Indian subsidiaryYour Indian entityA domestic payment providerA company, bank account and tax registrations in India

What about a merchant of record?

A merchant of record resells your product and becomes the seller your customer pays, so it handles payment and tax in its own name. You trade control of the customer relationship and pricing for less admin.

When you compare providers, check that recurring billing covers UPI AutoPay alongside cards. A provider that lets you accept international payments from India without an Indian entity can collect from Indian customers and settle to your existing overseas account, so your current banking and accounting stay in place.


How to set up UPI AutoPay for SaaS through a cross-border provider

When you set up UPI AutoPay for SaaS through a cross-border provider, the provider must meet the NPCI rules on notices and retries, and must offer pause, revoke and amount changes. Your work is pricing, billing schedules and customer messages, since recurring payment setups vary widely between providers.


These steps run from signing up with a provider to your first live renewal. Each one maps to a rule covered earlier, so you can check your plans, timing and failure handling against the same limits before any customer is charged.


Steps from provider onboarding to your first live renewal


  1. Check your plans - map each price in rupees against the Rs 15,000 line and decide how to handle any plan above it.
  2. Open a merchant account - complete the provider's business checks as a company based outside India.
  3. Add the checkout - place the provider's UPI AutoPay option next to cards, with intent on mobile and QR on desktop.
  4. Set the schedule - send each renewal date and amount early enough for the 24-hour notice, and let the provider pick debit windows outside peak hours.
  5. Handle outcomes - listen for success, failure, pause and revoke events and update the subscription status in your system.
  6. Test a live renewal - run a small real plan before launch to see the notice, debit and payout end to end.

Tax on sales to Indian customers

Selling software to Indian individuals usually means your company registers for Indian GST and pays IGST at the standard services rate, while registered Indian businesses pay it themselves under reverse charge. Your provider or tax adviser can confirm what applies to you.

Questions to ask a provider in writing before you commit


Your customer experience depends on how the provider meets each NPCI duty, so get these answers in writing before you sign:


  • Notice timing - do you start the pre-debit notification at least 24 hours before each debit, and what cut-off do you need from us?
  • Retry spacing - how do you space the one attempt and three retries for each renewal, and which windows outside peak hours do you use?
  • Revoke and pause - do you give our customers a revoke option on our site or app, and can we support pausing a single renewal?
  • Amount changes - how do customers modify the mandate amount when we change a price, and what do they see in their app?
  • Refunds and payout - how long do refunds on renewal debits take, and when does each payout reach our account in our own currency?

Collecting subscriptions from Indian customers with Xflow and settling in your currency

We are Xflow, and we help businesses based outside India accept payments from Indian customers without setting up an Indian entity. We hold final authorisation from RBI as a payment aggregator for cross-border payments, granted on 18 February 2026, which is the fully approved stage.


Your customers can pay by cards including RuPay, UPI, UPI AutoPay, card mandates, e-NACH and netbanking. You receive the money in your own currency in your existing overseas bank account, with settlement at T+2, two business days after collection. Pricing depends on your volumes and plans, so speak to our team for a quote.

Collect Indian subscription renewals and get paid in your own currency


Conclusion

For most SaaS businesses abroad, UPI AutoPay for SaaS works well for Indian customers on monthly and lower-priced yearly plans, provided each debit stays at Rs 14,999 or less. Above that line, split the billing or expect the customer to approve each charge. A cross-border provider must meet the NPCI rules on notices and retries, so your job is pricing, scheduling and clear customer messages.


Start with your price list, pick a provider that answers the NPCI questions in writing, and test one real renewal before launch. Done in that order, UPI AutoPay can sit beside cards as a second way your Indian customers keep their plans running.


Frequently asked questions

Your customer pays nothing to set up or use a UPI mandate, under the RBI e-mandate framework. NPCI also bars surcharges on UPI payments, and any convenience fee a merchant adds must be shown before the customer picks UPI.

Yes. Customers approve with their UPI PIN, get notice 24 hours before each debit, and can pause or revoke at any time.


For you, the risk is that a customer can cancel whenever they like, so no renewal is certain to be collected.

Yes, with a variable mandate. The customer sets a maximum per charge, and each debit must stay within it. Debits up to Rs 15,000 run without fresh approval, while anything above needs the customer to authenticate that charge.

NPCI allows one attempt and up to three retries for each renewal, so four tries in total. Each must run outside peak hours. After that, collect that cycle's payment another way, such as an emailed invoice.

No. A payment aggregator for cross-border payments (PA-CB) authorised by RBI can onboard merchants based outside India directly, so you sell from your home company and receive payouts abroad.

The customer's bank and UPI app send it at least 24 hours before the debit. Your provider must start it in time, and you supply the amount and date. You do not send it yourself.

Only within the maximum the customer approved. A rise above it needs the customer to modify the mandate and approve the change in their UPI app, so warn them early and explain the new price clearly.

Related Posts