Dunning copy

Stripe Failed Payment Email Templates: 5 Sequences

The best recovery email is the one a customer actually reads and acts on. Type your SaaS name, customer name, and plan amount below to customize all 5 recovery sequences live, or copy the canonical {{merge_tags}} directly into your RenewalRescue editor.

Hi {{customer_name}},

We attempted to process your subscription renewal for {{merchant_name}} ({{amount}}), but the transaction did not go through with your card on file.

This usually happens due to temporary bank holds or an expired card. You can quickly review and update your payment method here:

-> {{invoice_or_billing_url}}

We will automatically retry the payment in 24 hours. If you have any questions, simply reply to this email.

Best,
The {{merchant_name}} Team

Hi {{customer_name}},

Just a quick follow-up regarding your {{merchant_name}} subscription. We tried to process your renewal again today, but your payment of {{amount}} was declined.

To make sure your workspace continues without interruption, please take 30 seconds to update your card on file:

-> {{invoice_or_billing_url}}

Once updated, your subscription will renew automatically. Let us know if you need any help.

Best,
The {{merchant_name}} Team

Hi {{customer_name}},

We have been unable to process your renewal for {{merchant_name}} ({{amount}}) after several attempts.

Your account is currently in a grace period, but access to your workspace and active features will pause in 48 hours unless your payment method is updated:

-> {{invoice_or_billing_url}}

We would love to keep you with us. If your billing details have changed or if you need an invoice receipt, update your details above or reply directly to this email.

Warm regards,
The {{merchant_name}} Team

Hi {{customer_name}},

Your bank requires 3D Secure authentication before they can authorize your renewal payment of {{amount}} for {{merchant_name}}.

Please click the secure link below to complete the one-step verification with your card issuer:

-> {{invoice_or_billing_url}}

This takes less than 30 seconds and immediately confirms your subscription.

Thank you,
The {{merchant_name}} Team

Hi {{customer_name}},

Because we were unable to process your {{amount}} renewal for {{merchant_name}}, we have temporarily paused your subscription so no further charges are attempted on your declined card.

Your workspace settings and historical data are safely preserved. Whenever you are ready to jump back in, you can update your payment method and reactivate your account in one click:

-> {{invoice_or_billing_url}}

If you meant to pause or need any assistance with your billing account, just reply to this email.

Best,
The {{merchant_name}} Team

What makes a recovery email effective

Effective dunning emails share three qualities: they are timely (sent shortly after the failure, not days later), they are specific (they name the product, subscription, or invoice at risk), and they give the customer a single clear next step: a direct link to update their payment method.

Vague emails ("there was a problem with your account") generate support tickets instead of self-service resolutions. Emails that feel punitive ("your access will be suspended immediately") trigger disputes and unsubscribes. The goal is to read as a helpful heads-up from a business the customer already chose to pay.

First-attempt vs follow-up tone

The tone should shift slightly across attempts. A first-attempt email can be matter-of-fact and assume the customer will fix it quickly: no drama, just the facts and a link. A second or third attempt can acknowledge that the customer may have missed the first message and gently restate the consequence of inaction (service interruption, not account deletion threats).

What should not change across attempts: your brand voice, the Reply-To address, and the clarity of the action step. Customers who received the first email and chose to act later should find the follow-up familiar, not jarring.

What to include in each message

Every recovery email should cover the same four elements, regardless of length:

• What happened - payment failed for {{merchant_name}} ({{amount}}).
• Why it matters - renewal will not complete until the payment goes through.
• What to do - a single, prominent link ({{invoice_or_billing_url}}) to update their payment method or retry.
• Who to contact - your Reply-To or support address if they have questions.

If you have a Stripe customer portal or Hosted Invoice page configured, the {{invoice_or_billing_url}} merge tag routes directly to the 1-click payment method flow without requiring a password login.

Interactive preview: generic emails vs branded dunning

Compare how generic payment processor notices look compared to an automated, high-converting RenewalRescue notification:

What not to say

Avoid language that erodes trust or creates legal exposure. "Your account has been suspended" is premature if the account is still active during a grace period. "We were unable to process your payment" is neutral; "your card was declined" can feel accusatory even when accurate. "Final notice" on a second email sets expectations you may not fulfil.

Copy that reads as a business communication rather than a collections notice consistently outperforms aggressive language in recovery rate and unsubscribe rate. You are not collecting a debt; you are helping a customer who wants your product stay subscribed.

Related reading

For the broader context on email timing and retry alignment, see dunning emails for Stripe and Stripe failed payment recovery.

Frequently asked questions

How long should a failed payment reminder email be?

Short. The customer needs to know what happened, why it matters, and what to do next. Three to five sentences is enough for a first attempt. Longer emails bury the action step and reduce click-through on the payment update link.

Should I personalise the email by failure reason?

When possible, yes. An expired card message ("your card ending in 4242 expired last month") reads more helpfully than a generic decline message. However, Stripe does not always surface the exact decline reason, so a good default template that works for any failure is more practical than trying to branch for every code.

What subject lines work for dunning emails?

Direct, factual subject lines outperform clever ones: "Action required: update your payment method for {{merchant_name}}", "Your {{merchant_name}} renewal did not go through", or "Your subscription payment failed". Avoid urgency bait ("URGENT: your account is about to be deleted") because it damages trust for high-LTV customers.

How do I keep recovery emails out of the spam folder?

Send from an authenticated domain (SPF, DKIM, DMARC), use a consistent Reply-To that matches your brand, avoid all-caps or excessive punctuation, and only send to customers with a real billing relationship. Spam complaints spike when reminders are sent too frequently or feel impersonal, so limit to one email per recovery attempt.