Involuntary Churn Strategy
Soft decline vs hard decline: the call that sets your message
Two failures land in the same dashboard column minutes apart. One needs nothing from the customer for days; the other needs them today. Treat them the same and you'll be wrong twice.
Two failed payments land in the same dashboard column, five minutes apart. One of them needs nothing from the customer for a few days. The other needs them to act today. Treat the two the same way — and you will be wrong twice, in opposite directions.
The single most useful thing a recovery system does first is tell them apart.
The only triage that comes first
A soft decline means the bank could say yes later — insufficient funds, a temporary issue. A hard decline means it cannot say yes until something changes — a dead card, an expired or revoked mandate. Everything downstream — tone, timing, channel — follows from which of these you are looking at.
A soft decline is a "not yet". A hard decline is a "not unless you do something". The message differs because the truth does.
What each looks like on Indian rails
| Signal | Soft or hard | Right response |
|---|---|---|
| UPI / card — insufficient funds | Soft | Let the gateway retry; nudge near payday |
| Card expired or invalid | Hard | Card-update request now |
| Mandate expired / rejected | Hard | Re-authorisation link now |
| UPI "rejected by payer" | Voluntary (soft touch) | One gentle message; lower urgency |
| Failed inside a peak window | Neither — it's a queue | Wait; confirm before messaging |
The timing move on soft declines
Soft declines reward patience and good timing. Indian salaried customers are mostly paid on the 1st or the last working day of the month, so a soft decline on the 27th is a very different situation from one on the 6th. Let the gateway's retry run, and time the human nudge for when money is more likely to be in the account.
An escalating, urgent tone on a soft decline is a quiet way to lose a happy customer. They did nothing wrong; their balance dipped for a day. The message should read like a small heads-up, not a final notice.
The urgency move on hard declines
Hard declines are the opposite. No retry fixes a dead card or a broken mandate — the only thing that helps is a clear action from the customer, sent immediately on the channel most likely to be seen: update the card, re-authorise the mandate. Waiting on a retry that can never succeed just burns the recovery window while the subscription drifts toward halted.
Where SubsShield fits
The first thing SubsShield decides about any failure is soft versus hard — then the finer category — and that single call sets the tone, the timing, and the channel of everything that follows. It diagnoses and communicates; it does not move money.
So of last month's failures, how many soft declines got an urgent hard-decline message — and how many hard declines were left waiting on a retry that could never work?
Meghna Iyer, Recovery Operations Lead
Meghna leads recovery operations at SubsShield. She writes the ops-level pieces — turning raw gateway webhooks into classified failure states, separating soft declines from hard ones, and building the playbook a founder runs across their first 50 failed payments.