Failed recurring donations end monthly giving by accident

Aug 29
3 min read

Updated: 4 days ago

Introduction

A monthly donor's card expires. The payment fails, the platform tries twice more, and the gift stops. Nobody at the charity notices, and the donor assumes the money is still going out.

Eighteen months later somebody spots that the regular giving total has drifted downward. By then the relationship has cooled, and a supporter who never intended to stop has effectively lapsed. This is the largest quiet leak in monthly giving programmes, and it is almost entirely preventable.

1. Failed recurring donations are a retention problem, not an accounts problem

Frame it correctly and it gets attention.

These are not bookkeeping discrepancies. They are supporters who are still willing to give and have stopped without deciding to. Treated as a finance reconciliation issue, they are dealt with weeks late, if at all.

2. Know how your platform handles failures

The behaviour varies enormously.

How many retries, over what period, whether the donor is notified, whether you are notified, and whether the gift is cancelled automatically after a set number of attempts. Find out rather than assume, because the defaults are rarely what you would choose.

3. Check failures at least monthly

The single change that fixes most of this.

A recurring diary entry to pull the failed payments report and act on it. Organisations that do this recover a large proportion; those relying on someone noticing the total recover almost none.

4. Contact the donor quickly and helpfully

Tone matters because they have done nothing wrong.

A short message saying the payment did not go through, that it is probably an expired card, and here is the link to update it. No implication of failure on their part and no request for a different amount.

5. Make updating details genuinely easy

The recovery depends on the friction here.

A direct link to update payment details, working on a phone, without logging into an account they never created. If fixing it takes ten minutes they will intend to do it later and not.

6. Prompt before the card expires

The preventive version, and better than recovery.

Many platforms know the expiry date. A reminder a month ahead, offering to update, prevents the failure entirely and is far more comfortable for both sides than a message after the event.

7. Follow up more than once, then stop

Persistence within reason.

Two or three attempts across a few weeks, in different channels if you have them, then leave it. Someone who has not responded may have chosen to stop, and continuing indefinitely becomes an annoyance.

8. Record what happened

Data hygiene matters here.

Mark whether the gift was recovered, cancelled or left unresolved. Otherwise your active monthly donor count includes people who have not given for a year, and every projection built on it is wrong.

9. Track the involuntary churn rate separately

The number that reveals the size of the problem.

Distinguish donors who cancelled deliberately from those whose payments simply failed. The second figure is usually larger than expected and it is the one you can actually do something about.

Make deliberate cancellation easy and ask why. A difficult cancellation process produces card disputes and complaints rather than retained donors, and the reasons people give when leaving are among the most useful information the programme produces.

Conclusion

Treat failed payments as lapsed supporters rather than as an accounting task, because these donors never decided to stop.

Find out exactly how your platform handles retries and notifications, check the failed payments report every month, write to the donor promptly in a tone that assumes an expired card rather than a decision, make updating details a single easy step on a phone, prompt ahead of known expiry dates to prevent the failure entirely, follow up two or three times and then leave it, record the outcome so your active donor count stays honest, and track involuntary churn separately from deliberate cancellation.