Online giving is no longer a nice-to-have for churches. For most congregations in 2026, it is the dominant channel — the plate is the supplement, not the source. This guide covers what online giving actually is, how to think about fees, the difference between recurring and one-time gifts, why your giving platform should not live outside your church management software, and the questions to ask any provider.
What “online giving” actually means
Online giving is the set of digital channels through which your members and donors contribute — web giving pages, in-app giving inside your member portal, text-to-give, and recurring scheduled gifts. It typically supports both card and ACH (bank transfer), can be designated to specific funds (general, missions, building), and produces year-end statements automatically.
Recurring vs. one-time
Recurring gifts are the most important number in your generosity report. Why? They smooth cash flow, they reduce the dependence on Sunday attendance, and they free pastors from the trap of preaching to the budget. A church with 60% of its base giving recurring is structurally healthier than one with 20% — even if the totals are the same.
One-time gifts still matter: they are the entry point for most new donors and the engine for special campaigns. The right platform makes both easy and lets recurring gifts be set up in two taps.
ACH vs. card
This is the single biggest cost question in online giving. Card processing fees typically run 2.2–2.9% plus a per-transaction cent fee. ACH is dramatically cheaper — often a flat $0.25 to 1% with a low cap. For a $500 monthly recurring gift, ACH can save the church $100–$170 a year.
Practical advice: make ACH the default for recurring gifts and frame it correctly. Donors don’t avoid ACH because they prefer card — they avoid it because the form makes it sound scary. A good giving experience defaults to ACH for recurring with a one-line note: “Bank transfer means more of your gift reaches ministry.”
How to think about fees
You will see three layers of fees: processor fees (paid to the card network and acquirer), platform fees (paid to the giving software), and optional “cover the fee” surcharges donors can add at checkout. Get clarity from any vendor on all three. The honest version is something like: 2.2% + $0.30 per card transaction, $0.25 per ACH, no platform markup, no monthly minimum, year-end statements included.
Watch for: hidden percentage spreads layered on top of processor fees, monthly minimums that punish small churches, and “optional” donor fee coverage that defaults to on (which is a UX trick, not a feature).
Designated funds and pledges
Real giving software lets donors give to specific funds (General, Building, Missions, Benevolence) and tracks pledges — multi-month or multi-year commitments — against payments. The giving page should show a donor their own pledge progress without making them call the office.
For capital campaigns, this is non-negotiable. A campaign without a pledge module quickly becomes a spreadsheet that nobody trusts.
Donor-managed accounts
Every modern giving platform lets the donor — not the church staff — manage their own card, bank account, frequency, and amount. The benefit is twofold: fewer staff hours spent on “please update my card,” and dramatically lower failed-payment rates because donors can self-correct before a gift fails.
Year-end statements, automated
If your treasurer is hand-assembling giving statements in January, you have a software problem, not a process problem. A complete platform generates IRS-compliant statements automatically, makes them available in the donor portal year-round, and emails them in bulk on a schedule you set.
PCI — who holds the scope
This is more important than it sounds. PCI-DSS (the card industry security standard) places obligations on anyone who touches cardholder data. The right architecture: the donor enters card details into a hosted form provided by a PCI-DSS Level 1 gateway. Your church management platform receives a token, never the card number. This means your church is not in PCI scope — and your IT volunteer doesn’t need to read 250 pages of regulation.
If a vendor stores card numbers in their own database, walk away.
Why your giving platform should not live outside your ChMS
You can absolutely run a standalone giving processor and import the data nightly into your member database. Many churches do. But every seam between two systems is a place data drift hides:
- The donor exists twice and their address gets out of sync.
- The deposit amount the bank shows doesn’t match either system.
- A refund happens in the giving tool and never makes it to the books.
- Statements include or exclude things based on which system “won” in last night’s sync.
An integrated platform — one database for people, gifts, pledges, and statements — eliminates the seam by removing the second system. The treasurer’s month-end goes from a weekend to an afternoon.
Mobile giving in 2026
Most online giving in 2026 happens on a phone — often during or right after a service. This means the giving page must load in under two seconds on a slow connection, support Apple Pay and Google Pay (which dramatically lift completion rates), and remember the donor without a second login. If your giving link redirects to a 2014-era hosted form that asks for a CAPTCHA, you are losing gifts.
Text-to-give
Text-to-give still has a place — for guests, for events, for “respond now” moments. But it should not be the default channel for regular givers. Treat it as a doorway into recurring giving, not a destination.
The right vendor questions
- Are you the processor or a re-seller? What gateway sits underneath?
- What is the all-in fee for ACH, card, and Apple/Google Pay?
- Do you store card numbers, or only tokens?
- Can donors manage their own recurring gifts?
- Are year-end statements included and IRS-compliant?
- How do refunds and chargebacks flow into our accounting?
- Can a single donor split a single gift across multiple funds?
- Is pledge tracking included?
- Where does the data live, and how do we export it?
- What happens to recurring gifts if we change platforms?
The bottom line
Online giving is generosity infrastructure. Treat it like infrastructure: cheap to operate, transparent in cost, integrated with everything else, and invisible to the donor. Get this right, and your stewardship conversation gets to be about discipleship instead of payment processing.