Automate Stripe Failed Payment Recovery with Make.com and Resend (Save 15% Churn)

The True Cost of Involuntary Churn

Consider a SaaS company generating \$100,000 in Monthly Recurring Revenue (MRR):

• Average monthly churn is 5% (\$5,000 MRR lost per month).
• Approximately 35% of that churn (\$1,750/mo) is purely involuntary payment failure.
• Over a 12-month period, compounded involuntary churn strips more than \$21,000 in recurring revenue straight off the top line.
• Recovering even half of those subscribers (\$10,500/yr) drops directly into bottom-line EBITDA with zero customer acquisition cost (CAC).

Before configuring the webhooks, review our directory of Best Workflow Automation Software and evaluate transaction infrastructure in our comparison of Stripe vs Lemon Squeezy and email engines in Resend vs SendGrid.

The 4-Stage Dunning Lifecycle Architecture

A high-converting dunning workflow must balance urgency, deliverability, and user convenience. Here is the operational architecture:

Stage	Trigger Event	Action Taken	Email Tone & Urgency
Stage 1: Hour 0	invoice.payment_failed	Generate Customer Portal session & send instant notice	Gentle heads-up: “Action required on your billing info”
Stage 2: Day 3	Scheduled Data Store check	Verify if invoice remains unpaid; dispatch follow-up	Firm advisory: “Subscription will pause in 4 days”
Stage 3: Day 7	Scheduled Data Store check	Final warning email + Slack alert to account manager	Critical alert: “Account access suspended in 24 hours”
Stage 4: Recovery	invoice.payment_succeeded	Cancel pending dunning sequence & send thank you	Reassurance: “Payment confirmed, thank you!”

Step 1: Setting Up the Stripe Webhook in Make.com

The pipeline begins the instant Stripe encounters a failed charge:

1. Create a new scenario in Make.com and add the Stripe: Watch Events (Custom Webhook) trigger module.
2. Copy the generated webhook URL.
3. In your Stripe Dashboard, go to Developers → Webhooks → Add endpoint.
4. Paste the URL and select the following three events:
   • invoice.payment_failed (Triggered when recurring subscription charge fails)
   • invoice.payment_succeeded (Triggered when customer successfully updates their card)
   • customer.subscription.deleted (Triggered if subscription is permanently canceled)
5. Save the endpoint and copy the Signing Secret into Make.com to verify cryptographic signatures.

Step 2: Generating One-Click Stripe Customer Portal Sessions

The greatest friction in payment recovery is forcing customers to remember passwords, log into an app, navigate to account settings, and find the billing page. Every extra step decreases recovery rates by 25%.

With Stripe’s Billing Customer Portal API, you can generate an authenticated, direct-access URL that requires zero login credentials:

1. In Make.com, add an HTTP: Make a request module (or native Stripe module).
2. Configure the call:
   • Method: POST
   • URL: https://api.stripe.com/v1/billing_portal/sessions
   • Headers: Authorization: Bearer sk_live_... and Content-Type: application/x-www-form-urlencoded
   • Body: customer={{1.data.object.customer}}&return_url=https://yourdomain.com/dashboard
