A Step-by-Step Guide to Implementing Recurring Payment Solutions for Indian Fintechs

By WovLab Team | March 21, 2026 | 11 min read

Understanding India's Recurring Billing Landscape: UPI AutoPay, e-NACH, and Card Mandates

For any Indian fintech aiming to build a sustainable revenue stream, mastering recurring payments is not just an advantage; it's a necessity. The landscape for recurring payment solutions in India has evolved dramatically, moving from clunky, paper-based processes to a sophisticated digital ecosystem. Understanding the three primary pillars of this ecosystem is the first step towards building a frictionless subscription experience. These pillars are UPI AutoPay, e-NACH (Electronic National Automated Clearing House), and Card Mandates. Each serves different use cases, transaction values, and customer segments.

UPI AutoPay has revolutionized low-to-mid-value recurring transactions. Leveraging the ubiquity of the Unified Payments Interface, it allows users to set up mandates directly from their UPI app for amounts up to ₹1,00,000. This method is perfect for SaaS subscriptions, OTT platforms, and any service where a quick, mobile-first setup is crucial for conversion. The user experience is seamless, often involving a single-click authentication within a familiar app.

For higher-value transactions like loan EMIs, insurance premiums, or B2B service contracts, e-NACH is the workhorse. As a digital evolution of the physical mandate process, it facilitates debits directly from a customer's bank account. While the setup can involve an extra step of net banking or debit card authentication, its reliability and high transaction limits make it indispensable for enterprise-grade billing. Finally, Card Mandates on debit and credit cards remain a popular choice, governed by RBI's guidelines which mandate an Additional Factor of Authentication (AFA) at setup and strict pre-debit notifications, ensuring a high degree of security and consumer trust.

Choosing the right mix of these methods is critical. A B2C app might prioritize UPI AutoPay for its low friction, while a lending platform would be unable to operate without a robust e-NACH and card mandate infrastructure.

Choosing Your Payment Gateway: Razorpay vs. Stripe vs. PayU for Subscription Models

Once you've understood the payment methods, selecting the right payment gateway is the most critical decision you'll make. A gateway is more than just a processor; it's your partner in managing subscriptions, handling compliance, and recovering revenue. In India, the three dominant players for subscription models are Razorpay, Stripe, and PayU, each with distinct strengths.

Razorpay has established itself as the de-facto leader for Indian businesses. Its Subscriptions product is feature-rich, offering out-of-the-box support for UPI AutoPay, e-NACH, and card mandates. Their API documentation is developer-friendly, and they offer powerful tools like automated "smart retries" for failed payments. For businesses focused squarely on the Indian market, Razorpay often provides the quickest path to market with the most comprehensive set of local payment options.

Stripe, a global powerhouse, brings world-class API design and exceptional developer experience to the table. While historically stronger in international markets, Stripe has invested heavily in its Indian operations, now offering robust support for UPI and card mandates. Its key differentiator is scalability; if your fintech has global ambitions, Stripe's unified platform for managing payments across multiple countries is unparalleled. Their pricing is transparent, and their ecosystem of tools and integrations is vast.

PayU is a veteran in the Indian payments space, known for its competitive pricing and strong relationships with large enterprises. Their subscription solutions are robust and reliable, and they often provide customized pricing for high-volume businesses. While their API might not be as universally praised as Stripe's, their deep market penetration and extensive experience make them a formidable option, especially for established companies looking to optimize costs.

Technical Deep Dive: Integrating Subscription APIs for Seamless Billing Automation

Integrating a subscription billing system is not a one-time setup; it's about building an automated engine that runs your revenue model. While specific code varies, the architectural flow of integrating with a gateway like Razorpay or Stripe is remarkably consistent. The entire process hinges on a few core API objects and, most importantly, a robust webhook handling system.

The lifecycle of a subscription typically follows these steps, which you will orchestrate via API calls:

