Stripe handles your payments. Your email platform handles your communications. But most SaaS companies keep these systems in silos, missing opportunities to send relevant, timely emails based on billing events.

When a customer upgrades, you should thank them and help them use their new features. When a payment fails, you should alert them before their account gets suspended. When a subscription renews, you should reinforce the value they're getting. All of this requires connecting Stripe to your email marketing.

This guide walks through setting up that integration, the key events to trigger emails from, and the automations that drive real results.

Why Stripe Integration Matters

Payment events are some of the most important triggers for email. They represent real decisions and real money, which means users are paying attention.

When someone upgrades from free to paid, they've just demonstrated serious intent. An email at this moment has high open rates because the user is engaged and expecting confirmation. It's also a perfect opportunity to help them get value from what they just paid for. This is a critical moment in your SaaS lifecycle email strategy because the transition from trial to paid sets the tone for the entire customer relationship.

When a payment fails, time is critical. The sooner you notify the user, the sooner they can fix it. Waiting even a day means more failed retry attempts and higher involuntary churn. Failed payment recovery is one of the highest-ROI email automations any SaaS company can implement.

When a subscription is about to renew, especially on annual plans, users want to know before money leaves their account. A renewal reminder email prevents surprise charges, reduces chargebacks, and gives you a chance to reinforce value. For more on this, see our guide on subscription renewal reminder emails.

None of this works without connecting Stripe events to your email system.

Setting Up the Connection

There are two main approaches to connecting Stripe with your email marketing: using your email platform's native Stripe integration, or building a webhook-based integration.

Native Integration

Many email platforms now offer native Stripe integrations. You connect your Stripe account, and the platform automatically syncs customer data and payment events. This is the easiest path if your platform supports it. Check your email tool's integration marketplace.

Native integrations typically handle:

Syncing customer data (name, email, plan type, subscription status)
Mapping Stripe events to email triggers
Keeping subscriber attributes up to date as billing status changes
Providing pre-built automation templates for common billing emails

The advantage is speed. You can be up and running in minutes without writing any code. The disadvantage is limited customization. You're constrained to whatever events and data the integration supports, which might not cover every use case you need.

Webhook-Based Integration

If your platform doesn't have a native integration, or if you need more control, you'll build a webhook-based connection. Stripe sends webhooks when events happen (payment succeeded, subscription created, invoice upcoming, etc.). You set up an endpoint to receive these webhooks and trigger emails based on the event type.

For the webhook approach, you need to build a small server or use a service like Zapier to receive the webhooks and translate them into email triggers. The technical complexity depends on your stack, but the logic is straightforward: receive event, check event type, send appropriate email.

Here's the basic flow:

Configure Stripe webhooks. In the Stripe Dashboard, go to Developers > Webhooks and add your endpoint URL. Select the events you want to receive.
Build a webhook handler. Your endpoint receives POST requests from Stripe with event data. Parse the event, verify the signature, and determine what action to take.
Map events to email triggers. When you receive a customer.subscription.created event, trigger your welcome email. When you receive invoice.payment_failed, trigger your dunning sequence.
Sync subscriber data. Update your email platform's subscriber record with billing information: plan type, subscription status, MRR, next billing date.

Hybrid Approach

Many SaaS companies use a hybrid approach. They use their email platform's native integration for basic data syncing and common events, but also set up custom webhooks for specialized triggers or data the native integration doesn't handle. This gives you the convenience of a native integration with the flexibility of custom logic where you need it.

Essential Stripe Events for Email Triggers

Not every Stripe event needs an email. Focus on the events that represent meaningful moments in the customer relationship.

customer.subscription.created: A user started a paid subscription. Send a welcome email for new paying customers. Include help getting started with paid features and set expectations for billing. This is the beginning of your post-conversion onboarding sequence for paying customers.

customer.subscription.updated: The subscription changed. If it was an upgrade, send a thank you email with guidance on new features. If it was a downgrade, send an email acknowledging the change and asking for feedback. The difference matters. An upgrade is a moment of expansion and excitement. A downgrade is an early warning sign that needs careful handling.

customer.subscription.deleted: The subscription was cancelled. Send a confirmation of cancellation, include information about what happens to their account, and consider a win-back offer. Timing matters here. The cancellation confirmation should go out immediately. The win-back should wait 2-4 weeks to give the user space.

invoice.payment_succeeded: A payment went through. For first payments, this overlaps with subscription created. For recurring payments, this is your renewal confirmation. Don't over-communicate here. Monthly receipts become noise if they arrive as a separate email every month.

invoice.payment_failed: A payment didn't go through. This is critical. Send an email immediately alerting the user and explaining how to update their payment method. This is the start of your dunning sequence, which we'll cover in detail below.

