Selling subscriptions, SaaS or memberships in India? Here's how recurring payments work via UPI AutoPay and card e-mandates, the RBI 2026 e-mandate rules and limits, and how to set it all up with a payment gateway.
If you sell anything on a subscription - SaaS, a membership, a content plan, EMIs or repeat orders - you do not want to chase customers for payment every cycle. In India, automated recurring payments run on two rails: UPI AutoPay and card e-mandates. Both are tightly regulated by the RBI, and the rules were consolidated in 2026. Here is how to set it up the right way.
For most India-first subscription businesses, lead with UPI AutoPay and offer cards as a fallback.
The RBI's consolidated E-mandate Framework took effect on 21 April 2026 and applies to recurring payments across UPI, cards and prepaid instruments. The key rules every merchant should know:
You do not implement these rules yourself - a compliant payment gateway handles the mandate registration, notifications and limits for you. But you should understand them, because they shape churn (the 24-hour notice gives customers a clear cancel moment) and your pricing (keep per-cycle charges under Rs.15,000 where possible to avoid extra friction).
Recurring payments are a payment-gateway feature, so the decision comes down to which gateway fits you. Compare them in our best payment gateway for startups in India guide, learn the basics of accepting UPI on your website, or browse every option in the Payments category.
RBI rules, limits and gateway features change. Confirm the current e-mandate limits and your gateway's subscription capabilities before launching.
Turn this research into a workflow with apps, stages, caveats, and next actions.
Start with the product itself: a place to write and ship code, host it reliably, and catch errors in production, because nothing else matters until customers can actually use what you built. Next, get the team coordinated with project management and a shared knowledge base so work and decisions are not lost in chat. Then put customer acquisition on a real CRM so leads, demos, and deals are tracked rather than living in inboxes. Add billing and accounting once you have paying users, choosing payment rails that fit whether you sell to India, abroad, or both, and keep GST-clean books from day one. Finish with customer support, product analytics, and access security so you can keep users happy, see what they actually do, and not get breached. Do not buy enterprise sales, analytics, and security suites before you have product-market signal; sequence around shipping and getting your first paying customers.
View stack
Start by choosing the right no-code platform for what you are building, because a customer-facing web app, a mobile app, and an internal portal each suit different tools. Next, model your data cleanly in a database or spreadsheet backend, since a messy data model is the most common reason no-code projects collapse later. Then build the interface and logic so users have real screens and workflows, not just a database. Add payments, forms, and automations to connect your app to the outside world and remove manual work. Finish by launching, securing team access, and measuring usage so you know the app works and is safe. Do not expect no-code to scale infinitely; it is excellent for validating and running real workflows, but be honest about its ceilings and plan to move to custom code if you outgrow it.
View stack
Start by choosing a website builder that matches your skill and needs, because the builder decides how fast you launch and what you can do later. Sort your domain and hosting next, remembering that most builders bundle hosting while self-hosted WordPress needs its own, so you do not pay twice. Then design and write the site so it looks credible and explains clearly what you offer, since a confusing site loses visitors in seconds. Add lead capture, booking, and payment tools so the site actually does something, whether that is collecting enquiries, taking appointments, or selling. Finish by getting found and measuring, with basic SEO, a Google presence, and analytics so you know what is working. Do not over-build a complex site before you have visitors; launch a clear, fast site and improve it with real data.
View stack
Describe your actual business goal and FindThatSoftware will map the apps, trade-offs, setup stages, and buying caveats.
Build a pipeline