The card reader we never built

The request that made sense (on the surface)

I understand the appeal. A physical card reader sat on the collection plate feels familiar. Swiping feels secure. There's a ritual to it that some treasurers find reassuring. One email came from a church in Kent that'd invested in three readers already and wanted one system to rule them all.

We looked at the numbers. Card readers add hardware cost, logistics, training, and support burden. They require NFC or Stripe-certified hardware. We'd need to stock them, handle returns, troubleshoot connectivity in 400-year-old stone chapels with patchy WiFi.

We also looked at what was actually happening in churches every week. Congregants weren't queuing at collection plates anymore. They were sat in pews with phones in their pockets. They were giving before they even sat down, or five minutes before leaving. The plate was becoming theatre.

The moment we realised simplicity was the whole point

A treasure from a Methodist chapel in Leeds gave us the clarity we needed. She wrote: 'I don't want another box. I don't want training. I just want my congregation to give without thinking about it.'

That sentence changed how we thought about the problem. We weren't in the business of selling church tech hardware. We were solving a specific UK problem: Gift Aid. Every year, an estimated £560M in Gift Aid goes unclaimed because claiming it is hard. Treasurers fill forms. HMRC takes months to respond. Many churches don't bother.

A card reader doesn't solve that. It just adds friction in a different place. It puts another device between the church and its donor. It makes the treasurer's job more complex, not simpler. It feels modern, but it moves the church further from what they actually need.

What we chose instead: a phone and a QR code

Givr works like this. A congregant scans a QR code on a wall, on a banner, or in a bulletin. The browser opens. They type an amount. They give. It takes 15 seconds. No app. No account. No card reader. No new device for the church to maintain.

We designed it for the real constraint: churches are volunteer-run. Their treasurers are often unpaid. They don't have IT support or a tech budget that stretches to hardware maintenance. They need something that works on any phone, in any browser, without training.

The Gift Aid magic happens after. Once a congregant gives, they can optionally declare their Gift Aid eligibility. Givr captures that declaration, submits it to HMRC Charities Online automatically. The church never files a manual form. The treasurer never chases HMRC follow-ups. That's where the complexity lives, and that's what we automated.

The harder conversation: saying no early

Saying no to card readers was one of the first hard decisions we made as a company. Every software founder gets customer requests. Most are good faith. The card reader requests weren't wrong. They were just orthogonal to what we were building.

The temptation was to build it anyway. Add it as a premium feature. Sell it as a differentiator. Plenty of vendors do exactly that. They build for every request, and end up with bloated products that do everything badly and nothing well.

Instead, we asked: what's the one problem that only Givr solves? Gift Aid. The 560 million pounds. The HMRC submission. The automated declaration. That's the unfair advantage. Card readers are a commodity. Any payment company sells them. We'd be competing on price and logistics, not on something that matters to UK churches.

So we stayed focused. QR code. 15 seconds. Automated Gift Aid. We built Gather tier to add recurring giving through GoCardless because churches asked for it and it integrated cleanly into the existing flow. We're building white-label and API access in Grow because some churches want custom branding and integrations with their existing systems. Those are extensions of what Givr does best, not detours.

What we learned about listening to customers

The card reader requests taught us something important. Customers don't always ask for what they need. They ask for what they think exists. Treasurers asked for card readers because other church platforms offer them. It felt like a feature they should want, so they wanted it.

Our job wasn't to build every feature customers asked for. It was to solve the problem they couldn't see yet. They knew Gift Aid was painful. They didn't always know that automated HMRC submission was possible. They didn't know that capturing gift declarations at the point of giving, and batching those submissions, would save them hours every quarter.

So we listened deeper. We asked why. We pushed back gently. We explained what we were building and why. Some treasurers switched to us. Some didn't. That's okay. You can't build a product for everyone.