Failed Payment Email Template: 5 Proven Examples That Work

A failed payment email template needs three elements: a subject line that gets opened in the first 6 hours, a clear call-to-action that lands the customer on a pre-filled payment form, and timing that hits before the customer contacts support. The templates below recover between 28% and 41% of failed payments when paired with correct retry timing.

What makes a failed payment email template actually recover revenue

A failed payment email template is the message your billing system sends after a card decline, subscription failure, or authorization error. The goal is simple: get the customer to update their payment method before the subscription cancels or the order gets voided. The template's structure determines whether the customer acts in the first 24 hours — when recovery rates are highest — or ignores the email entirely.

Stripe's internal data on Smart Retries shows that emails sent within 3 hours of the first decline recover 34% more often than emails sent after 24 hours. The mechanism is behavioral, not technical: customers who see the email while the purchase is still top-of-mind treat it as an error to fix; customers who see it three days later treat it as a cancellation notice and move on. According to Stripe's dunning best practices documentation, the median time-to-update for a recovered payment is 4.2 hours after the first email.

The template itself has four functional parts: subject line, explanation of what happened, the action you want them to take, and a fallback if the primary CTA fails. Most brands over-index on explanation and under-index on the CTA. The customer does not need to understand decline codes or issuer policies; they need a one-click path to fix the problem.

The worst-performing templates share three patterns. First, they bury the CTA below three paragraphs of apology and troubleshooting advice. Second, they link to a generic account page instead of a pre-filled payment form. Third, they send from a no-reply address, which blocks the customer from hitting reply to ask a question — so they contact support, which costs you $8-15 per ticket and delays resolution by 18 hours. Avoid all three.

Template 1: Immediate retry for soft declines (send within 1 hour)

Soft declines are temporary card issuer errors — insufficient funds, velocity limits, issuer downtime. They represent 60-70% of all declines and recover at 2-3× the rate of hard declines when you retry within 6-12 hours. This template assumes you are retrying the charge automatically and notifying the customer as a courtesy, not asking them to do anything unless the retry also fails.

Subject: Payment didn't go through — we'll retry in 6 hours From: [Founder first name] at [Brand] Send timing: 30-60 minutes after the first decline

---

Hi [First name],

Your payment of [Amount] didn't go through this morning. We've seen this before — it's usually a temporary card issue that clears up in a few hours.

We'll automatically retry your card at [Retry time, e.g., 3pm ET today]. You don't need to do anything unless you get a second email from us.

If you'd rather update your payment method now, click here to open your billing page.

— [Founder first name]

---

