A QR code for church connects your printed pew cards, bulletins and lobby signs to whatever giving, signup or feedback tool your congregation already uses. CodeQR generates dynamic codes you can repoint without reprinting, and tags each placement with its own UTM — so the office can see which sign people actually scan.
What church teams actually need from a QR code
If you handle the giving, the bulletin or the communications for a congregation, your problem is not that giving has gone digital — it is that your printed materials haven't caught up. Pew cards, offering envelopes and bulletins still go to the printer, but the giving happens on a phone. In 2023, 77% of givers used at least one digital tool to give, and faith leaders said digital giving made up 60% of annual contributions.[^1] The other hard part: if you switch or add a giving platform, every printed QR you already handed out becomes dead unless the code is dynamic.
Common use cases for churches
- Giving on the pew card and bulletin. A dynamic donation QR code sends givers to your existing platform — Tithely, Pushpay, PayPal or your own page. When you change platforms, you repoint the same code instead of reprinting every pew card.
- Event signups on the volunteer table. An event-registration QR code on the welcome desk or volunteer table lets people sign up for the retreat, the potluck or a serving slot from their phone — no paper form for someone to retype Monday morning.
- Feedback at the exit. A feedback QR code on the way out gives first-time visitors a way to leave a note or a prayer request without cornering a greeter. The responses land in the tool you already read.
Practical example
Consider a church office printing three different QR codes for the season. The giving code goes on the pew card and the bulletin; the event-signup code sits on the volunteer table; the feedback code is posted by the exit. Each one carries its own UTM tag, so the office can compare which placement the congregation scans instead of guessing. When the church moves from one giving platform to another mid-year, the treasurer repoints the giving code in CodeQR and the already-printed pew cards keep working — nothing goes back to the printer.
How CodeQR fits into your stack
CodeQR is the printed-materials layer, not a giving platform — it never touches the money. Your donations still run through Tithely, Pushpay, PayPal or your own site; CodeQR connects the code on the paper to that platform and reports the scans. It makes no tax, compliance or donor-management claims and does not manage your donor records. What it does replace is the static QR generator that forces a reprint every time a link changes, and its scan and conversion tracking shows you which placement earns the taps. Remember that congregations span generations: QR giving complements cash and check, it does not replace them.
Best practices for churches
- Size the code for the reading distance. A pew-card or bulletin code is read at arm's length, so about 2–3 cm square is enough; a lobby poster read from several feet away needs to be much larger — a rough rule is one-tenth of the scan distance.
- Expect folds and thumbprints. Bulletins get folded and pew cards get thumbed; built-in QR error correction absorbs much of that — at the highest level, H, roughly 30% of a damaged or obscured code can still be recovered[^2] — so a crease or coffee ring won't kill the scan.
- Give every placement its own UTM. The giving code on the pew card and the same code on the lobby poster should carry different tags, or you can't tell which one the congregation used.
- Keep the codes dynamic. Mobile giving is growing fast — nonprofit mobile-driven revenue grew 48% in 2025.[^3] A dynamic code lets you move to a better platform without reprinting a single bulletin. See dynamic QR codes and pricing for how the tiers compare.
[^1]: Lake Institute on Faith & Giving — https://lakeinstitute.org/resource-library/insights/june-issue1-2024/ [^2]: QR Code (Denso Wave), error-correction levels — https://www.qrcode.com/en/about/error_correction.html [^3]: M+R Benchmarks — https://mrbenchmarks.com/mobile-messaging/