Does GoCardless Send Automatic Payment Reminders for Failed Payments?

A Direct Debit you set up months ago quietly failed this week. You found out from a dashboard notification, not from the client, and now you are staring at a payment marked failed and wondering whether anyone told them. Do you email? Does GoCardless already handle it? Are you about to send a slightly awkward message about something they were warned about two days ago?

It is a fair question, because the answer sits in an odd middle ground. GoCardless does contact your customer automatically when a payment fails, and it contacts them again before it tries to take the money a second time. So the mechanical side is covered. What is not covered is the part that actually gets a stalled payment resolved when the retries run out.

This guide walks through the exact emails GoCardless sends around a failed payment, how the automatic retry feature changes the timeline, and which conversations still land on your desk. By the end you will know what your customer has already been told, so you can pick up the thread instead of repeating it.

Does GoCardless Send Automatic Payment Reminders? Yes, But They Are Event Notifications

GoCardless sends a fixed set of automated emails to your customer whenever something happens to their mandate or their payment. You do not switch these on and you cannot write them yourself. They fire off the event, and three of them matter when a collection fails.

Per GoCardless documentation on payer notifications, the relevant three are an advance notice of an upcoming collection, a failure notice titled along the lines of "Your payment has failed," and a reattempt notice when a previously failed payment is tried again. The failure notice is the one people ask about, and it goes out once GoCardless receives word from the customer's bank, most commonly one business day after the charge date.

So by the time you notice the failed status, your customer has usually already been emailed about it. That is genuinely useful. It also explains why a follow-up from you that opens with "I wanted to let you know your payment failed" can feel oddly redundant to the person reading it.

What Success+ Retries Change About the Timeline

If you have enabled the automatic retry feature, GoCardless will try the collection again on its own rather than leaving the failed payment sitting there. This is worth understanding before you send anything, because a retry already scheduled for next Tuesday changes what your message should say.

The default configuration retries three times within a four-week window, and GoCardless reports recovery rates of up to 70 percent on that setting. You can adjust the window and the number of attempts, delay the first retry by a set number of business days, and turn on a filter that skips retries when the odds of another failure are very high. Each attempt is charged at your normal transaction rate, so more retries is not automatically better.

Two practical details are easy to miss. Retries land on business days and are subject to each scheme's daily submission cut-off, so a retry is never same-day money. And under the Bacs rules, your customer must be told the retry date before the money is taken, which means every attempt generates another email in their inbox.

That detail shapes your timing. If retries are running, your customer is already hearing from GoCardless on a schedule, and piling your own reminders on top creates noise rather than urgency.

The Difference Between a Notification and a Nudge

Here is the distinction that resolves most of the confusion. GoCardless emails describe the state of a bank instruction. They tell your customer what happened to a collection and what will happen next. They are accurate, transactional, and written in the payment processor's voice.

A follow-up, by contrast, asks someone to do something. It comes from you, references the work, and gives the person a clear next step. When a Direct Debit fails because a card was replaced, an account was closed, or a balance ran short, the fix is usually an action only your customer can take. A status email rarely prompts that action, because it reads like a receipt rather than a request.

This is why plenty of businesses using GoCardless still keep a follow-up routine. Not because the notifications are broken, but because notifications and nudges do different jobs.

The One-Email Limit Nobody Warns You About

Payer notifications go to a single email address per customer record. One address, no CC list, no second contact. If your customer is a solo client that is fine. If your customer is a company where the person who signed the agreement is not the person who watches the bank account, every failure email lands with whoever happens to be on file.

That is a quiet source of delay. The notification technically went out and the record shows the customer was informed, but the message reached an inbox that cannot act on it. Your follow-up is often the first one that reaches someone who can.

What GoCardless Notifications Do Not Cover at All

The automated emails are tied to mandates and collections. Step outside that and there is nothing running in the background for you:

A one-off invoice you sent by email with no mandate attached. No mandate means no payment event, which means no notification of any kind.
The gap after the final retry. When the attempts are exhausted, the emails stop and the balance stays open. Nothing further is sent.
A cancelled or expired mandate. Your customer is told once. If they do not act on it, the next scheduled collection simply never happens.
Any reply that is a question rather than a payment. Those come to you and need a human answer.
Clients you invoice through a different tool entirely. Mixed setups are common, and only the GoCardless side generates automated email.