3. Stripe returns a JSON response containing url (e.g., https://billing.stripe.com/p/session/live_...). This link is valid for 24 hours and takes the customer directly into Stripe’s hosted card update form.

Step 3: Sending High-Deliverability Dunning Emails with Resend

Traditional email marketing platforms often route transactional billing warnings into Gmail’s “Promotions” or “Spam” tabs because they are bundled with marketing campaign IPs. Resend provides developer-grade dedicated IPs, modern React email support, and sub-second dispatch speeds.

Add an HTTP module to call the Resend API:

• URL: https://api.resend.com/emails
• Method: POST
• Headers: Authorization: Bearer re_123456... and Content-Type: application/json

The High-Converting Plain-Text Email Template

Studies consistently show that plain-text styled personal emails from the founder or Head of Customer Success convert 38% better than over-designed HTML templates with big warning graphics:

{
  "from": "Sarah from Acme <billing@acme.com>",
  "to": ["{{1.data.object.customer_email}}"],
  "subject": "Quick heads up regarding your Acme subscription",
  "html": "<p>Hi {{1.data.object.customer_name || 'there'}},</p><p>We attempted to process your latest subscription renewal for Acme Pro (\$49/mo), but your card issuer declined the transaction (Reason: {{1.data.object.last_payment_error.message || 'Payment method failed'}}).</p><p>No worries at all—these things happen when cards expire or banks update fraud filters. Your account remains active right now, but Stripe will retry the charge in 72 hours.</p><p>To ensure uninterrupted service for you and your team, you can update your payment method in one click here:</p><p style='margin: 24px 0;'><a href='{{2.data.url}}' style='background: #6366F1; color: #ffffff; padding: 12px 24px; border-radius: 6px; text-decoration: none; font-weight: bold;'>Update Payment Details &rarr;</a></p><p>Thanks,<br/>Sarah Jenkins<br/>Head of Customer Success, Acme</p>"
}

Alternative: React Email & Tailwind Component for Resend

If your product design requires on-brand typography, modern container cards, and retina logo headers while retaining 99%+ deliverability, you can render a pre-compiled React Email template using Resend’s native SDK or inline HTML:

// React Email Dunning Notification Component
import { Html, Head, Body, Container, Section, Text, Button, Hr, Link } from "@react-email/components";

export default function DunningEmail({ customerName, amountDue, portalUrl, brandName }) {
  return (
    <Html>
      <Head />
      <Body style={{ backgroundColor: "#f8fafc", fontFamily: "sans-serif", padding: "20px 0" }}>
        <Container style={{ backgroundColor: "#ffffff", border: "1px solid #e2e8f0", borderRadius: "8px", padding: "32px", maxWidth: "560px" }}>
          <Text style={{ fontSize: "20px", fontWeight: "bold", color: "#0f172a", marginBottom: "16px" }}>
            Action Required: Payment Update for {{brandName}}
          </Text>
          <Text style={{ fontSize: "15px", color: "#475569", lineHeight: "1.6" }}>
            Hi {{customerName}}, your latest recurring subscription of {{amountDue}} was declined by your bank. Your team features remain unlocked for the next 72 hours.
          </Text>
          <Section style={{ textAlign: "center", margin: "28px 0" }}>
            <Button href={{portalUrl}} style={{ backgroundColor: "#4f46e5", color: "#ffffff", padding: "12px 24px", borderRadius: "6px", fontWeight: "bold", textDecoration: "none" }}>
              Update Card Securely →
            </Button>
          </Section>
          <Hr style={{ borderColor: "#e2e8f0", margin: "24px 0" }} />
          <Text style={{ fontSize: "12px", color: "#94a3b8", textAlign: "center" }}>
            Protected by Stripe 256-bit encryption. You will not be asked to log in.
          </Text>
        </Container>
      </Body>
    </Html>
  );
}

Step 4: Behavioral Tracking with Make.com Data Stores

To manage the multi-day sequence (Day 0 → Day 3 → Day 7), store each failed invoice state in a Make.com Data Store called Dunning_Ledger:

• Key: {1.data.object.invoice_id}
• Customer ID: {1.data.object.customer}
• Failed Timestamp: {now}
• Stage: 1_sent
• Status: unresolved

When invoice.payment_succeeded arrives, update Status to resolved. A secondary scenario running daily queries records with Status = unresolved and dispatches Stage 2 and Stage 3 reminders according to their elapsed timestamp.

Step 5: VIP High-Value Account Alerts on Slack

If a customer paying \$500+/month fails payment, you should never rely solely on automated emails. Insert a Router in Make.com:

• Filter: {1.data.object.amount_due} >= 50000 (in cents).
• Action: Send immediate high-priority alert to #sales-churn-alerts on Slack:
  “🚨 High-Value Account Failed Payment: Acme Corp (\$1,200/mo). Failed reason: Do Not Honor. Assigned Rep: @Alex — please reach out personally.”

Financial Comparison: Make.com + Resend vs Proprietary Dunning SaaS

Solution	Monthly Fixed Fee	Commission on Recovered ARR	Annual Cost ($5k Recovered/mo)
Make.com + Resend (Self-Built)	$9.00 / month	0.0% (Zero commission)	$108.00 / year
Baremetrics Recover	$69.00 / month	Tiered based on MRR	$828.00 / year
Churnkey / ProfitWell Retain	$250.00 / month	5% to 8% of recovered ARR	$3,000.00 to $4,800.00 / year

Decoding Stripe Decline Codes: Tailoring the Recovery Message

Not all payment declines are created equal. Blasting the same generic email for an expired debit card versus a suspected fraud flag confuses customers and lowers recovery rates.

Stripe provides a specific decline_code inside the invoice.payment_failed payload under data.object.last_payment_error.decline_code. Map your messaging to these 5 distinct decline archetypes:

Decline Code	Bank Root Cause	Optimal Email Subject	Customer Call-to-Action
insufficient_funds	Temporary account balance deficit	Payment retry scheduled for your Acme subscription	Allow auto-retry or switch to a secondary backup payment card
expired_card	Card passed MM/YY expiration date	Your card on file for Acme has expired	Update expiration date or replace with replacement card
do_not_honor	Bank automated fraud risk hold	Quick verification needed with your bank for Acme	Contact card issuer to approve recurring charge or use alternative card
card_velocity_exceeded	Daily or monthly credit limit hit	Temporary limit reached on your payment card	Authorize credit limit increase or enter corporate charge card
lost_card / stolen_card	Card reported stolen or cancelled	Action required: please provide an active payment card	Immediate card replacement required (disable automatic retries)

Step 6: SMS Dunning Escalation via Twilio for Mobile-First Audiences

For consumer SaaS, B2C subscriptions, and mobile apps, email open rates hover near 20%, but SMS open rates exceed 98% within 3 minutes.

When an invoice remains unpaid after 72 hours (Stage 2), you can trigger an automated SMS notification using the Twilio module in Make.com:

1. Query customer phone number from Stripe: {1.data.object.customer_phone}.
2. Validate that the customer has a valid E.164 phone number.
3. Add the Twilio: Send a Message module:
   • From: Your registered A2P 10DLC Twilio phone number.
   • To: {1.data.object.customer_phone}
   • Body: “Hi Alex, your Acme Pro renewal could not be processed. To keep your team’s access active, update your card in one tap: {2.data.short_url}”

SMS follow-ups capture users on the go who ignore desktop billing emails, driving a 30% boost in Day 3 recovery rates.

Step 7: The Daily Cron Scenario Architecture (Day 3 & Day 7 Follow-ups)

To ensure the multi-day sequence executes reliably without manual oversight:

1. Create a secondary Make.com scenario scheduled to run Every day at 09:00 UTC.
2. Module 1 (Data Store – Search Records): Filter records where status = "unresolved".
3. Module 2 (Router):
   • Route A (Day 3 Check): timestamp <= now - 72 hours AND stage = "1_sent".
     Action: Call Stripe Customer Portal API, dispatch Day 3 firm reminder via Resend, and update Data Store record to stage = "2_sent".
   • Route B (Day 7 Check): timestamp <= now - 168 hours AND stage = "2_sent".
     Action: Call Stripe Customer Portal API, dispatch final 24-hour warning via Resend, post Slack alert to account manager, and update Data Store record to stage = "3_sent".

Financial Comparison: Make.com + Resend vs Proprietary Dunning SaaS

By taking control of your dunning infrastructure, you preserve 100% of your recovered capital. Calculate the exact burn rate savings for your startup using our SaaS Burn Rate Calculator.

Production Hardening: 4 Critical Dunning Best Practices

1. Grace Period Management: Set Stripe’s subscription retry schedule to “Smart Retries” over 2 weeks rather than immediate cancellation. This gives your 3-stage email flow adequate runway to convert.
2. Handle Webhook Idempotency: Stripe may deliver webhooks more than once. Use the event.id as a unique constraint in your Make.com Data Store to guarantee duplicate emails are never dispatched.
3. In-App Banner Integration: In addition to email, expose a banner in your web application when subscription.status == past_due linking to the Customer Portal session.
4. Resilient Error Handling: Protect your webhook listeners from crashing during third-party outages by following the blueprints in Make.com Error Handlers Explained.