Why recurring giving matters - and how Givr makes it work

The problem with one-off giving (and why churches need recurring donations)

Churches know the score. You can fill a room with 200 people on Sunday, pass the plate, and walk away with £800. But next Sunday? You're starting from zero. There's no continuity. No predictability. The treasurer can't plan. The budget feels like it's written in sand.

Recurring giving changes that equation completely. When someone commits to £20 a month, you're no longer chasing 52 one-off donations. You're building a revenue floor. You know what's coming in. You can fund the heating. You can plan the mission trip.

The problem is that asking people to set up a standing order feels clunky. It requires going to their bank, filling in forms, remembering sort codes and account numbers. By the time they've waded through that, you've lost them. Even with good intentions, the friction is real.

Why we chose GoCardless for Givr

When we started building the recurring giving feature, we looked at a few routes. We could have built a basic subscription system ourselves, but that would have meant handling payment processing directly, which opened the door to regulatory headaches we didn't want to invite.

GoCardless made sense immediately. They're built for recurring payments in the UK. They handle Direct Debits natively, which matters because Direct Debit is the friction-free way British people give standing commitments. It's trusted. It's reversible. It doesn't feel risky.

The integration meant our users (the churches) could offer recurring giving without needing a separate account, separate login, or separate platform. Someone scans the QR code, gives once if they want, or taps the recurring option and sets up a Direct Debit right there in the browser. Fifteen seconds. No app. Done.

For the treasurer, that means every recurring gift flows straight into the reconciliation dashboard, bundled with Gift Aid data, with HMRC submission happening automatically. One platform. One view of giving.

The recurring giving workflow: what actually happens

Let's walk through the real sequence because it matters.

A congregant scans the QR code on a Sunday. The browser opens Givr. They see the option to give once, or to set up recurring giving. If they choose recurring, they enter an amount (say, £15 a month), select the frequency, and then the Direct Debit mandate appears on screen. They authorise it. Payment processes on the date they choose.

From the church's end, that recurring donation appears on the dashboard under that donor's name. If they've submitted a Gift Aid declaration (which happens simultaneously when they first give, no separate form), the £15 is automatically marked for Gift Aid at the point of setup. When the monthly payment lands, the Gift Aid claim builds up in the background.

The real win comes at the HMRC submission stage. Instead of the treasurer manually tracking recurring gifts separately, trying to remember which donors are Gift Aid eligible and which aren't, Givr collects it all. The platform then submits the claim to HMRC Charities Online on your behalf. No spreadsheet. No phone calls to HMRC. No wondering if you've left money on the table.

That's the non-obvious part. Recurring giving isn't just about smoother cash flow. It's about smoother Gift Aid. Most UK churches claim Gift Aid on maybe 60% of what they're eligible for. That £560 million figure I mentioned? A lot of it sits in recurring giving that simply never gets claimed because the manual process is too complicated.

What we learned building this (and why it took longer than we expected)

One thing I should say plainly: building the recurring integration correctly took longer than I'd planned. GoCardless handles the payment side brilliantly, but making sure it talked cleanly to our Gift Aid automation, our HMRC submission, and our dashboard required thinking through scenarios we hadn't fully mapped. What happens if a donor changes the frequency mid-month? What if a Direct Debit fails and needs to retry? How do we report that accurately to HMRC?

The other thing I underestimated was how much treasurers wanted to see not just that the recurring donation was happening, but when it was happening. We built in a calendar view so you can see when each Direct Debit is scheduled to land. Small detail. Huge for planning.

We also learned that churches wanted to set minimum amounts for recurring gifts. Some wanted to keep their one-off and recurring streams separate for reporting. So we built those features in. Not because we guessed. Because treasurers told us.

The Gift Aid piece (why this matters more than people realise)

Here's the thing that genuinely bothers me when I talk to churches using other platforms: they can set up recurring giving, but they're not claiming the Gift Aid on it. Which means they're leaving money on the table every single month.

In Givr, once a congregant has given (and submitted a Gift Aid declaration), every subsequent recurring donation is automatically flagged as Gift Aid eligible. When Givr submits to HMRC, those claims go in. You don't have to do anything. The system remembers. The claim goes through. The money comes back to the church.

For someone giving £20 a month with Gift Aid, that's an extra £5 going back to the church every month. Over a year, that's £60. Over five years, that's £300. Multiply that across 50 recurring donors, and you're looking at several thousand pounds a year that most churches simply aren't capturing today.

That's why this feature exists. Not because recurring giving is trendy. But because recurring giving without Gift Aid automation is leaving your church's money at HMRC's door.

Setting it up: what the treasurer actually needs to do

If you're running Givr on the Gather tier (which includes recurring giving and HMRC submission), the setup is straightforward. You've already connected Stripe so that one-off giving works. Recurring giving uses GoCardless, so you'll go through a quick authorisation with them (similar to connecting Stripe). Takes five minutes.

Once that's live, your congregants see the recurring option on the giving page. You can set how long the recurring commitment lasts (open-ended, or until a certain date). You can create different recurring "campaigns" if you want (e.g., a campaign for building fund donations separate from general offerings).

From your dashboard, you see which donors have active recurring commitments, when payments are coming, and the Gift Aid impact. HMRC submission still happens automatically every quarter.

The treasurer doesn't need to touch GoCardless directly. Everything flows through Givr.