Audits · Checklist
Dunning & Recovery Audit
Check whether your failed-payment recovery system is actually recovering the revenue it could be.
About this audit
When a payment fails, what happens in the next 30 days determines whether that revenue is recovered or permanently lost. A well-configured dunning system typically recovers 50-70% of failed payments; a poorly configured one recovers far less, quietly bleeding revenue that was never really at risk of churning voluntarily.
This audit checks retry configuration, customer communication, and — critically — whether recovery rate is actually being measured at all.
Frequently Asked Questions
What's a healthy dunning recovery rate?
50-70% is a commonly cited healthy range for failed payments eventually recovered through retries and communication. Below 40% usually indicates the retry sequence or messaging needs work.
Why does a magic link matter in the payment-update email?
Requiring a customer to log in to update their card adds friction at exactly the moment they're most likely to abandon the process. A direct, no-login link to the update-payment form removes that friction.
Fix what this audit finds
Turn your results into an action plan with the Dunning / Failed Payments Playbook Builder.
Dunning / Failed Payments Playbook Builder →Want this checked automatically, every month?
Connect Stripe in read-only mode and Dnoise flags these issues automatically — no manual audit required.
Connect Stripe — free →