The middle item is the one that costs real money. Retries recover a large share of failures, but the share that survives all three attempts is exactly the group least likely to resolve itself, and it is the moment the automation goes quiet.

A Follow-Up Rhythm That Fits Around the Retries

Because your customer is already receiving scheduled emails, the goal is to be complementary rather than louder. A rhythm that works well:

Stay quiet for the first failure if a retry is already scheduled. The system is handling it and the customer knows.
Reach out after the second failure. Two failures usually means something structural, like a closed account, and structural problems do not fix themselves on the third attempt.
Send a real follow-up the day after the final retry. This is the highest-value message you will send, and it is the one most often forgotten because the dashboard has stopped generating activity.
Reference what they already received. A line like "you may have seen a note from our payment provider" saves them from re-reading three emails to work out what you mean.
Ask for one specific action. Update the bank details, confirm a new date, or reply with a question. One clear step beats a general request to sort it out.

A failed Direct Debit is usually accidental, so warmth costs you nothing and gets a faster reply. Our buyer checklist for invoice reminder software covers what to look for if you want this handled for you, and if you also collect card payments elsewhere, the same questions come up with Stripe's automatic reminders for unpaid invoices.

Settings Worth Checking This Week

Five minutes in the dashboard removes most of the guesswork about what your customers are being told.

Confirm whether automatic retries are actually enabled, and for which schemes. Many accounts assume they are on when they are not.
Note your retry window and attempt count, then write the end of that window on your calendar. That date is when follow-up becomes your job.
Audit the email address on your top customer records. One wrong address quietly disables every notification for that client.
Decide whether the failure filter suits you. Skipping doomed attempts saves transaction fees but shortens the automated runway.
List the clients you bill outside GoCardless. That list has no automated email behind it at all.

Covering the Part That Stays Manual

Once you have mapped the automated coverage, what is left is a small but persistent set of messages: the second-failure check-in, the post-retry follow-up, and everything for clients billed elsewhere. Each one is short. They just arrive on unpredictable days, in ones and twos, and they are easy to postpone because nothing breaks when you do.

Some people handle this with a weekly calendar block and a saved template, which works if the volume is low and the discipline holds. Others put a reminder layer on top of whatever they already use to bill, so the follow-ups go out on schedule regardless of how the week goes. That is the job DueDrop does, sitting alongside your existing tools and sending the friendly nudges that a payment processor's status emails were never designed to be.

Either way, the useful shift is mental. Stop asking whether your provider sends reminders, and start asking which specific moments in your own process have no message attached to them. That list is short, and it is where the unpaid balances live.

Frequently Asked Questions

Does GoCardless tell my customer when a payment fails?

Yes, automatically. GoCardless emails the customer once it receives the failure notice from their bank, most commonly one business day after the charge date. You do not need to enable it, and you cannot edit the wording.

Will my customer know a retry is coming?

Yes. Under the Bacs Direct Debit rules, customers must be notified of the retry date before the money is taken, so every retry attempt generates its own advance email.

How many times does GoCardless retry a failed payment?

By default, up to three attempts inside a four-week window when automatic retries are switched on. You can change the window and the number of attempts, and each attempt is billed at your standard transaction rate.

Can I send the failure email to more than one contact?

No. Payer notifications go to one email address per customer record. If several people at a client need to know, that has to come from your side.

What happens after the last retry fails?

The automated emails stop and the balance stays open. No further notification is sent, so any follow-up from that point is entirely yours to send.

The Short List

Failure and retry emails are automatic and cannot be customised, so assume your customer already knows.
Automatic retries default to three attempts over four weeks and recover a large share of failures on their own.
Notifications describe a bank instruction. They do not ask anyone to do anything.
One email address per customer means multi-person clients often never see the notice.
The day after the final retry is the most valuable message you will send, and nothing prompts you to send it.

For more on covering the gaps your billing tools leave behind, browse the rest of our guides on invoice follow-up.