The templates
Each one copies with its subject line. Change the parts in brackets, and put the same billing link in every email of the sequence.
Subject: Your payment for [Product] did not go through
Subject: Reminder: please update your card for [Product]
Subject: Your [Product] access pauses on [date]
Subject: The card on your [Product] account expires soon
Subject: All sorted: your [Product] payment went through
Subject: Your card for [Product]
Subject: Payment failed: [Product]
Payment failed email subject lines
Plain beats clever. The subject has to say it is about a payment and that it needs them, and name the product so it cannot be mistaken for phishing. Save the date for the final notice, where it does the work.
- Your payment for [Product] did not go through
- Action needed: update your card for [Product]
- Reminder: your [Product] payment is still outstanding
- Your [Product] access pauses on [date]
- The card on your [Product] account expires soon
- All sorted: your [Product] payment went through
What makes a failed payment email work
- No blame. “Your payment did not go through”, never “you failed to pay”. The card, the bank or the expiry date did it, and the customer knows that.
- One link, near the top. The only thing you need from them is a new card. Put the link where someone reading on a phone sees it without scrolling.
- A real date on the last one. “Access pauses on 12 October” gets a card updated; “soon” does not.
- An easy way out. “If you meant to cancel, just reply” costs you nothing, and someone who wanted to leave says so instead of ignoring the reminders and disputing the charge later.
- A thank-you when it is fixed. Two lines saying it went through close the loop and stop them wondering whether it worked.
- No scare words. “URGENT”, “FINAL WARNING” and red capitals read like phishing, which is the last thing an email asking for card details should resemble.
Decide who sends what: you or your billing platform
Stripe retries failed subscription payments automatically, on a schedule you can set or leave to its Smart Retries, and it can email customers about failed payments and expiring cards itself. Those customer emails are settings in your Stripe dashboard, and other billing platforms have their own versions. Know which are switched on before you send a single one of the templates above.
- Let the platform send the mechanical ones if you are happy with how they read: the first notice and the card-expiring warning are mostly a link, and the platform’s link goes straight to the right page.
- Send the personal ones yourself: the final notice, anything to a long-time customer, and every reply to someone who writes back.
- Never both. A customer who gets the platform’s notice and yours on the same morning reads it as two problems. Turn one of them off.
- Match the dates to the settings. The date in your final notice should be the day the platform actually cancels or pauses the subscription after its last retry, which is a setting too.
When the customer writes back
Most of this sequence is mechanical. The part that is not is the reply: “I have a new card, can you try again?”, “I thought I had cancelled”, “can I switch to yearly instead?”. Those land in your inbox, and answering them well means knowing what actually happened with the payment.
With Stripe connected, Moorline shows the failed charge beside the conversation, along with the customer’s plan and the payments that did go through. It is read-only: it cannot retry the payment, refund it or change the plan, so that still happens in Stripe. And when the customer says they will update the card at the weekend, the conversation sits in waiting on them and comes back to you, rather than being archived with everything else. The playbook on customer support as a solo founder covers why billing context belongs next to the email in the first place.
Questions people ask
What should a failed payment email say?
That the payment did not go through, how much and for what, a single link to update the card, and what happens if nothing changes, with a date on the final notice. Keep it short and neutral. A failed payment is often an expired card or a cautious bank, and an email that treats the customer as if they refused to pay is the one that makes them leave.
How many failed payment emails should I send?
Three is a common shape: a notice the day it fails, a reminder a few days later, and a final notice a few days before access stops. Line them up with your billing platform’s retry schedule, and stop the moment the payment succeeds or the customer replies.
What is a good subject line for a payment failed email?
Plain and specific, such as "Your payment for [Product] did not go through" or "Action needed: update your card for [Product]". Name the product so it is not mistaken for phishing, and put the date in the subject of the final notice. Avoid capitals, "URGENT" and anything that sounds like a threat.
Does Stripe send failed payment emails automatically?
It can. Stripe retries failed subscription payments automatically, and it has customer email settings for failed payments and expiring cards that include a link for the customer to update their details. Whether those go out depends on your billing settings, so check them before adding your own, or the customer gets the same news twice.
Should I cut off access as soon as a payment fails?
No. Give the retries and the reminders time to work, a week or two, and keep the account working while they do. Cutting access on the first decline punishes the customer for their bank’s decision, and a working account is the best reason they have to update the card.