The RBI E-Mandate Limit and How It Should Shape Your Pricing

There is a number in the RBI’s recurring payments framework that quietly decides how well your subscription business runs: the per-transaction limit below which a registered mandate can be debited without the customer authenticating that individual charge.

Get your pricing under it and renewals are invisible. Go over it and every renewal becomes a task you are asking your customer to complete.

The number

For most merchant categories the limit is ₹15,000 per transaction. The RBI raised it from ₹5,000 in 2021 and again in 2023, and raised it further to ₹1,00,000 for a specific set of categories — insurance premiums, mutual fund subscriptions and credit card bill payments.

For a typical ecommerce subscription — a box, a replenishment order, a membership — the number you are working with is ₹15,000.

Why it matters more than it sounds

A charge above the limit does not fail. That would at least be obvious. What happens is worse: the customer is asked to approve it, and approval is a thing that requires them to notice a notification, open an app, and act within a window.

Plenty of people do not. Not because they want to cancel — because they were in a meeting.

So a plan priced above the limit has a structurally higher renewal failure rate than the same plan priced below it, entirely independent of how good your product is. You are converting a silent background process into a task, once per cycle, for every customer.

How to price around it

Prefer monthly to annual above the threshold. ₹1,250/month clears silently twelve times. ₹15,000/year needs approval once — but if that approval does not happen, you lose the whole year rather than one month.

Use prepaid for large commitments. A prepaid plan takes one payment at checkout, where the customer is already authenticating and expecting to. There is no recurring mandate to debit against later, so the limit does not apply to the renewals — because there are no renewals, only scheduled deliveries against money already collected.

This is the single most useful structural trick for Indian subscription pricing, and it is why Super Subscription treats prepaid as a first-class plan type rather than an add-on.

Register mandates with headroom. A mandate carries a maximum amount, and it does not have to equal today’s price. Registering a ₹999 plan with a ₹1,500 mandate maximum means a later price increase, a GST change or an add-on does not break the standing instruction. Registering at exactly ₹999 means any change forces re-authorisation, and re-authorisation is churn.

Split large orders where the product allows. If a customer wants ₹24,000 of product a year, two ₹1,000/month subscriptions to different product lines both sit inside the limit. This is not always sensible, but for multi-product stores it sometimes is.

The reporting consequence

Track renewals that fail because of authentication separately from renewals that fail for funds. They look identical in a naive dashboard and they need completely different responses:

• Funds failure → retry on a schedule, send a dunning email, offer a payment method update.
• Authentication not completed → remind, and make the approval one tap. Retrying does not help; the customer never declined, they just did not act.

If your subscription app shows you one number called “failed payments”, you cannot tell these apart, and you will apply the wrong fix to half of them. See why Indian subscription payments fail.

Frequently asked questions

What happens if a subscription charge is above the e-mandate limit?

The debit does not execute automatically. The customer receives a request to authenticate that specific transaction, and the charge only completes once they do. If they do not, the renewal fails even though nothing is wrong with their account.