Day 0
send now
First recovery email
Explain that you will retry later and keep an optional update link available.
Free Stripe dunning tool
Build a practical failed-payment sequence from the Stripe failure reason, invoice value, account type, and recovery window.
Build your schedule
Choose the account type, invoice amount, failure reason, and recovery window. The calculator turns that into a practical sequence for customer emails, retries, escalation, and final notice.
Recommended sequence
$129 failed invoice - Worth a careful sequence
Day 0
send now
Explain that you will retry later and keep an optional update link available.
Day 3
retry window
Wait 2-3 days before the next attempt so payroll, card limits, or balances can change.
Day 5
manual review
Send a short personal note before the account becomes silent churn.
Day 14
final step
Escalate softly before the final retry if the account is valuable.
Retry
Secure link
How to use it
Use the output as a starting point for your Stripe dunning sequence, then adapt the language to your customers and support policy.
A Stripe dunning schedule is the sequence of customer emails, payment retries, payment update prompts, escalation steps, and final notices after a subscription payment fails.
Many SaaS teams use a 7 to 21 day dunning window. Low-price self-serve products can keep the sequence short, while higher-value accounts often deserve more time and a human escalation step.
No. An expired card needs a fast update-card email, insufficient funds often benefits from a delayed retry, and authentication_required needs a direct customer action link.
Dunlo automates the customer-facing payment recovery workflow around Stripe, including failure-specific emails, secure update links, founder review, and recovered revenue tracking.