Blog
Stripe Smart Retries and dunning: what to validate for subscription payments
Stripe Smart Retries can be a strong recovery tool, but enabling it is not the same as operating an observable recovery process. A subscription business still needs to know what failed, what was scheduled to happen next, what the customer saw, and whether the payment later recovered.
Start with the configuration questions
- Is Smart Retries enabled, or is a custom retry schedule in use?
- What is the retry window and maximum attempt count for each relevant collection flow?
- Can the team see the next scheduled payment attempt and the final outcome?
- Are failed-payment messages enabled and connected to a secure payment-update path?
- Does an updated payment method become the method the subscription uses at the next collection attempt?
Do not optimize the setting in isolation
A retry schedule cannot be evaluated only by its configuration screen. Measure the first-attempt failure value, later recovery value, current exposure, customer-action cases, and hard-decline cases across a defined time period. Then test a change against that baseline rather than treating a vendor default as a finished strategy.
Keep hard-decline communication neutral
Stripe’s guidance distinguishes decline situations that should not receive an ordinary retry. In customer-facing communication, the safer operational pattern is to request a valid payment method without exposing a sensitive lost- or stolen-card reason. Stripe failed-payment recovery guidance
FAQ
Are Smart Retries better than a custom Stripe retry schedule?
It depends on the business, payment mix, and observed outcomes. The first step is to make the current choice and its results visible, then decide what to test.
What should be measured after a dunning or retry change?
Track first-attempt failure, later recovered value, current exposure, recovery timing, and the distribution of customer-action and hard-decline paths over the same defined population.
Ready to put this to work?
Use a defined analysis window to evaluate your current Stripe retry, dunning, and payment-update journey before changing it.