invoice.upcoming: Stripe sends this before an invoice is generated (default is 3 days before, but you can configure this). Use it to send renewal reminders, especially for annual subscriptions where the amount is significant.

customer.source.expiring: The user's card is about to expire. Send a reminder to update their payment method before it causes a failed payment. This proactive email prevents a problem before it starts.

checkout.session.completed: If you use Stripe Checkout, this fires when a user completes the checkout flow. It's a reliable trigger for welcome and thank-you emails because it captures the exact moment of purchase.

Syncing Subscriber Data from Stripe

Beyond triggering emails from events, you should sync billing data to your email platform's subscriber records. This enables segmentation by plan type and billing status, which is essential for sending relevant communications.

Key data points to sync:

Plan type: Free, starter, pro, enterprise. This determines which upgrade paths and feature content to send.
Subscription status: Active, trialing, past_due, cancelled. This drives lifecycle segmentation.
MRR (Monthly Recurring Revenue): Knowing what each customer pays helps you prioritize communications and calculate email marketing ROI.
Next billing date: Enables accurate renewal reminder timing.
Payment method expiration: Enables proactive card expiration reminders.
Trial end date: Drives trial expiration email sequences.
Coupon or discount applied: Affects messaging about pricing and upgrades.
Customer lifetime: How long they've been paying. Long-tenured customers deserve different treatment than new converts.

Keep this data in sync. Stale billing data in your email platform leads to embarrassing mistakes like sending upgrade emails to your highest-tier customers or trial expiration warnings to paying users.

Automating Successful Payment Emails

When a payment succeeds, the email you send depends on context.

For first payments (new subscribers), send a welcome email that acknowledges the purchase and helps them get value. This isn't just a receipt. It's the beginning of your customer relationship. Include a clear next step, like setting up a key feature or booking an onboarding call. Reference the specific plan they chose and highlight what's now available to them.

Keep receipts separate. Stripe can send transactional receipts automatically, or you can send your own. Either way, the receipt and the welcome email should be different messages with different purposes. The receipt is a record. The welcome is engagement. If you're letting Stripe handle receipts, make sure your welcome email doesn't duplicate the receipt information. If you're handling receipts yourself, include the essential billing details but frame the email as a welcome, not a transaction confirmation.

For recurring payments (renewals), especially on annual plans, send a renewal confirmation that reinforces value. "Your subscription just renewed. Here's what you accomplished this year..." is more powerful than a bare confirmation of charges. Pull in usage data if you can: emails sent, features used, team members added, time saved. Make the renewal feel like a worthwhile investment, not just an expense.

For monthly renewals, you probably don't need an email every month. Monthly receipts become noise. Consider sending a quarterly summary instead, or only emailing when there's something meaningful to communicate alongside the renewal.

Building Failed Payment Recovery Sequences

Failed payments cause involuntary churn. The user didn't decide to leave. Their credit card just didn't work. This is recoverable revenue if you act quickly. The connection between failed payment recovery and reducing SaaS churn with email is direct: dunning emails are one of the highest-ROI tactics for preventing churn.

Stripe has built-in dunning (Smart Retries), but you should complement it with email communication. When invoice.payment_failed fires, start a recovery sequence.

Email 1: Immediate Notification (Day 0)

The first email goes out immediately. It should be helpful, not alarming. "There was an issue processing your payment" is better than "Your payment failed!" Explain what happened, what happens next (automatic retry), and how to update their payment method if needed.

Include a direct link to update payment. Don't make users figure out where to go. Deep link them to your billing settings or Stripe's customer portal. The fewer clicks between reading the email and fixing the problem, the higher your recovery rate.

Email 2: Follow-Up (Day 3)

If the first retry fails, send a follow-up email with more urgency. Reference that this is the second attempt. Emphasize the timeline before their account is affected. Include the same direct link to update payment, but also mention what they'll lose if the payment isn't resolved.

Email 3: Urgency (Day 5-7)

If you're approaching the final retry or account suspension, be clear about consequences. "Your account will be downgraded in 3 days if payment isn't resolved." This creates urgency without being manipulative. Be specific about what happens: which features they'll lose, whether their data is preserved, and how to restore their account.

Email 4: Final Notice (Day 10-12)

The last email before account action. This should be direct and clear. State exactly what will happen and when. Offer a final easy path to resolution. Some companies have the founder or CEO send this email personally, which can increase response rates.

Throughout the sequence, make it easy to get help. Some users have payment issues they don't know how to resolve. A support email or chat option can save customers who would otherwise churn. Consider including a phone number for high-value customers.

Measuring Dunning Performance

Track these metrics for your failed payment sequence:

Recovery rate: What percentage of failed payments are ultimately recovered? Industry benchmark is 20-50%.
Recovery by email: Which email in the sequence drives the most recoveries?
Time to recovery: How quickly do users fix their payment after the first notification?
Involuntary churn rate: What percentage of failed payments result in permanent churn despite your dunning sequence?

