How to set up online giving for a small church

Choose one giving tool, verify the church bank account, test a $5 gift, then announce once on Sunday. This 175-attendance plant uses Planning Center Giving with a named first-gift thank-you owner and a Monday batch review.

By Caleb Brooks · Published September 2026· Editorial standards · Conflict of interest

Field guide page: steps and costs from hands-on church-tech work, written under a pen name. Church names stay private. See how we write and verify.

What do you need before you start?

Church bank account details, elder or finance approval in writing, and admin access to your people database. Block one weekend for the $5 test gift. Do not announce online giving until that test clears into the church account. Write the Sunday explanation script before you pick button colors on the give page.

Why did this church build this workflow?

Cash-only giving left college students and new households out. They tried two giving tools at once and split the finance report into a mess. One tool, one announcement, and a named thank-you owner fixed the launch. Guests and members use the same link. The finance team reconciles on Monday with one export, not three.

What would they do differently next time?

They would write the Sunday script before choosing colors on the give page. People needed plain words more than branding. They would also brief ushers on how to help someone give on a phone without taking the phone out of the giver’s hand, and they would add a paper card with the give URL for members who will not scan a QR code.

Launch-week checklist

1. Elder or finance approval is in writing. Deposit account confirmed by treasurer and pastor.
2. Bank verification finished. One giving tool only.
3. Give link live in website header and bulletin. Paper URL card printed.
4. $5 staff test gift clears: receipt, batch, bank pending, thank-you checklist.
5. First-gift thank-you owner named with a Wednesday due date.
6. Sunday script practiced once in staff meeting. Ushers know how to help without holding phones.
7. Monday noon: first live batch review, including fees and failed gifts.

Common mistakes

• Announcing before the test gift clears. Guests hit a broken link and do not try again.
• Running Tithely and Planning Center Giving side by side “just in case.” Finance reports split for months.
• Turning on text-to-give on day one with no weekly mention. Unused channels still need support.

Field note from a split report month

A church left an old give link live on a sidebar “just until Christmas.” Two processors meant two Monday exports and one confused treasurer. They cut the old link on a Tuesday, posted one URL everywhere, and wrote the thank-you owner’s name on the closing checklist. Giving did not rise that week. Reconciliation finally became boring, which was the real win.

Field note after a QR-only launch

They launched online giving with foyer QR codes only. Older members left cash unmarked in the plate for months. A large-type printed URL card beside the QR brought first online gifts from people who refuse phone cameras in the lobby.

Field note after a fee surprise on the board packet

The launch packet listed software only. December statements showed processing clearly. They now print fee estimates on the launch page elders approve.

Before you copy the clicks

How to set up online giving for a small church only works when a tired Monday reader can finish it without inventing owners. Read the frontmatter tools (Planning Center Giving, Planning Center People, Mailchimp) and confirm those logins already exist in an-urban-church-plant-on-the-west-coast. If a tool is missing, buy or borrow it on purpose. Do not invent a parallel Sheet “just for this week.”

Setup difficulty on this page: a-weekend. Plan about one focused weekend for first setup, plus a quieter second pass after the first real Sunday. Incremental cost range: processing fees only (often ~2–3% + per-gift fee; confirm current rates). Confirm vendor pricing the week you brief elders.

Who owns each handoff

Name a primary owner and a vacation backup before the first live run. Write those names on a card near the desk that finishes Sunday entry. Greeters, finance helpers, and volunteer coordinators should know who to ping when a step stalls.

Keep exports and pastoral notes on the tightest permissions the job allows. A workflow that moves guest or benevolence data through a shared inbox needs an explicit watch schedule, including holiday weekends.

What the week looks like when it works

• Pick one giving tool and verify the church bank account: keep the owner and timing in the detail as written; do not skip the human handoff.
• Create the public give page and a short Sunday script: keep the owner and timing in the detail as written; do not skip the human handoff.
• Turn on a first-gift tag and name the thank-you owner: keep the owner and timing in the detail as written; do not skip the human handoff.
• Test a $5 gift end to end: keep the owner and timing in the detail as written; do not skip the human handoff.
• Review fees and failed gifts every Monday: keep the owner and timing in the detail as written; do not skip the human handoff.

When the week works, nobody needs a hallway rewrite. Cards or forms land in the right list the same day. Messages leave a church-owned channel when personal phones would hide replies. Exceptions get a note, not a new secret process.

What breaks first

The first break is usually ownership, not software: a card left in a basket, an unwatched reply-to, a schedule published without a backup, or a giving test that never clears into the church account. Automations without watchers create polite silence. Dual systems create double Monday reconcile.

If your staff hours are thinner than the churchRef stack assumes, shrink the promise. Keep the moral core (a person follows through) and cut optional channels until the core is reliable for four Sundays.

Pricing and time honesty

Budget processing fees only (often ~2–3% + per-gift fee; confirm current rates) plus the weekly minutes to keep the path honest. A $0 path that burns three volunteer evenings is not free. Put hours beside fees on the board note. Train the backup on a quiet weekday before vacation season.

Re-verify this workflow when tools change owners or when the churchRef stack updates. lastVerified dates are stewardship tools. Treat an unverified page as a starting draft until someone runs the path again.

Copy-only-if checklist

1. Tools in frontmatter match logins you actually have.
2. Primary and backup owners are named in writing.
3. One full path timed end to end on a phone if foyer work is involved.
4. No second database or second inbox “for transition.”
5. Elder or staff note includes cost range processing fees only (often ~2–3% + per-gift fee; confirm current rates) and setup time one focused weekend.

Steal the promise and the ownership pattern. Adapt the branding later.

After the first four Sundays

Review what actually happened: missed steps, reply delays, and any hallway workarounds. Keep the parts people used. Cut the parts that required heroics. A workflow that only works when one specific person is healthy is not finished yet. Write the backup path before you call the process done.