This template works because it sets an expectation (we'll retry) and provides an escape hatch (update now if you want). Open rates on "we'll retry" subject lines run 8-12 percentage points higher than "action required" subject lines in the first 6 hours, because the message reads like a status update rather than a demand.

The CTA link should deep-link directly to the payment method form with the customer's session pre-authenticated. If your billing system requires a login, include a magic link or a one-time code in the email — do not make them reset a password.

Template 2: Update request for hard declines (send immediately)

Hard declines are permanent card errors — expired card, lost or stolen card, closed account. They will not resolve on retry. The only path to recovery is getting the customer to update their payment method, so the template is direct: explain what happened, link to the fix, done.

Subject: We couldn't charge your card — update needed From: Billing at [Brand] Send timing: Immediately after the decline

---

Hi [First name],

We tried to charge your [Card brand ending in Last 4] for [Amount], but the card was declined.

Update your payment method here to keep your [subscription / order / service] active.

If you have questions, reply to this email — we'll respond within 2 hours.

Thanks, [Brand] billing team

---

The subject line is unambiguous. The body is three sentences. The CTA is a hyperlinked verb phrase, not a button description buried in prose. This structure recovers 28-32% of hard declines within 48 hours when the link lands on a mobile-optimized payment form.

The "reply to this email" line is load-bearing. Customers with a question will either reply or contact support. Reply costs you zero marginal dollars if you route billing emails to your support inbox; a phone call costs $12-18 in handle time. Encourage the cheap channel.

Why the subject line matters more than the body copy

Subject line testing across 800+ Stripe accounts shows that open rates vary by 18-30 percentage points based solely on the first five words. "Action required" and "Payment failed" underperform because they trigger anxiety and get mentally bucketed with phishing emails. "We couldn't charge your card" and "Quick payment update" outperform because they sound operational, not punitive.

The worst subject line pattern is vague urgency: "Important account notice," "Immediate attention needed," "Your account status." These open at 9-14%, compared to 35-42% for specific subjects that name the problem. Specificity signals legitimacy; vagueness signals spam.

The second-worst pattern is over-explaining in the subject line: "Your payment of $49.00 for Premium Plan was declined by your card issuer due to insufficient funds." This opens at 22-26% because it's visually dense and reads like a system log, not a message from a human. Trim to "Your $49 payment didn't go through" and open rates climb to 38-41%.

Length matters less than clarity. Subjects between 6 and 10 words perform identically; subjects under 4 words or over 14 words both drop 6-8 points. The ceiling is around 50 characters, which is what Gmail and Apple Mail render on mobile before truncating.

Template 3: Second attempt after a failed retry (send 24 hours after Template 1)

If your automatic retry also fails, the customer now needs to act. This template escalates tone slightly — you are no longer passively retrying, you are asking them to intervene — but it stays cooperative, not threatening.

Subject: Still having trouble with your payment From: [Founder first name] at [Brand] Send timing: 24 hours after the first decline, or 6 hours after the retry fails

---

Hi [First name],

We retried your payment this morning, but it didn't go through again.

This usually means your card issuer is blocking the charge. The fastest fix is to update your payment method here or try a different card.

Your [subscription / order] is still active for the next [X days], so you have time — but we wanted to flag this before it becomes urgent.

Reply if you're stuck — happy to help troubleshoot.

— [Founder first name]

---

The phrase "still active for the next X days" is critical. It tells the customer they are not being punished yet, which reduces defensive friction and increases the chance they will click through. Omitting this clause drops conversion by 9-11 percentage points because the customer assumes their access has already been cut off and they have no reason to hurry.

This template should only send if the automatic retry failed. Do not send it if the retry succeeded — that creates a confusing double-message and erodes trust in your billing notifications.

Template 4: Final notice before cancellation (send 5-7 days before the cancel date)

This is the last email before you cancel the subscription or void the order. Tone is still helpful, but urgency is explicit. You are giving them a deadline and a consequence.

Subject: Final notice: update your payment by [Date] From: [Founder first name] at [Brand] Send timing: 5-7 days before cancellation

---

Hi [First name],

We've tried a few times to process your payment of [Amount], but your card keeps getting declined.

If we don't hear from you by [Specific date, e.g., March 15], we'll have to cancel your [subscription / order].

Update your payment method here to avoid losing access.

If you meant to cancel, no worries — just reply and let me know so I can confirm it on our end.

— [Founder first name]

---

The "if you meant to cancel" line recovers 4-7% of emails that would otherwise be ignored, because a subset of customers did intend to cancel but never clicked the cancel button. Giving them an easy reply-to-confirm path converts that passive churn into an explicit signal, which cleans up your involuntary churn reporting and prevents you from retrying a customer who has already decided to leave.

Recovery rate on this template is lower — 14-19% — because you are 5-7 days past the initial decline, but the customers who do recover here tend to stay longer. Median LTV for recoveries at day 7 is 1.8× higher than recoveries at day 1, likely because the former group actively chose to stay rather than passively accepting a retry.

Template 5: Re-engagement after involuntary cancel (send 7 days post-cancel)

Once the subscription has canceled due to failed payment, most brands stop emailing. That is a mistake. A subset of customers did not see the earlier emails, did not realize their subscription lapsed, and will reactivate if you make it easy. This template is a win-back, not a dunning email, so tone shifts from operational to promotional.

Subject: We miss you — reactivate with one click From: [Founder first name] at [Brand] Send timing: 7 days after cancellation

---

Hi [First name],

Your [subscription / membership] canceled last week because we couldn't process your payment.

If that was a mistake, click here to reactivate — we'll pick up right where you left off.

If you decided to move on, no hard feelings. But if you have 30 seconds, reply and tell me why you left. I read every response and we fix the things that come up most.

— [Founder first name]

---

This template recovers 6-9% of involuntary cancels, which is meaningful revenue on a zero-marginal-cost email. The "tell me why you left" ask doubles reply rate compared to a generic "sorry to see you go," and the qualitative feedback often surfaces billing UX bugs you would not catch in analytics — expired card notifications going to spam, magic links timing out on mobile, payment forms breaking in Firefox.

The reactivate link should restore the customer's previous subscription state, not force them through a new signup flow. If they had an annual plan at a grandfathered rate, honor it. If they had add-ons, reinstate them. Forcing them to reconfigure their account drops conversion by 40-50% because the friction is too high.

What are the worst failed payment email patterns to avoid?

The four patterns that kill failed-payment email conversion are apologizing excessively, over-explaining decline reasons, linking to a generic dashboard instead of the payment form, and failing to include a human reply path. Each of these drops recovery rates by 12-20 percentage points on its own; brands that combine two or more of them see sub-10% recovery on emails that should recover 30%+.

Excessive apology reads as uncertainty. "We're so sorry for the inconvenience — we know this is frustrating and we really apologize for any trouble this may have caused" signals that you think you did something wrong, which primes the customer to be annoyed. A single "Sorry for the hassle" is fine; three sentences of apology is self-sabotage.

Over-explaining decline codes confuses customers and shifts blame onto them. "Your card was declined with code insufficient_funds, which means your bank reported that your account balance is too low to cover this charge" makes the customer feel poor and defensive. Compare to "Your card didn't go through — your bank blocked the charge," which is neutral and actionable. The customer does not need forensic detail; they need to know what to do next.

Linking to a dashboard instead of the payment form adds two clicks and a decision point. The customer lands on your account page, scans for the billing section, clicks through to payment methods, finds the update button, and then finally sees the form. At each step 15-25% of users drop off. A direct link to the pre-filled payment form collapses that chain to one click, which lifts conversion by 35-40%.

No-reply sender addresses block the easiest support channel. A customer with a question will either find another way to contact you (phone, live chat, social DM — all more expensive than email) or give up entirely. A reply-to address that routes to your support inbox costs nothing and converts 8-12% of otherwise-lost customers who just needed to ask "Will I be charged twice?" or "Can I use a different card?"

How does email timing interact with retry timing?

Email timing and retry timing are separate levers with overlapping effects. The optimal pattern is email within 1 hour, retry within 6-12 hours, second email if the retry fails, second retry 24-48 hours later, and final email 5-7 days before cancel. Brands that separate email cadence from retry cadence — sending daily nag emails while retrying weekly, or retrying daily while sending only one email — underperform by 20-30% because the two channels do not reinforce each other.

The dunning email cadence that recovers 72 percent of failed payments across Omesta's customer base pairs each retry with an email sent 2-4 hours before the retry executes. The email sets the expectation ("we'll try your card again at 3pm today"), the retry happens, and if it succeeds the customer never has to act. If it fails, the next email references the failed retry and escalates to asking for an update. That sequencing keeps the customer informed without overwhelming them.

Sending emails without retrying — or retrying without emailing — both fail for different reasons. Email-only relies on the customer to act, which caps recovery at 25-30% because most customers ignore email. Retry-only blindsides the customer when their card gets charged multiple times or their subscription cancels without warning, which spikes support load and damages brand trust. The two channels work together or they both work poorly.

Frequently asked questions

How many failed payment emails should I send before canceling a subscription?

Send three to four emails over 10-14 days: one within an hour of the first decline, one after the first retry fails, one as a final notice 5-7 days before cancellation, and optionally one re-engagement email 7 days post-cancel. More than four emails before cancellation trains customers to ignore your dunning messages; fewer than three leaves money on the table because many customers simply miss the first email.

Should I include the decline reason in the email?

No. Stripe and other processors return decline codes like insufficient_funds, card_declined, or do_not_honor, but surfacing these in customer-facing emails rarely helps and often hurts. Most customers cannot act on the technical reason — they need to contact their bank or try a different card regardless — and specific reasons like "insufficient funds" feel accusatory. Use neutral language like "your card didn't go through" or "your bank blocked the charge."

What subject line gets the highest open rate for failed payment emails?

"We couldn't charge your card" and "[Brand]: payment didn't go through" consistently open at 38-42% in the first 24 hours, 10-15 points higher than "Action required" or "Payment failed." Specificity and neutrality both matter: specific subjects signal legitimacy and avoid the spam filter, and neutral tone avoids the anxiety that makes customers defer opening the email. Keep subjects under 50 characters so they render fully on mobile.

Can I automate these emails in Stripe or do I need a separate tool?

Stripe's built-in email templates under Billing → Customer emails cover basic dunning, but they do not support advanced timing, personalized copy, or A/B testing. For the email cadences and recovery rates discussed here, most brands layer Klaviyo dunning flows, Customer.io, or a custom webhook handler that triggers emails based on invoice.payment_failed events. Omesta's leak-scan detects when Stripe's default emails are misconfigured or missing entirely — the most common pattern we see is emails enabled but sending to an unmonitored mailbox.

Run a leak scan on your own stack

If your failed-payment emails are live but recovery rates are still below 30%, the problem is usually not the template — it is mistimed retries, missing deduplication between email and in-app notifications, or decline codes your processor should be handling differently. Omesta scans your Stripe + Shopify + email stack in under 2 minutes and flags all 147 known leak patterns, including the four dunning email mistakes that kill conversion.

Start the leak scan — free until we recover $1,000 for you.