Visible assumptions
The public benchmark exposes the illustrative failed-payment bands and 62% illustrative modeled recovery assumption used in its model. Updated July 2026.
Public report
State of Stripe Failed Payments 2026
A living report for SaaS founders tracking failed payments, decline codes, and recovery opportunities across Stripe.
Public benchmark
Failed-payment ranges by MRR.
These ranges are the public model used by Dunlo's benchmark and audit pages. They are useful for estimation, not a substitute for connecting Stripe and reading your actual invoices.
< $5k MRR
Stripe defaults can hide the problem because volume is still low.
4.2%
$5k-$20k MRR
The first range where a dedicated recovery workflow usually pays back.
5.1%
$20k-$80k MRR
Failed payments become a visible retention problem, not just billing noise.
5.8%
$80k+ MRR
Recovery needs prioritization, account value, and human escalation.
6.4%
Failure-code playbook
The useful report is code-level, not just rate-level.
insufficient_funds
Retry timing matters, but the customer email should stay calm.
expired_card
Stop retrying blindly and send a direct card-update path.
authentication_required
Explain the bank authentication step before another charge attempt.
do_not_honor
Escalate carefully when account value justifies a personal touch.
Report scope
What this asset covers.
01
Public benchmark model by MRR range
02
Failure-code recovery playbook
03
Beta data publication rules
04
Approved screenshots and testimonials when available
Beta transparency
What can be verified today.
Dunlo publishes assumptions, recovery mechanics, and its proof policy before it publishes customer outcomes.
During beta, customer outcomes are published only with approval and enough context to be useful.
Inspect the public model
Visible mechanics
Failure reasons, recovery timing, customer update links, and founder review are documented before signup.
Visible proof policy
Customer metrics and stories remain private until the sample is useful and the customer approves publication.