QR Codes for Church Giving

You already have a giving page. Tithe.ly, Planning Center, Pushpay, or a form on your church site. The problem is not the processor. The problem is the pew. People will not type a long URL during the offering. They will scan a square if you put one on the card they are already holding.

I want you to print a dynamic code. The card encodes a short link you own. Most Sundays that link opens general giving. Missions week it opens the missions fund. After the building campaign it goes back. Same pew card. Same bulletin footer. You never reprint because the fund changed.

Pew cards outlive a fund

A chair-back card is a print job you do not want twice. You laminate it, you drop it in a holder, and it sits there for a year. If you bake this Sunday's Tithe.ly campaign path into the pixels, the card is wrong the first time you launch a building fund.

Print a dynamic square instead. The image holds a short path. You point that path at general giving in January, at benevolence after a storm, and at the Christmas offering in December. The laminate does not care. I would rather change a URL on Saturday night than reprint two hundred cards on Sunday morning.

Put one line of type next to the square: Scan to give. People should not have to guess whether the code is Wi-Fi, a sermon archive, or the nursery map. One job per card. If you also want a connect card, that is a second square.

Slides have to read from the back row

The giving slide is a distance problem. Someone in the last pew holds a phone at chest height toward a projector that is already a little soft. A tiny code in the corner will not lock. I treat the screen like a poster: area, a quiet zone, a light background.

You can reuse the pew-card code on the slide, or create a QR code just for the screen so the dashboard tells you which placement worked. After the campaign weekend, point that slide code back at the regular give page. Do not animate the square or crop the quiet zone. A failed scan during the offering is a gift you did not receive.

Connect cards and the lobby rack

Visitors will scan a card on the welcome table if it opens a short form. Point that code at Planning Center, a Google Form, or whatever the hospitality team actually reads. When the team switches tools, edit the destination. Keep giving and connect as two codes. One question per square. The rack can hold both cards.

Seasonal funds without a new print run

Building, benevolence, missions, the Christmas offering. You already know the calendar. What you do not want is a new pew card every time the treasurer opens a fund in Pushpay. A dynamic short link shares one printed square across those seasons. Most weeks it opens general giving. For a four-week appeal you point it at that fund, then point it home on Monday.

If you need a clean report for a capital campaign, make a second code and print it only on the campaign insert. That insert can die in June. The standing pew card should never encode a campaign URL you will retire.

Create it on this site

Here is how I create QR codes for church giving that you can edit after the printer run.

1. Open the Tithe.ly, Planning Center, or Pushpay page you want people to hit this Sunday. Confirm it loads in a private tab.
2. Pick Link and paste that URL. The image encodes a short link, not the raw processor path.
3. Hit Download. Confirm the email we send. Pay $1 for the PNG so you can edit the destination later.
4. Place the PNG on the pew card, bulletin, and slide. Keep the quiet zone. Scan one proof in the sanctuary light.

When the fund changes, open the dashboard and edit the URL. Do not generate a new image unless the card design changed. That is the whole reason to print a dynamic code before you order a box of pew cards.

Size the square for the room you actually have

Your office monitor lies. Sanctuaries run warm bulbs, stained glass, and phones held one-handed over a hymnal. A 2 cm code that locked on a desk will fail on a chair-back card at dusk. Use the 10:1 rule from the QR code size guide for print: printed width should be about scan distance divided by 10, then add margin for dim light.

Black modules on white or cream stock. Skip a photo of the sanctuary behind the code. Skip gold foil on a Christmas bulletin. Leave a quiet zone. Matte laminate beats gloss under spotlights. Label it in plain type.

One code or two

A small church can run one short link on the pew card, the bulletin, and the slide, then retarget it when the fund changes. Two codes are better when you want to know which placement worked. I keep connect cards on a third code so visitor forms never mix with gifts.

What not to encode

• A personal Venmo or Cash App handle. That money is not the church's books. Point at the processor the treasurer already reconciles.
• A Facebook event or a locked sermon post. Guests who are not logged in hit a wall. Host a page you own.
• A Google Drive or Planning Center file that asks for access. Open the destination in a private tab. If you hit a login, change it before you print.
• The generator Event type. That writes a static calendar invite. Use Link so you can edit the page behind the square.
• Last year's bit.ly. If you do not own the redirect, you cannot fix it when the campaign ends.

If you want a code you can edit after the printer run, read how to create a QR code you can edit after printing. Then come back, paste this week's give URL, and print the pew card once.