Follow-ups in your own name vs Stripe's failed payment emails
Stripe Billing can send customers an email when their card payment fails, with a link to fix it. It is free, it works, and many businesses never go further. Follow-ups sent in your own company's name are a different tool with a different purpose. This article compares the two honestly, including when you do not need the second.
What Stripe's emails do
In your Billing settings you can let Stripe email customers about failed card payments and about cards that are about to expire, and send a link when a payment needs 3-D Secure authentication. The emails carry your business name and branding settings and point to a Stripe-hosted page where the customer can pay or update their card.
- They are free and take minutes to switch on.
- They handle the update link and authentication properly.
- They stop by themselves when the invoice is paid.
If you have not switched them on, do that first. Every other improvement is measured against a starting point where customers are at least told.
Where they are limited
Stripe's emails are designed to work for every business on the platform. That generality has a cost.
- Generic wording. The message says a payment failed; it does not adapt to the reason. A customer whose card expired and a customer whose bank asks for a confirmation read roughly the same thing.
- Limited sequence. You control whether they are sent, not a sequence of several messages with different tones and timings.
- Sender identity. Depending on your settings, the email can feel like a notification from a payment processor rather than a note from the company the customer signed up with. Some customers ignore anything that looks automatic.
- No measurement. You see payments that came back, not what the email changed compared with not sending it.
What follow-ups in your own name add
A follow-up sent in your company's name comes from an address on your domain, signed by a person, written in your tone and in the customer's language. It can be shaped around the decline reason and spread over several steps, as in our dunning email templates.
- Recognition: the customer sees the name of the product they use every day, not a payment processor.
- Relevance: 'your card expired, here is where to add the new one' is easier to act on than 'there was a problem with your payment'.
- Replies: customers can answer the email, and the answer reaches you. Many problems are solved by a one-line reply.
- Respect for long-standing customers: a customer who has paid for years can receive a personal message instead of a template.
None of this requires changing how Stripe charges. Follow-ups can link to the same hosted invoice page and let Stripe's retries continue as before.
Side by side
| Aspect | Stripe's emails | Follow-ups in your name |
|---|---|---|
| Cost | Included | Your time, or a tool |
| Sender | Your business name through Stripe | Your domain, a real signature |
| Adapted to the decline | No | Yes, if the process reads the code |
| Several steps | Limited | Yes |
| Replies reach you | Depends on your settings | Yes |
| Measured against doing nothing | No | Possible with a holdout group |
What a good follow-up in your name looks like
- A subject line that names your product and the problem, without alarm: 'Your [Company] payment did not go through'.
- A first sentence with the facts: plan, amount, what the bank said.
- One button, leading to a page where the customer pays without logging in.
- A line inviting a reply, and a real person who reads the replies.
- A signature with a first name, not 'The billing team'.
It is less about clever copywriting than about removing every reason to postpone. The customer should understand the email in five seconds and fix the payment in one minute.
Running both without confusing customers
The worst outcome is a customer receiving three emails in one hour about the same invoice, from two senders, with two different links. If you add your own follow-ups, decide who says what.
- Either turn off Stripe's failed payment email and let your sequence handle that moment, or keep it and start your own sequence a little later, with a different angle.
- Keep Stripe's authentication link if your own follow-ups cannot handle 3-D Secure; otherwise make sure your first email covers it immediately.
- Use the same destination for every link: the hosted invoice page.
- Check the invoice status right before every send.
- Keep the same tone in both, so that the customer feels they are hearing from one company, not from two systems.
When Stripe's emails are enough
If you have few failed payments, mostly small monthly amounts, and customers who rarely reply, Stripe's emails with Smart Retries may cover most of what you can recover. The way to know is to measure what is still being lost after them, as described in how much do failed payments cost you, and what an addition actually changes, with a holdout group.
Reclaiva sends follow-ups in your company's name, adapted to each decline, starts in preview mode so you can read every email before anything is sent, and reports each month the revenue recovered on top of what Stripe recovers on its own, measured against a holdout group, for a fixed price with no commission. If the measured difference is small, you see it.