Multi-Channel Recovery
The 26-hour window: turning the RBI pre-debit notice into trust
The cheapest payment to recover is the one that never fails. Just before each renewal there's a window where a brand-first message can make that happen — before the bank's SMS lands.
The cheapest payment to recover is the one that never fails. And there is a window, just before each renewal, where you can make that happen — if you reach the customer at the right moment, in the right voice.
Most teams only think about recovery after a debit has failed. The best ones do quiet work in the hours before it.
The 24-hour notice is a moment, not a formality
Under the RBI 2026 framework, the customer's bank must notify them at least 24 hours before each recurring debit, naming the merchant, the amount, the date, and the mandate reference. For many customers that bank SMS is the first they have thought about the charge in a month — and it lands as a small jolt of "wait, what is this?" That moment of mild confusion is where avoidable failures and disputes begin.
The best recovery message is the one you send before the failure.
Land before the bank does
A friendly heads-up roughly 26 hours out — just before the bank's mandatory 24-hour notice — reframes that confusion as a moment of trust. It names your brand, reminds the customer what they are paying for, and gives them time to make sure funds are available or authentication is ready. The customer goes into the bank's SMS already expecting it, instead of being startled by it.
Where the rails differ
How you trigger this depends on the gateway. Cashfree exposes a webhook that fires when it sends the customer the pre-debit notification, so you can land your message off that signal. Razorpay has no equivalent, so you schedule the heads-up yourself from the known billing date.
| Gateway | Pre-debit signal | What you do |
|---|---|---|
| Cashfree | Pre-debit notification webhook | Trigger the heads-up off the event |
| Razorpay | None | Schedule from the billing date yourself |
This is a Utility-category message — event-anchored, no upsell. The moment you add a discount or a cross-sell, it becomes Marketing, delivery drops, and the trust effect you were after is gone.
What the heads-up should and shouldn't say
Keep it spare: the brand, the plan, the amount, the date, and a simple way to act if something needs attention. No marketing flair. It earns its place most clearly on plans above ₹15,000, where fresh authentication is coming anyway and a calm, expected prompt is the difference between a clean debit and a failed one.
Where SubsShield fits
SubsShield turns the pre-debit moment into a scheduled, brand-first WhatsApp — so the debit succeeds and there is nothing to chase afterwards. It diagnoses and communicates; it does not move money.
So for your renewals above ₹15,000, who reaches the customer before the bank's SMS — you, or no one?
Priyanka Daga, Co-founder & Head of Product
Priyanka co-founded SubsShield and leads product. She designs the cancellation flows, WhatsApp templates, and channel choices that decide whether a paying customer in India comes back — or quietly disappears between a failed debit and a discount they never wanted.