Dunning

Dunning is what happens after a recurring charge fails. Instead of cancelling the subscription on the first decline, a dunning system retries the payment on a schedule, notifies the customer with escalating urgency, and only writes the account off after the recovery attempts are exhausted. The name comes from an old English word for pressing debtors; the modern version is considerably more polite and considerably more automated.

A typical escalation runs in stages. A soft decline (insufficient funds, temporary issuer refusal) gets a quiet retry after a grace period. Repeated failures trigger customer-facing notices asking for an updated card. A final-notice stage warns of service interruption. Exhaustion ends in cancellation or write-off. Good systems make every knob configurable (retry counts, days between attempts, and independent auto-cancel guards based on days past due or consecutive failures), because recovery economics differ by vertical: a $9 media subscription and a $900 B2B seat justify very different persistence.

Dunning matters because involuntary churn (customers lost to payment failure rather than choice) commonly accounts for a large share of subscription churn, and much of it is recoverable. Reissued cards alone cause a significant fraction of card-on-file declines, which is why dunning pairs naturally with network account-updater services that refresh card numbers before a charge ever fails.

One design principle separates good implementations from bad: notification settings should gate the email, never the retry. Suppressing a failure notice must not silently suppress recovery itself.

QorCommerce Recurring ships a four-stage dunning engine with configurable retry schedules and dual auto-cancel guards as part of QorPay’s recurring billing module.