"Dunning" is a slightly old-fashioned word for a very modern problem. In subscription commerce it refers specifically to the process of recovering a payment that failed at billing time - through automatic retries, customer messages, and card-updater services. Done well, the dunning process recovers 60-75% of failed payments; done poorly, it loses most of them.
The standard dunning process step by step
- Day 0: charge fails. The subscription platform attempts to charge the card and the issuer declines. A reason code comes back (expired, insufficient funds, fraud, etc.) - this drives what happens next.
- Day 0-1: first retry and first email. Some processors immediately retry; most wait. A friendly notification email goes to the customer explaining what happened and asking them to update.
- Day 3-5: second retry. Smart retry logic picks the optimal day based on the decline reason - wait longer for issuer blocks, retry faster for insufficient-funds at month-end.
- Day 4-7: reminder email. "We tried again - please update your card." Tone slightly more urgent.
- Day 7-10: final retry plus final notice. "Last try before we pause your subscription." This message converts the most.
- Day 10-14: pause or cancel. Best practice: pause rather than cancel outright. Many customers reactivate within 30 days.
What runs in the background
Two services work silently in parallel with the visible dunning sequence: card-updater programs (Visa Account Updater, Mastercard ABU) that refresh expired or replaced cards automatically, and fraud-recovery logic that retries blocked charges after a delay so they look less suspicious to the issuer. These recover meaningful chunks of revenue without the customer ever receiving an email.
Operational signs your dunning process is healthy
- Recovery rate of failed payments above 60%.
- Card-updater services enabled (often 10-20% silent recovery).
- Three to four dunning messages over 7-14 days, not one or seven.
- Pause-before-cancel default, not immediate termination.
- A dashboard showing failed payments, recovery by reason, and revenue saved.
See dunning management, payment retries, and dunning messages.