My harmonious padlet by Gratefully

gratefully451 — 2026-09-11 06:41:05 UTC

The quietest revenue leak in fundraising is an expiring card

Best fit: annual fund, operations, monthly giving programme managers

A monthly donor gives you $25 a month for four years. Then their card expires, the charge fails, and nothing happens. No conversation, no decision, no disagreement. Just an absence.

Twelve months later they appear on a lapsed report and someone writes them a letter about how much you miss them. They did not go anywhere.

This is the cheapest recoverable revenue in fundraising, and most organisations do not look for it.

Why it is invisible

A failed recurring payment does not announce itself. It produces no complaint, no unsubscribe, no inbound contact. From the donor's side, nothing happened at all, because most people do not audit their statements for charities that stopped charging them.

From your side, the signal exists but arrives in a place nobody reads: a payment processor notification, or a report inside the giving platform that is separate from the CRM where the fundraising team lives.

So a decision that nobody made removes income that nobody notices, and the loss compounds every month it goes unchecked.

The arithmetic

Take a programme with 400 monthly donors at an average of $22. Card expiries and failures run at a few percent a month in most portfolios, and lapsed recurring donors are rarely recovered passively.

Even at a modest failure rate, a programme that size loses several thousand dollars a year that had already been committed, from people who had already decided to support you and had not changed their mind. The gift was won. It was lost administratively.

Against the cost of acquiring an equivalent new monthly donor, this is the highest-return work available to a development team, and it is filing rather than fundraising.

What to actually do

Look monthly, not annually. Fifteen minutes. Pull failed and declined recurring transactions since the last check. That single habit captures most of the value here.

Treat it as a service message, not an appeal. These people did not lapse. Asking them to come back misreads what happened and can be mildly insulting. "Your card on file expired, here is a link to update it" is the correct message, and it converts far better than warmth.

Separate this group out of every lapsed campaign. A mechanical failure and a decision to stop giving look identical on a lapsed report and need opposite messages. Splitting them is the single change that most improves a recapture campaign, which we set out in a piece on identifying donors at risk of lapsing.

Turn on card updater services if your processor offers them. Most major processors can refresh expiring card details automatically with the networks. It is not universal and it is not perfect, but it removes a meaningful share of the problem without any human looking.

The wider pattern

Card expiry is the clearest example of a category worth naming: revenue lost to administration rather than to a donor decision.

Others in the same family. A donor moves and the mail returns undelivered, so they stop hearing from you and eventually stop giving. An email address decays and engagement drops to zero, which then reads as disinterest. A pledge reminder never goes out because the person who owned the schedule left.

None of these are fundraising failures. They are operational ones, and they are invisible because the metric they damage, retention, is reported annually while the failures happen daily.

The practical answer is not more analysis. It is a short monthly habit, and making sure whoever runs donor re-engagement can tell a payment failure from a decision before they write anything.

Where to start

This month, pull two lists. Failed recurring payments, and mail or email that hard bounced.

Handle both as service issues within a week, with no ask attached. Then count how many donors that recovered, and compare it to what the same effort would have cost you in acquisition.

That number is usually the most persuasive argument for retention work that a development team can put in front of a board, because it is real money from your own file rather than a sector multiplier.

Further reading