Automated Stripe dunning emails, done for you

A single retry email isn't a dunning strategy

Most subscription tools trigger one generic "your card was declined" email and stop there. That treats every failure the same, whether the customer's bank had a temporary hiccup or their card actually expired six months ago — and a generic email sent at the wrong moment gets ignored as often as it gets acted on.

Smart dunning notifications work differently: the message, timing, and retry schedule all depend on why the charge failed. A soft decline gets retried quietly, often recovering the payment before the customer ever sees an email. A hard decline skips retries entirely and goes straight to a card-update request, because retrying a card that's expired just wastes an attempt and delays the fix. That distinction is what separates a dunning email sequence that recovers revenue from one that trains customers to ignore your emails.

Retry, then email — decline-code aware

1. We classify the decline code — codes like insufficient_funds or try_again_later are worth retrying; codes like expired_card or stolen_card go straight to card-update messaging instead of wasting a retry.
2. We retry on a smart schedule — soft declines get retried soon; ambiguous ones get a longer, more cautious window.
3. We email the customer — a dunning email with a secure card-update link, so they can resolve it without you lifting a finger.
4. You can send a manual reminder — for cases that stall, you can send an editable follow-up email straight from the case page.

Common questions

Reduce involuntary churn · Chargeback evidence · Stripe integration · Dunning email best practices guide