Overview
Failed payments are silent revenue killers. The average SaaS or subscription business loses 5-9% of MRR to failed payments — most of which are recoverable. Stripe's Smart Retries combined with an automated email sequence can recover the majority of these before they become churned customers. This guide walks through configuring Stripe's built-in dunning settings and layering in a Zapier-triggered email sequence for maximum recovery.
Before you start
- Stripe account with Billing/Subscriptions enabled
- Zapier account (Multi-Step plan)
- Gmail or email marketing tool connected to Zapier
- Stripe Customer Portal configured
Step-by-step guide (5 steps)
Configure Stripe Smart Retries
In Stripe Dashboard, go to Billing > Settings > Retry schedule. Enable Smart Retries — Stripe's ML-based system that retries at statistically optimal times. Set your retry window to 14 days with 3-4 attempts.
Smart Retries outperforms fixed schedules by 10-20% because it retries at times when cards are most likely to succeed (e.g., after a payday).
Set up the customer email notification in Stripe
Under Billing > Settings > Customer emails, enable 'Failed payment' notifications. Customize the email to include your business name, what failed, and a link to update their payment method via the Stripe Customer Portal.
Create a Zapier workflow for escalating follow-ups
In Zapier, create a Zap triggered by 'Stripe: Payment Failed.' Add a delay (Day 1, Day 3, Day 7) and send escalating emails via Gmail or your email tool. Day 1: friendly alert, Day 3: action required, Day 7: final notice before cancellation.
Enable the Stripe Customer Portal
In Stripe Dashboard, go to Settings > Billing > Customer portal. Enable it and add the portal link to all dunning emails. This lets customers self-serve their payment method update without contacting you.
The Customer Portal reduces support tickets about failed payments by 80% — customers can update cards themselves at any time.
Set up a cancellation webhook and Slack alert
In Zapier, create a second Zap triggered by 'Stripe: Customer Subscription Deleted.' Send a Slack notification to your team with the customer name and MRR lost. This lets you make a personal save attempt for high-value accounts.
What you'll get
Recovers 30-50% of failed payments automatically
Reduces involuntary churn without manual outreach
Customer Portal eliminates support tickets for payment updates
Slack alerts let you personally save high-value accounts
Common mistakes to avoid
Using a fixed retry schedule instead of Smart Retries
Not including the Customer Portal link in dunning emails
Setting the dunning window too short (under 14 days)
Sending too many emails too quickly — space them out to avoid spam flags
Frequently asked questions
Do I need coding experience to set up this Stripe automation?
No coding is required. This guide walks you through everything using Stripe's built-in features and Zapier's visual interface. If you can follow a recipe, you can follow this guide.
How long does this automation take to set up?
Most users complete this setup in 30–60 minutes on their first try. Once set up, it runs completely automatically with zero ongoing effort.
What happens if the automation fails?
Zapier and Make both have error notifications and task history, so you'll know immediately if something goes wrong. We cover troubleshooting steps in the guide above.
Can I customize this automation for my specific business?
Absolutely. The guide includes notes on common customizations. Most automations have multiple variation points — timing, conditions, notification recipients, and more.