Why Indian Subscription Payments Fail (And What Fixes Each One)

In most markets a failed subscription renewal means one of two things: no money, or a dead card. Retry logic and a dunning email cover almost everything.

In India there is a third category, and it is often the largest: the mandate is the problem, not the money. Retrying a mandate failure does nothing except burn attempts.

Here is the taxonomy, and the correct response to each.

1. No mandate was ever registered

What happened. The order completed at checkout but the mandate registration did not. The customer believes they subscribed. Your system believes they subscribed. There is no standing instruction to debit against.

Symptom. The first renewal fails, roughly 30 days after signup, with an error that often looks generic.

Fix. Prevention, not recovery: your app must verify mandate registration succeeded before confirming the subscription. After the fact, the only route is asking the customer to set it up again — which many will not do, because as far as they are concerned they already did.

This is the most damaging failure in the list because it is silent for a month and then unrecoverable.

2. The mandate was revoked by the customer

What happened. The customer cancelled the mandate in their bank or UPI app, without touching your cancellation flow.

Symptom. Renewal fails with a mandate-not-found or revoked status. Your portal still shows an active subscription.

Fix. Treat this as a cancellation signal, not a payment failure. Retrying is pointless. The right response is to mark the subscription as needing re-authorisation and send a re-subscribe link — and to count it separately in your churn numbers, because it is voluntary churn that happened outside your funnel.

3. The charge exceeds the mandate maximum

What happened. You registered a mandate for ₹999 and are now charging ₹1,299 — a price rise, an add-on, or a GST change.

Symptom. Consistent failures across many subscribers at once, correlated with a price change.

Fix. Register mandates with headroom above the current price. A mandate maximum is a ceiling, not a commitment — registering at ₹1,500 for a ₹999 plan costs the customer nothing and survives a future increase. Retrofitting requires re-registration, so this is one to get right at launch. See the e-mandate limit.

4. The amount is above the AFA threshold

What happened. The charge is above the per-transaction limit, so the customer must approve this specific debit. They did not — usually because they did not notice, not because they declined.

Symptom. High failure rate concentrated on your expensive plans.

Fix. Two options. Reprice below the limit, or restructure to prepaid so there is one authenticated payment instead of recurring debits. Reminders help at the margin; structure helps more.

5. The pre-debit notification was not sent

What happened. The 24-hour notification did not go out, and the debit was rejected or disputed.

Symptom. Failures that correlate with your notification job rather than with anything about the customer.

Fix. Make the billing attempt conditional on the notification having been sent, and alert on notification job failures. See pre-debit notification rules.

6. Actually insufficient funds

The familiar one. This is the case where retries and dunning work — and in India it is worth timing retries around salary dates rather than on a fixed offset, because the pattern is strongly monthly.

Why the distinction matters

If your dashboard collapses all of these into “failed payments”, you will respond to all of them with retries and dunning emails. That is the right treatment for exactly one of the six.

Super Subscription separates mandate failures from funds failures in reporting and routes them differently — re-authorisation flows for the former, retries and dunning for the latter.

More on the general case in failed subscription payments.

Frequently asked questions

Why do Indian subscription renewals fail more often than international ones?

Because a renewal depends on a valid mandate as well as available funds. A mandate can expire, be revoked in the customer's banking or UPI app, or be registered for an amount lower than the current price — none of which are funds problems and none of which a retry fixes.