card_expired
high intent
The customer is still willing to pay
Send a direct update-card path before a simple expiry becomes cancellation noise.
Stripe failed payment recovery
Failure-code emailsSmarter Stripe retry timing
Recover failed payments before they turn into quiet churn.
Dunlo turns raw Stripe decline events into a recovery workflow: the right customer email, the right retry moment, and founder escalation when an account is worth saving personally.
Failure-code logic
The reason changes the recovery play.
Generic payment failed emails flatten every problem into the same message. Dunlo keeps the response tied to the Stripe failure code.
insufficient_funds
timing
Timing matters more than pressure
Wait, explain the issue, and retry when the payment has a better chance to clear.
do_not_honor
context
Vague bank blocks need context
Tell the customer what the bank blocked and what to do before another retry burns trust.
Blind retries are not a recovery strategy.
If the card expired or the bank blocked the charge, another retry without context can train customers to ignore the problem.
Recovery operating system
From event to paid invoice.
Dunlo gives failed payments a clear owner, a customer-safe message, and a visible recovery state.
Failure-code emails
Messaging changes with the decline reason.
Payment retry timing
Retries are paced around failure type and customer action.
Revenue tracking
Recovered MRR is visible without spreadsheet work.
Stripe failed payments FAQ
What is a Stripe failed payment?
A Stripe failed payment is a charge, invoice, or payment intent that Stripe could not complete because the card, bank, customer, or authentication step blocked the transaction.
Can failed Stripe payments be recovered?
Yes. Many failed Stripe payments are recoverable when the customer is contacted quickly, the retry is timed around the failure reason, and the email explains the exact action needed.
How is Dunlo different from basic retry logic?
Dunlo combines failure-code-specific recovery emails, smart timing, founder escalation, and recovered revenue tracking so SaaS teams can act on the reason each payment failed.
Is payment retry enough to recover failed payments?
Payment retry helps when the failure is temporary, such as insufficient funds or a network issue. It is weaker when the customer needs to update a card, complete authentication, or understand why their bank blocked the charge.
Guide
Failed payment email templates
Copy email examples for expired cards, insufficient funds, bank declines, and authentication-required payments.
Read guideGuide
Stripe recovery software
See the full software layer for failed-payment emails, retries, escalation, and reporting.
Read guideGuide
Stripe Smart Retries
See which failures benefit from retry timing and which need customer action.
Read guideGuide
Involuntary churn
Measure when a failed payment becomes churn and how much MRR remains recoverable.
Read guideGuide
Stripe dunning workflow
Build the email cadence, retry windows, and escalation path around each failed invoice.
Read guideGuide
Stripe decline codes
Decode the card failure reason before choosing the email, retry timing, or escalation path.
Read guideGuide
card_velocity_exceeded
Handle issuer-limit declines with safer timing and a clear customer action.
Read guideGuide
Dunning schedule calculator
Plan the first email, retry window, escalation, and final notice from the failure reason.
Read guideFree during beta
Find the failed payments Stripe is not recovering.
Connect Stripe, import existing failures, and start recovering revenue with customer-safe emails in minutes.