DEV Community

Swipe Again for Swipe Again

Posted on

Day 1, Day 3, Day 7: Why a Dunning Cadence Exists at All

A failed payment starts two clocks. One belongs to the retry engine: when is this card most likely to work again? The other belongs to the customer, who usually does not know anything went wrong. The dunning cadence — for Swipe Again, emails on day 1, day 3, and day 7 alongside the retry schedule — exists to serve the second clock without abusing it.

Day 1 is information, not pressure. Most customers, told plainly that a payment failed and given a working card-update link, fix it themselves within hours. Every self-serve fix is a recovery no retry had to earn, and it arrives with the customer's own consent refreshed. That is why the first message goes out while the first retries are still young.

Day 3 is for the people day 1 missed — the email went to spam, the week was loud, the card is in a drawer. The message changes slightly: same clarity, a little more consequence. Day 7 is the honest deadline: the last structured ask before the subscription's fate is decided, timed so a customer who wants to stay has a real chance to act, and a customer who has left gets a clean ending instead of a month of noise.

What the cadence refuses to do matters as much. No daily emails. No artificial panic. No pretending a banking problem is a character flaw. The recovery flow treats dunning as customer communication that happens to be about money — because the businesses that keep subscribers longest are the ones whose worst-day messages still sound like their best-day product.

Top comments (0)