Renewal Reminder Emails

For annual subscriptions, send a reminder before renewal. This prevents surprise charges, reduces chargebacks and support requests, and gives you an opportunity to communicate value.

Send the reminder 7-14 days before renewal. This gives users time to review and take action if needed. For enterprise customers with large annual contracts, consider sending a reminder 30 days in advance.

The email should include the renewal date, the amount that will be charged, and a summary of value received. "Your subscription renews on March 15 for $480. This past year, you've sent 24,000 emails and created 15 automations."

Include clear instructions for what to do if they don't want to renew. This feels counterintuitive, but transparency builds trust. Users who want to cancel will cancel anyway. Making it easy reduces frustration. You might also want to consider an email preference center where users can manage their communication preferences as part of the renewal flow.

For monthly subscriptions, renewal reminders are usually unnecessary. Monthly charges are small enough that surprises are minor. But consider reminders for the first few months as users get used to recurring billing.

Annual Renewal Email Template Structure

A strong annual renewal reminder includes these sections:

Clear headline: "Your [Product] subscription renews on [date]"
Renewal details: Amount, date, payment method on file
Value summary: Key metrics from the past year showing ROI
What's coming: Brief preview of upcoming features or improvements
Action options: Link to manage subscription, update payment, or contact support
Help link: Direct path to billing support if they have questions

Upgrade and Expansion Emails

Stripe events can trigger emails that drive expansion revenue, not just retain existing revenue. When combined with product usage data, Stripe integration enables powerful upgrade prompt emails that arrive at exactly the right moment.

When a user approaches a plan limit (tracked in your application, not Stripe), send an upgrade prompt. "You've used 90% of your email sends this month. Upgrade to send more." Time this email to arrive before they actually hit the limit. The Stripe integration handles the billing side: you know exactly what plan they're on, what they're paying, and what the next tier costs.

When a user's usage increases significantly, that's a signal of engagement and a potential upgrade opportunity. "You've doubled your email sends this month. If you're growing, our Pro plan might be a better fit." Connect usage events from your product with billing data from Stripe to make these emails specific and actionable.

When a user has been on the same plan for a long time without upgrading, consider a gentle check-in. "You've been on the Starter plan for 6 months. Here's what you could do with Pro." Don't be pushy, but make sure users know about higher tiers.

For annual upsell, target monthly subscribers who've been paying consistently for 3+ months. "You've been with us for 4 months. Switch to annual billing and save 20%." This is a win-win: the customer saves money, and you get a longer commitment and improved cash flow.

Handling Downgrades and Cancellations

Downgrades and cancellations are just as important to handle well as upgrades. These moments reveal what's not working and give you a chance to learn and potentially recover.

Downgrade Emails

When customer.subscription.updated fires with a plan change to a lower tier:

Acknowledge the change without judgment. Confirm what their new plan includes.
Ask for feedback. A single question, "What made you decide to switch?" with a few multiple-choice options, gives you data without requiring effort.
Explain what changes. If they'll lose access to features, be clear about the timeline and what happens to their data.
Leave the door open. Mention that they can upgrade again anytime. Don't make it a pitch, just a reminder.

Cancellation Emails

When customer.subscription.deleted fires:

Confirm the cancellation immediately. Include the date their access ends and what happens to their data.
Request feedback through a brief cancellation feedback email. This is your most valuable source of churn data.
Offer alternatives if appropriate. A pause option, a discount, or a lower tier might retain users who are leaving for cost reasons.
Plan a win-back sequence. Wait 2-4 weeks, then begin a win-back email campaign highlighting what's improved since they left.

Technical Implementation Tips

When building Stripe webhook handling, verify the webhook signature. Stripe signs webhooks, and you should verify them to ensure the events are legitimate. This prevents spoofed events from triggering emails.

Handle webhooks idempotently. Stripe can send the same webhook multiple times. Your handler should check if you've already processed an event before triggering an email. Nobody wants duplicate "your payment failed" emails. Use the event ID as a deduplication key.

Process webhooks asynchronously. Return a 200 response to Stripe immediately, then process the event in a background job. This ensures you don't miss webhooks due to processing delays. Stripe considers a webhook failed if it doesn't get a 2xx response within 20 seconds.

Log everything. Webhook debugging is hard without good logs. Log the event type, customer ID, and any actions taken. When something goes wrong, you'll be glad you did.

Test with Stripe's test mode. Send test events through your webhook endpoint before going live. Stripe's CLI can send test webhooks, making this easy:

stripe listen --forward-to localhost:3000/api/webhooks/stripe
stripe trigger invoice.payment_failed

