Selling Subscriptions on WooCommerce in India: What Works

You can sell subscriptions on WooCommerce in India, but automatic renewals only work when the customer registers an e-mandate through a gateway that supports it, and each charge must stay inside RBI's rules. Under the Reserve Bank's E-mandate Framework, 2026, a recurring charge of up to ₹15,000 can go through without the customer approving it again; above that, they must authenticate each time. Fixed monthly plans under that limit renew well. Large, variable or frequently changing amounts are where subscriptions break.

This article is for founders planning a subscription box, a membership, a course or a service retainer on WooCommerce. It explains the rules in business terms, how WooCommerce and Indian gateways fit together, which designs renew reliably and which ones fail. It goes further than the short section in my payment gateway guide.

#Why subscriptions in India are different

In India the customer's bank, not the merchant, controls whether a repeat charge goes through. Many overseas tutorials assume a store can save a card and charge it every month. Here, every automatic charge needs a registered mandate and a notice to the customer first.

For a business this changes the maths. Some share of renewals will not happen on their own: a customer declines the notice, the account is short of funds, or the mandate has lapsed. A subscription business that budgets for 100% automatic renewal will be disappointed. One that designs for recovery will do well.

#What RBI's e-mandate rules require

The rules are set out in RBI's Digital Payments: E-mandate Framework, 2026 (opens in a new tab), issued on 21 April 2026. It covers recurring transactions, domestic or cross-border, made through cards, prepaid payment instruments and UPI. These are the parts a store owner needs to know.

Recurring charge limit without extra authentication

₹15,000

Minimum notice before each debit

24 hours

Limit for insurance, mutual funds and card bills

₹1,00,000

On UPI, recurring payments run through UPI AutoPay, where the customer approves the mandate in their UPI app and can manage it there later. Your gateway handles the mandate, the notifications and the debit; your store only needs to react correctly to what the gateway reports.

#How WooCommerce and the gateway split the work

Two pieces of software run a subscription store, and they do different jobs. Mixing them up is the most common cause of a bad quote.

The subscription engine lives in WooCommerce. WooCommerce Subscriptions (opens in a new tab) is a premium extension for selling products and services with recurring payments. It defines the plans, creates a renewal order on each due date, and manages pausing, cancelling and reactivating.

The payment side lives with your gateway. WooCommerce's own subscription payment gateway guide (opens in a new tab) explains two renewal types. With automatic renewal, the gateway charges the customer without any action from them. With manual renewal, the extension creates a pending order and the customer pays it with any gateway.

That guide lists the gateways with automatic renewal support through official WooCommerce extensions, and as of November 2026 the Indian gateways (Razorpay, Cashfree, PayU) are not on it. For gateways outside the list, the guide suggests contacting the developer of that gateway's extension. In practice Indian gateways publish their own subscription plugins.

Razorpay is the example I can point to with documentation. Its Subscriptions product (opens in a new tab) supports cards (tokenised under RBI guidelines), UPI AutoPay and e-mandates through netbanking, debit card or Aadhaar, with automatic retries on failed collections. Its WooCommerce plugin documentation (opens in a new tab) states that the subscriptions plugin needs WooCommerce Subscriptions installed first. On price, Razorpay's pricing page (opens in a new tab) lists card subscriptions at 0.9% on top of the platform fee, with UPI and e-mandate pricing on request, as of November 2026.

#What works reliably

Simple, predictable subscriptions renew best. The closer your offer is to "the same amount on the same day", the fewer renewals you lose.

• Fixed monthly or yearly plans under ₹15,000 per charge. These fit the no-authentication limit, so renewals run without the customer doing anything.
• Yearly plans paid up front. One payment a year means one chance of failure a year, and a discount for paying yearly is an easy offer to explain.
• A small number of plans. Three tiers are easier to test end to end than twelve.
• Sign-up and first payment together. The customer authenticates once, and the mandate is live from that moment.
• Manual renewal as a fallback. A renewal email with a "pay now" button works with any gateway and any payment method.
• Clear cancellation from the account page. Customers who can cancel easily complain less and dispute fewer charges.

#What fails, and why

Subscriptions fail quietly, which is what makes them dangerous. Nobody sees an error; revenue simply does not arrive.

The last two are technical, and they are the ones a customer never forgives: being charged but locked out, or keeping access for months without paying. Both come from the store and the gateway disagreeing about the state of a subscription.

#Designing the plan around the rules

A few commercial choices at the start avoid most of the trouble above. Make them before any development is quoted.

1. Keep each charge under the limit if you can. A ₹30,000 yearly plan will need authentication at every renewal; a ₹2,500 monthly plan will not.
2. Decide the grace period. How many days does a member keep access after a failed renewal? A few days is usually enough for a retry and a reminder, but it is a business decision, not a technical one.
3. Decide what a failed renewal looks like to the customer. An email, a WhatsApp message, a banner in their account, or all three.
4. Write the cancellation and refund terms. Customers and gateways will both ask for them.
5. Choose the gateway for its subscription product, not its headline fee. Ask which payment methods support mandates, how retries work and how you will be told when a mandate is cancelled.
6. Plan for physical goods separately. A subscription box also needs stock, dispatch dates and shipping on every cycle.

If the subscription is for access to content or a community, the access rules matter as much as the billing. My article on planning a WordPress membership site covers that half.

#What a professional set-up covers

The engine and the gateway plugin can be installed in an afternoon; making them trustworthy takes longer. This is where a developer earns the fee on a subscription project.

• Testing every path in the gateway's test mode: sign-up, renewal, failed renewal, retry, opt-out, cancellation, plan change and refund
• Confirming the store handles gateway messages correctly, including late and repeated ones
• Renewal reminder and failure emails written in plain language, with a working pay link
• A grace period that matches what you decided
• A simple report of active, due and lapsed subscribers, so you see problems the same week
• A written note of what happens in each case, for whoever handles support

This sits within WooCommerce checkout and payment gateway work, and for sites built around members, membership and directory website development.

#Do it yourself or hire help

A single plan with manual renewals is within reach of a confident store owner. Customers get a renewal email and pay as they would for any order, with no mandate involved, and for a small membership that can be enough.

Automatic renewals are different. Money moves without the customer present, the rules are specific to India, and mistakes surface as charge disputes or lost subscribers. If recurring revenue is the core of the business, have the set-up built and tested by someone who has to sign off on every path in the table above.

#Where to start

Write your plans on one page: the amount, how often it is charged, whether there is a trial, and what happens when a payment fails. Mark any charge above ₹15,000.

Then send that page to the gateway you are considering and ask which payment methods will support automatic renewal for each plan. Their answer tells you whether your pricing fits the rules or needs reshaping before anything is built.