1. Create a Customer: The first step is to create a customer object in your payment gateway's system. This involves passing basic information like name, email, and phone number. The gateway returns a unique customer_id, which you must store in your local database against your user's record. This ID is the anchor for all future billing activities.
2. Define a Plan: You then create a plan object. This defines the commercial terms: the billing amount, the currency (INR), the billing frequency (e.g., monthly, yearly), and the number of billing cycles. The gateway returns a plan_id. You can create multiple plans for different service tiers (e.g., Basic, Pro, Enterprise).
3. Create the Subscription: This is the key action where you tie a customer to a plan. You make an API call to create a subscription, passing the customer_id and plan_id. The gateway then generates a secure checkout link or initiates a process for the user to complete the mandate authentication (e.g., redirecting to their UPI app or bank's portal for e-NACH).
4. Handle Webhooks: You cannot rely on the API response alone to know the subscription status. You must expose a secure endpoint (a webhook URL) in your application that the payment gateway can call to notify you of events asynchronously. This is the most critical part of the integration.

Your webhook handler must be designed to listen for and process key events, such as:

• subscription.authenticated: The customer has successfully authorized the mandate. You can now provision the service.
• invoice.paid or charge.succeeded: A recurring payment was successfully debited. Update the user's service validity period.
• charge.failed: An attempted debit failed. Trigger your dunning management process.
• subscription.cancelled: The user has cancelled their subscription. Deprovision the service at the end of the current billing cycle.

A well-architected webhook system is the central nervous system of your billing automation. It ensures your application state is always in sync with the payment gateway, eliminating manual reconciliation and preventing revenue leakage.

Smart Dunning Management: How to Proactively Handle Failed Payments and Reduce Churn

Even with a perfect integration, payments will fail. This is a fact of life in the world of recurring billing. The reasons are numerous: insufficient bank balance, expired cards, lost cards, or technical glitches at the bank's end. How you handle these failures is what separates high-growth fintechs from those that bleed revenue. This process is called dunning management, and a smart, automated approach can recover a significant percentage of failed payments and reduce involuntary churn.

Most modern payment gateways provide built-in dunning tools. Your job is to configure them intelligently. A best-practice dunning strategy is not aggressive; it's communicative and helpful. It should be a multi-stage, multi-channel process:

• Stage 1: Smart Retries: The first failure should trigger an automatic retry logic. Don't just retry the next day. Use "smart retry" features that leverage machine learning to attempt the debit at an optimal time (e.g., on the 1st or 5th of the month, when salaries are typically credited). Configure 2-3 such retries over a week.
• Stage 2: Proactive Communication: As soon as the first payment fails, send an automated but friendly email and SMS/WhatsApp notification to the customer. Don't sound accusatory. Frame it as a technical issue: "Hi [Name], we were unable to process your payment for [Service]. This can sometimes happen due to bank issues. Please ensure you have sufficient balance. We will try again in 3 days."
• Stage 3: Payment Method Update: If the failure is due to an expired or cancelled card, your communication should include a secure, one-click link for the customer to update their payment method. This avoids a phone call and empowers the customer to self-serve, dramatically increasing the recovery rate.
• Stage 4: Grace Period and Suspension: If all automated retries fail over a 10-15 day period, the system should move the subscription into a "grace period." Notify the customer that their service is at risk. Only after the grace period expires should you automatically suspend the account. This prevents accidental loss of service and data for your legitimate customers.

Effective dunning management is a form of customer service. By proactively communicating and making it easy for users to fix payment issues, you not only recover revenue but also build trust and reduce the likelihood of a customer churning out of frustration.

Ensuring Security and Compliance with RBI Guidelines for Recurring Payments

In the fintech world, and especially when dealing with the intricacies of recurring payment solutions in India, compliance is not optional—it's the bedrock of your business. The Reserve Bank of India (RBI) has laid out a comprehensive framework for e-mandates on cards, UPI, and other prepaid instruments to protect consumers and ensure a secure ecosystem. Building your system in adherence to these guidelines is non-negotiable, and failure to do so can result in heavy penalties and reputational damage.

Partnering with a compliant payment gateway like Razorpay, Stripe, or PayU is your first and most important line of defense, as they have built their platforms around these rules. However, you must also be aware of your responsibilities. The key tenets of the RBI framework include:

• Additional Factor of Authentication (AFA): The initial setup of any recurring mandate must be authenticated by the customer with an AFA. This could be a UPI PIN, a 3D-Secure password, or an OTP. This ensures explicit, verifiable consent from the cardholder.
• Pre-Debit Notification: For every single recurring debit, you are required to send a notification to the customer via SMS and/or email at least 24 hours before the actual debit. This notification must clearly state the merchant's name, the transaction amount, the date of debit, and the reason for the charge.
• Post-Debit Notification: After a successful debit, a receipt or confirmation must be sent to the customer.
• Simple Opt-Out and Modification: The customer must be provided with a clear, easily accessible online facility to view, modify, and, most importantly, cancel a recurring mandate. This functionality is often provided via a customer portal by the payment gateway itself. Hiding the "cancel" button is a direct violation of these guidelines.
• Transaction Limits: The framework sets limits. For subsequent transactions without AFA, the limit is currently ₹1,00,000 for UPI AutoPay and ₹1,00,000 for card mandates (provided the initial mandate was authenticated). Any transaction above this limit would require AFA for every debit.

Think of compliance as a feature that builds customer trust. When users know their money is safe, that they will be notified before every charge, and that they can cancel anytime, they are far more likely to subscribe to your service. A compliant gateway handles the heavy lifting, but you must ensure your own communication and business logic reinforce these principles.

Scale Your Fintech: Partner with WovLab for End-to-End Payment Automation

As we've seen, implementing effective, compliant, and scalable recurring payment solutions in India is a complex undertaking. It requires deep expertise not just in software development, but also in financial regulations, system architecture, and customer experience design. While payment gateways provide the tools, integrating them into a seamless, automated, and churn-resistant system is a significant engineering challenge. This is where WovLab transforms from a service provider into your strategic growth partner.

Simply integrating a payment API is just the beginning. True payment automation means creating a system that talks to your entire business. It means when a payment succeeds, your accounting ERP is automatically updated. When a payment fails, an AI-powered agent initiates a personalized dunning sequence. When a customer's usage crosses a certain threshold, your CRM is flagged to upsell them to a higher-tier plan. This level of end-to-end automation is what allows you to scale without linearly increasing your operational overhead.

At WovLab, we combine our multi-disciplinary expertise to build these holistic solutions:

• Payments & Dev: Our engineering teams are masters of the Razorpay, Stripe, and PayU APIs. We don't just "plug them in"; we architect robust webhook handlers, secure customer data, and build frictionless checkout experiences that maximize conversion.
• AI Agents & Ops: We go beyond basic dunning. We build and deploy custom AI Agents that can analyze payment failure data, predict churn risk, and engage customers with intelligent, personalized communication to resolve issues before they lead to cancellation.
• ERP & Cloud: We specialize in integrating payment systems with core business platforms like ERPNext. This means automated invoice generation, seamless reconciliation, and a single source of truth for your financial data, all hosted on a scalable cloud infrastructure.

Your focus should be on building an innovative fintech product, not on wrestling with payment APIs and compliance rules. WovLab provides the specialized expertise to build, manage, and optimize your entire recurring revenue stack. We handle the complexity of payments so you can focus on growth. Contact WovLab today for a free consultation and let's build your end-to-end payment automation engine.