How it works
A renewal fails for ordinary reasons: the card expired, the bank flagged a charge, the balance was short. Dunning is the response, and it has two parts.
- Retries. The billing system tries the charge again on a schedule.
- Contact. The customer is told and given a way to fix the card, for example a link to update it.
Stripe’s documentation says Smart Retries retries failed subscription and invoice payments, including subscriptions created with Payment Links. As of November 2026, new Stripe accounts have it on by default with up to 8 retries within 2 weeks. You can set the policy to a number of retries inside 1 week, 2 weeks, 3 weeks, 1 month or 2 months, or disable Smart Retries and define a custom schedule. Stripe does not retry when no payment method is available, when the issuer returns a hard decline code, or for India-issued cards.
Example: a license through a failed renewal
An illustrative subscription renews monthly on the 10th, and the 10th’s charge fails. This is how Clavem’s documented behavior plays out, with Stripe’s retries running in the background.
| Day | Stripe | License in Clavem |
|---|---|---|
| 10th | Charge fails, subscription becomes past_due, retries begin |
Stays valid: past_due keeps the license active during retries |
| 12th | Retry fails | Still valid |
| 14th | Customer updates the card in the portal, retry succeeds, invoice.paid |
Expiry moves to the end of the new paid period plus three days |
| If never fixed | Retries run out, status becomes unpaid or canceled |
License expires |
| Later, payment succeeds | invoice.paid |
License revived |
Only the statuses unpaid, canceled, incomplete_expired and paused expire a license. A license you disabled by hand stays disabled whatever Stripe says.
Dunning versus churn
Churn counts customers or revenue that leave. Dunning is one tool against the involuntary kind, where the customer did not choose to leave and the payment failed. A good dunning setup cuts involuntary churn, but it cannot stop a customer who wants to cancel.
How Clavem handles it
Clavem does not run retries or send dunning emails; Stripe does. Clavem follows the subscription status it receives through webhooks. A subscription license expires at the end of its paid period plus three days of grace, and invoice.paid revives an expired license at once, with no background job: expiry is evaluated whenever the license is read. The second kind of waiting, the 14-day offline window, is separate. Both are explained under grace period. Setup is in Connecting Stripe, and the seller side in failed subscription payments. A subscriber can fix a card through the Stripe customer portal.
Questions
Is dunning the same as a grace period?
No. Dunning is the seller's effort to collect the payment. A grace period is extra access the customer keeps while that happens. Clavem has a fixed three-day grace after a paid period, separate from Stripe's retry schedule.
Does Stripe retry failed subscription payments automatically?
Yes. As of November 2026, Stripe enables Smart Retries by default for new accounts, configured for up to 8 retries within 2 weeks. You can choose a different window or define your own schedule.