Dunning Examples

Payment Declined Email Examples for SaaS & Stripe

Browse high-converting payment declined email examples tailored for recurring SaaS subscriptions on Stripe. Customize the decline scenario below to generate copy for soft declines, expired cards, and SCA challenges.

Hi Alex,

Your monthly Acme Cloud renewal ($49/mo) did not go through today because the credit card on file has expired.

Because expired cards cannot clear automatic retries, please take 30 seconds to enter your new card details using your secure billing link below:

-> {{invoice_or_billing_url}}

As soon as your card is updated, your subscription will renew automatically with zero downtime.

Best,
The Acme Cloud Team

Why one payment declined email example is not enough

A customer whose corporate Visa expired last month needs a different message than a customer whose bank flagged a cross-border renewal for 3D Secure verification. Sending the exact same boilerplate alert for every failure lowers click-through rates and confuses subscribers.

The strongest payment declined email examples adapt to the stage of the recovery timeline: a helpful heads-up on Day 1, a direct reminder on Day 3, and a clear grace-period warning before workspace access pauses on Day 7.

3-Step Payment Declined Communication Framework

How to structure a 3-email declined payment sequence

Example 1 (30 minutes post-failure) assumes the decline is temporary. Keep it under 90 words, mention the upcoming automatic retry, and include the update link for convenience.

Example 2 (72 hours post-failure) lets the customer know the second retry also failed and asks them to switch cards or confirm with their bank. Example 3 (Day 7) clearly states the 48-hour countdown before subscription features pause.

Conversion lift from multi-step examples

In Stripe subscription cohorts, the first email typically drives 50% of total email-assisted recoveries, the Day 3 follow-up captures another 30%, and the final grace-period notice recovers the remaining 20% from busy founders and finance teams.

Frequently asked questions

What makes a payment declined email example convert well?

Clarity, brevity, and a single frictionless call to action. High-converting examples avoid red warning banners or legalistic language and instead read like a personal note from the product team with a direct Stripe update link.

How many payment declined emails should a SaaS business send per failed invoice?

Three to four emails spaced across a 7-to-10-day grace period is the sweet spot. Sending more than one email per retry attempt increases spam complaints without improving recovery rates.

Should payment declined email examples include the invoice amount?

Yes. Including the exact renewal amount via the {{amount}} merge tag builds trust and helps corporate cardholders recognize the recurring software charge immediately.

How do I prevent duplicate payment declined emails when Stripe retries webhooks?

Use an idempotent recovery engine like RenewalRescue that deduplicates Stripe invoice.payment_failed deliveries by invoice ID and attempt count before dispatching any email.