Failed Payment Email Templates

Template Category Overview

Subscription billing failures are a constant operational tax for SaaS and membership businesses. When a card declines, you need to notify the customer quickly, avoid sounding punitive, and drive them to update their payment method — all while protecting revenue. These aren't manual invoice reminders sent to businesses chasing a specific bill; they're dunning messages triggered automatically by failed recurring charges, and the tone, timing, and calls-to-action are fundamentally different. The same structural sequences repeat across every charge cycle: a first notice, a retry-status update, and a final suspension warning. Retyping these or assembling them from scratch each time wastes time and introduces inconsistency. Lightning Assist lets billing and customer-success teams store each message as a snippet with placeholders for the customer name, plan, update-payment link, and suspension date — then expand it in any desktop app, email client included. AI Enhance can tighten the wording without inventing facts.

When to Use These Templates

Use these dunning templates whenever a recurring subscription charge fails — card declines, expired cards, bank blocks — and you need to move the customer through a structured recovery sequence before suspension. This is distinct from chasing a manually issued invoice to a business client; the audience here is a consumer or SaaS subscriber whose automatic billing quietly failed, often without their awareness. The first notice sets an expectation of continued access and a clear action. The retry message adds time pressure with a specific retry date. The final notice removes any ambiguity about consequences. Running all three from a snippet library keeps messaging consistent across billing cycles, agents, and customers, and ensures nothing important — plan name, amount, suspension date — is accidentally omitted.

Example Templates in This Category

• Card declined — first notice: friendly heads-up with a clear update-payment CTA.
• Payment retry / update method: second touch naming the retry date and how to update the card.
• Final notice before suspension: firm but courteous, exact suspension date and what access is lost.

Example Templates in Practice

Subject: Action needed — payment for [#Plan Name#] didn't go through

Hi [#First Name#],

We weren't able to charge [#Amount#] for your [#Plan Name#] subscription — your card was declined. Don't worry, your account is still fully active.

To keep things running smoothly, please update your payment method:
[#Payment Update URL#]

If you have questions, reply here and we'll sort it out.

[#Your Name / Support Team#]

Subject: We'll retry your payment on [#Retry Date#] — update your card now

Hi [#First Name#],

We'll attempt to charge [#Amount#] for your [#Plan Name#] subscription again on [#Retry Date#]. To avoid any interruption, please update your payment method before then:
[#Payment Update URL#]

If your card details are already correct, no action is needed — we'll take care of it automatically.

Need help? We're here.

[#Your Name / Support Team#]

Subject: Final notice — [#Plan Name#] suspends on [#Suspension Date#]

Hi [#First Name#],

This is a final notice: your [#Plan Name#] account will be suspended on [#Suspension Date#] because we've been unable to process payment of [#Amount#].

After suspension, you will lose access to [#specific features / data#]. Reactivating later requires going through our full setup process.

Resolve this now (takes 60 seconds):
[#Payment Update URL#]

If there's been a mistake or you need help, please reply immediately.

[#Your Name / Support Team#]

How to Get Started

Set up three snippets: a first notice (;paydecline), a retry / update-method message (;payretry), and a final suspension warning (;paysuspend). Add placeholders for the customer's first name, plan name, charge amount, retry or suspension date, and your payment-update URL. Type the trigger and Lightning Assist expands the full message inline as you type — no hotkey needed (or use Hotkey Mode) — in Gmail, Outlook, Intercom, or any desktop email client. AI Enhance can sharpen the urgency or tone of a draft without changing the factual content. For a shared customer-success library, keep the templates structural: placeholders supply the specifics at send time so no customer account data is baked into the snippet.

Pro Tips

• Lead the first notice with reassurance that access is still active — good-faith framing prevents cancellations before the customer even reads the CTA.
• In the retry message, name a specific retry date rather than saying 'soon' — vague timing confuses customers about when to ensure funds are available.
• The final notice must state the exact suspension date and specifically what access is lost — vagueness at this stage erodes trust rather than softening the blow.
• Keep placeholders for the payment-update URL in every message so no template ever goes out without a direct, clickable resolution path.