Scan. Give. Claimed. How QR-code giving actually works

The fifteen-second problem nobody talks about

Church giving in the UK has a friction problem. Someone walks into a Sunday service, feels moved to give, and faces a choice: find the collection plate (increasingly rare), set up a bank standing order (takes days, requires paperwork), or download an app (downloads what? which app?). Most people give up. The money doesn't come in. And if it does, the Gift Aid paperwork sits in a spreadsheet somewhere, unclaimed.

We built Givr around a simple observation: what if giving took fifteen seconds? No app. No account. No form to fill. Just a QR code on the hymn sheet or projected on screen, a quick scan, and they're done.

The technical side is straightforward. A congregant pulls out their phone, opens the camera app (already on their home screen), points it at the QR code, and taps the notification. Their browser opens a donation page. They pick a fund if the church offers multiple ones, enter an amount, and pay. Stripe handles the transaction. They don't create a user profile. They don't download anything. By the time they've put their phone back in their pocket, the donation has hit your bank account and our system has already begun the Gift Aid process.

Why QR codes beat every other method

I spent the first year of building Givr listening to treasurers explain what actually happens with online giving links. They email a PayPal link to the congregation. Half of it bounces because it goes to spam. Someone posts it on the church noticeboard. A member clicks it from their phone, gets redirected somewhere confusing, and gives up. A summer team member prints the URL as a QR code, but it's pixelated and people can't scan it.

QR codes cut through all that. Print one on paper. Project one on a screen. Text it to the church WhatsApp group. Email it. Engrave it on a stone plaque in the vestibule. It doesn't matter. The code is the same. It always works. And because it's a standard technology, people already know how to use it. No learning curve.

From our end, the QR code is just a URL. When someone scans it, we know which fund they're giving to, which service they were at (if you've set that up), and what the donation was for. That metadata becomes crucial later, when we're claiming Gift Aid and need to submit donation records to HMRC.

The Gift Aid claim that happens while you sleep

Here's where QR-code giving becomes genuinely different from a card reader or a paper envelope. Every donation through Givr triggers an automated Gift Aid declaration capture. If the donor is a UK taxpayer, they tick a box saying so. If they're eligible (which most regular givers are), we record that declaration instantly.

That's the setup. The real work happens on the back end. Givr tracks every eligible donation. When you're ready (or when you choose to automate it), we compile your donation records and submit them directly to HMRC via Charities Online. No spreadsheets. No accountant fees for Gift Aid processing. No waiting three months for a response.

I'm not exaggerating when I say this is the reason we built the product. There's £560 million in Gift Aid going unclaimed by UK churches every year. Most of that isn't lost because churches don't want the money. It's lost because the admin is overwhelming. A treasurer collects donations throughout the year, tries to match them to donor records, fills out a form, submits it late, and then forgets about it when the next crisis hits.

QR-code giving creates a record automatically. Every transaction is timestamped, linked to a Gift Aid declaration, and ready to submit. A church using Givr's Gather tier doesn't think about Gift Aid again. We claim it for you.

Getting started is genuinely simple

I want to be honest about what 'simple' means in practice, because church finances can be complicated. Your treasurer needs a bank account. Givr connects via Stripe Connect Express, which is FCA-authorised and doesn't require you to hold an FCA licence yourself. You answer a few questions (church name, postcode, how much you're planning to process), and within a few minutes, you're connected to Stripe and the integration is live.

Then you create your QR code. You can add multiple funds if you want (one for the general offering, one for the building repair project, one for the food bank). You download or print the code. You put it somewhere people will see it. That's it.

The first time someone scans it, they land on a page that asks for their name, email, donation amount, and whether they're a UK taxpayer. If they are, they declare Gift Aid in one tap. The donation goes through. You see it in your Givr dashboard immediately. A week or two later, when you've batched a few donations together, you submit them to HMRC and the Gift Aid claim begins. HMRC sends the money back to your bank account.

The whole experience is designed around the idea that treasurers already have a hundred things to do. We try to eliminate as many of those as possible.

What actually happens in that dashboard

Once donations start coming in, you get a live view of who's given what, which funds they've chosen, and whether they've made a Gift Aid declaration. You can see trends (are Sundays busier than weekday services? are people opting for recurring giving?). You can export the data if you need to share it with your finance committee. Everything is encrypted and secured through Stripe's infrastructure.

If someone donates anonymously, that's fine. Givr doesn't force you to collect data you don't need. But most regular givers will give you their name and email, which means you have a connection point for a thank you, a prayer request, or a story about where the money went.

The dashboard is also where you see Gift Aid claims in progress. You can see which donations are eligible, which declarations have been captured, and which ones are pending submission to HMRC. It's not a black box. You're never wondering what's happening with your Gift Aid.