Online giving sits in an awkward spot for many churches: leadership knows it matters, nobody owns setting it up, and the whole topic feels vaguely commercial. So let us make it plain. This is a stewardship question, not a tech one, and it can be handled with the same integrity as the offering plate.
Why this deserves an hour of leadership attention
Giving follows habit and convenience. Fewer people carry cash or checks every year, families travel, students move away but stay connected, and members get sick for a season. Online giving is not about pressure; it is about not putting an obstacle between a willing giver and their own church. That is the entire case, and it is enough.
Choosing a platform without drowning in comparisons
There are many good church giving platforms (names like Tithe.ly, Givelify, Pushpay, and several others serve thousands of congregations), and for a small to mid-size church the differences matter less than the fundamentals. Evaluate any candidate on five plain questions:
- Fees, fully understood. Commonly a per-gift processing fee (cards usually cost more than bank transfers) and sometimes a monthly fee. Ask for the effective cost on a $100 gift by card and by bank transfer, and whether donors can cover the fee. Numbers change, so read the current pricing page, not a blog's summary, including ours.
- Recurring giving. The single most valuable feature. Faithful people love to set generosity on a schedule; make sure it is easy.
- Where the money lands and how fast. Straight to the church bank account, on a clear schedule, with statements your treasurer can reconcile.
- Year-end statements. Automatic giving statements save your volunteers real January pain.
- Who controls the account. Set it up under a church email, not a personal one, with at least two trusted people having access. Churches lose access to giving accounts the same way they lose Facebook pages: one departed volunteer at a time.
Putting giving on your website the right way
Your website's job is trust and clarity; the platform's job is processing. In practice:
- A Give link in the main menu, visible on every page. Guests should never hunt for it, and members on a Tuesday should reach it in one tap.
- A short giving page, not just a button. Two or three warm sentences on why generosity matters at your church, then every real way to give: online (the platform link or embed), in person, by mail with the address, by app if you use one. Plain instructions honor older members especially.
- One honest line for guests: if you are our guest, the service is our gift to you; giving is for those who call this church home. That single sentence defuses the suspicion many first-time visitors quietly carry.
- Working links, tested twice a year. A broken Give button fails silently and costs real generosity. Put it on the same checklist as your contact form; the full list is in the church website checklist.
What to say from the platform, and what not to
Keep the page free of guilt and urgency mechanics. No countdowns, no manufactured pressure, nothing you would be uncomfortable reading aloud in the service. Churches sometimes borrow fundraising tactics from the nonprofit marketing world that read as manipulative in a congregation. Plain invitation, clear instructions, genuine thanks. That tone is not just right; over time it is also what sustains giving, because it sustains trust.
The upkeep nobody assigns
Giving details change: banks, platforms, fees, the treasurer's email. Assign the giving page an owner the same way you assign the offering count. When we build sites, giving details go live only after the church confirms them in writing, and anything pending shows an honest coming soon rather than a guess; wrong giving information is the most expensive kind of typo. What belongs on the page and how to word it is covered further in what to write on every page.
If your church has been putting this off because nobody owns the tech, that is a solvable problem, and it is exactly the kind of thing we set up as part of every build and care plan: platform connected, page written in your voice, links tested, and kept current after launch.