Dunning

Dunning is the structured process of following up on a failed or overdue payment — a sequence of retries and reminder messages designed to recover revenue from a declined charge without souring the relationship with the customer who owns it.

It matters because a failed payment isn't usually a lost customer — most declines are recoverable if handled with the right timing and tone. A blind, one-size-fits-all retry schedule wastes attempts on cards that will never clear, like an expired one, and annoys customers whose failure was temporary, turning a fixable billing hiccup into a support ticket or a churn event.

In practice, effective dunning starts with the decline reason, not a fixed calendar. Insufficient funds recovers best with a short delay and a retry timed near a plausible payday; an expired or stolen card will never recover on retry and needs an immediate 'update your payment method' message instead. Each attempt is logged, and the customer's access and messaging adjust based on how many attempts have failed and why.

The common pitfall is treating dunning purely as a technical retry loop instead of a customer-facing moment. A generic 'payment failed' email that doesn't say why, arriving on a fixed schedule regardless of the reason, both under-recovers revenue and creates unnecessary support load — the fix is matching message and timing to the specific decline reason, not adding more retries.