The "Indian SaaS" Context
The ₹2 line: why ₹14,999 and ₹15,001 behave completely differently
To a pricing page they look like rounding. To the RBI e-mandate framework they are two different products — one renews itself, the other asks permission every month.
Two SaaS plans, one priced at ₹14,999 a month and one at ₹15,001, look like rounding on a pricing page. To the RBI e-mandate framework, they are two different products. One renews itself quietly. The other asks the customer for permission every single month.
Most founders discover this two rupees at a time, after the renewals on their highest plan start failing.
What the ₹15,000 line actually does
Under the Digital Payments – E-mandate Framework, 2026, recurring debits below ₹15,000 per transaction execute on the registered mandate with no per-debit customer intervention. At or above ₹15,000, the customer must complete a fresh Additional Factor of Authentication before each debit. The higher ₹1,00,000 ceiling exists only for insurance premiums, mutual-fund subscriptions, and credit-card bills — SaaS is not in that exempt set.
₹14,999 renews itself. ₹15,001 asks permission every month. Two rupees, two completely different retention problems.
A pricing decision, not a compliance footnote
Every renewal above the line reintroduces manual friction — at exactly your highest-value accounts. The customer has to be brought back to authenticate, and any step a customer has to complete is a step some customers will not. So the threshold quietly raises involuntary churn precisely where each lost account costs the most.
| Plan price | Debit behaviour | Retention implication |
|---|---|---|
| Below ₹15,000/mo | Auto-debits on the mandate, no per-cycle action | Lowest payment friction; recovery is mostly soft declines |
| ₹15,000 and above | Fresh AFA required before every debit | Friction at every renewal; your best accounts face it most |
The packaging options
There are three honest moves, and which one fits depends on your product and buyer.
| Option | Trade-off |
|---|---|
| Keep the flagship monthly under ₹15,000 | Cleanest collection, but caps monthly ARPU at the line |
| Move high-ARPU plans to annual | One authentication a year instead of twelve — but a larger upfront commitment to ask for |
| Stay above the line, invest in the AFA moment | Full pricing freedom, but you must make the monthly authentication easy and expected |
Annual billing changes the AFA maths entirely — one approval a year rather than twelve monthly friction points. Just watch the other side of it: a larger single commitment can raise cancellation anxiety at renewal.
If you are already above the line
You cannot wish the AFA away. The move is to make the authentication moment easy and expected rather than a surprise: a friendly heads-up before the bank's mandatory 24-hour notice, a clear instruction on exactly what to approve, and the right channel to do it on. Authentication that the customer is expecting succeeds far more often than authentication that arrives as a confusing bank SMS.
Where SubsShield fits
SubsShield surfaces which of your renewals cross the ₹15,000 line and drives the customer through the authentication step with the right message at the right time — so a debit that needs AFA actually gets it. It diagnoses and communicates; it does not move money.
So how many of your customers sit above ₹15,000 a month — and have you mapped the exact action each one must take before that debit can clear?
Divya Nair, Fractional CFO · guest writer
Divya is a fractional CFO working with Indian SaaS startups. She writes about revenue quality and the finance side of retention — how involuntary churn distorts valuation, why the ₹15,000 AFA line is a pricing decision, and what investors actually price.