Handle event ordering carefully. Stripe doesn't guarantee webhook delivery order. You might receive invoice.payment_succeeded before customer.subscription.created even though the subscription was created first. Your handler should be resilient to out-of-order events.

Set up webhook monitoring. Use Stripe's webhook logs to check for failed deliveries. Set up alerts for webhook failures so you can investigate promptly. A broken webhook endpoint means missed emails and potentially missed revenue.

Measuring Impact

Track these metrics for your Stripe-triggered emails:

For failed payment sequences, track recovery rate. What percentage of users with failed payments successfully resolve them? Good dunning sequences recover 20-50% of failed payments. Multiply your recovery rate by average customer lifetime value to calculate the revenue your dunning emails save.

For upgrade prompts, track upgrade rate. What percentage of users who receive upgrade emails actually upgrade? Even small conversion rates add up at scale. Track the revenue impact by measuring MRR expansion attributed to email-driven upgrades.

For renewal reminders, track churn rate around renewal. Do users who receive renewal reminders churn less than users who don't? Are there fewer chargebacks? Also track whether renewal reminders lead to support inquiries, which might indicate pricing or value concerns.

For all Stripe-triggered emails, watch for spam complaints. Billing emails should have near-zero complaint rates. If users are marking your payment emails as spam, something is wrong with tone, frequency, or relevance.

Use email marketing KPIs to benchmark your Stripe-triggered email performance against your other email programs. Billing emails should outperform marketing emails on open and click rates because they contain information users genuinely care about.

Putting It Together

A complete Stripe email integration includes:

New subscriber welcome emails (customer.subscription.created)
Upgrade acknowledgment emails (customer.subscription.updated - upgrade)
Downgrade handling emails (customer.subscription.updated - downgrade)
Failed payment recovery sequence (invoice.payment_failed)
Renewal reminders for annual plans (invoice.upcoming)
Card expiration reminders (customer.source.expiring)
Cancellation confirmation and win-back (customer.subscription.deleted)
Expansion and upsell emails (usage events + billing data)

Start with failed payment emails because they have the most immediate ROI. Recovering even a small percentage of failed payments adds real revenue. Then add welcome and renewal emails to improve the customer experience. Finally, layer in upgrade prompts to drive expansion.

The connection between Stripe and email marketing isn't just a nice-to-have. It's how you prevent involuntary churn, maximize customer lifetime value, and communicate at the moments that matter most.

Frequently Asked Questions

How quickly should billing emails be sent after a Stripe event?

Immediately for failed payments and cancellations. These are time-sensitive and users expect quick communication. For payment confirmations and renewals, within a few minutes is fine. For upgrade acknowledgments, aim for within 30 minutes so the user gets help with new features while they're still engaged.

Should I use Stripe's built-in email receipts or send my own?

For simple receipts, Stripe's built-in emails work fine and require zero development. For anything beyond a basic receipt, like including usage data, product recommendations, or personalized content, send your own. Many companies use Stripe for the transactional receipt and their email platform for the relationship-building email.

How do I prevent duplicate emails from Stripe webhooks?

Use the Stripe event ID as a deduplication key. Before processing any webhook, check whether you've already handled that event ID. Store processed event IDs in a database or cache with a TTL of at least 24 hours. Also implement idempotent email sending so that even if your handler runs twice, the email only sends once.

What's the best dunning email sequence length?

Three to four emails over 10-14 days works well for most SaaS companies. More than four emails rarely recovers additional customers and starts to feel aggressive. Space them 3-4 days apart, increasing urgency with each email. Match your email timing to Stripe's retry schedule so emails reference upcoming retries accurately.

How do I handle plan changes mid-billing cycle?

Send a confirmation email that explains the prorated billing. Users are often confused about prorated charges, so be clear about what they'll be charged, when, and why. If the plan change is an upgrade, focus the email on the new features they just unlocked rather than the billing details.

Should I send different emails for monthly vs annual subscribers?

Yes. Annual subscribers have a higher commitment level and typically generate more revenue. Their renewal reminders should arrive earlier (14-30 days before), include a year-in-review value summary, and receive more personal attention. Monthly subscriber communications can be lighter since the individual transaction amounts are smaller.

How do I test Stripe email integrations without affecting real customers?

Use Stripe's test mode with test API keys. Create test customers, trigger test events, and verify that emails send correctly. Use Stripe's CLI to trigger specific webhook events locally. Always test the full flow: webhook received, subscriber data updated, email triggered, email content rendered correctly.

What happens if my webhook endpoint goes down?

Stripe retries failed webhooks up to 16 times over approximately 72 hours, with exponential backoff. Monitor your webhook endpoint uptime and set up alerts for failures. If you experience extended downtime, check Stripe's webhook logs for missed events and replay them manually. Consider building a dead letter queue for events that fail processing.