Tools, Hosting and Giving
Online Giving for Church Websites
Set up online giving that members trust: one clear page, fees explained, recurring gifts, receipt records, and links that survive a platform change.

An online giving page is the most visited transaction a church website hosts, and the one where trust matters most: a member types bank details into a page wearing the church's name. This guide covers what belongs on that page, how fees and recurring gifts should be explained, what receipts need to survive tax season, and why the giving link must outlive any provider. The IRS publishes the charitable contribution rules that govern American deductions and acknowledgments, and the practical points below stay close to them.
The design question comes first and stays first: the page should feel like the offertory plate, quiet and dignified, not like a checkout funnel counting down a discount timer.
What belongs on the giving page itself?
Four things, in plain view. What the gift funds, in the congregation's own words, without euphemism. The amounts and options, one time and recurring, with the recurring gift described as the member controls it, cancelable at any time, from a page the member can find without emailing the office. The fees, stated honestly: the processing cost of each channel, so a member choosing bank transfer over card saves the church its percentage. And the receipt promise: what the giver receives, when, and from whom. Anything else on the page, campaign thermometers, suggested amounts, testimonials, earns its place only if it answers a question a giver actually has.
How should fees be explained?
Every electronic gift costs someone a percentage: the card networks, the processor, the platform bundling the processor. Churches handle this three ways: absorb the fee, ask the giver to cover it as an optional checkbox, or list it in the finance report. The page's duty is honesty about which. "Cover the processing fee" checkboxes that default to checked have begun to draw regulatory attention, and a church should want no part of pre selected extras in any case. The home page checklist puts the giving link in the header precisely so no donor has to hunt for these answers.
What makes a recurring gift work?
Recurring giving smooths the congregation's cash flow the way salary smooths a household's, and it asks for a design discipline in return: the member must see, change and cancel the gift without calling anyone. A giver who has to email the office to stop a gift learns something about the church that no committee wants taught. The page should say where the member manages their own schedule, and the office should treat the cancellation path as a feature, not a leak.
What do receipts need to say?
American taxpayers who itemize deduct charitable contributions, and the acknowledgment rules are specific: the church states whether any goods or services were provided in exchange, describes them if so, and arrives in time to file. Electronic acknowledgments satisfy the rule when they carry the required statements. The practical guidance: the giving page tells givers what receipt to expect and when, and the finance team sends one summary per giver per year rather than an email per gift, a habit that also reduces the mail members quietly filter out. The IRS charitable contribution pages hold the current wording; the church's treasurer should read them once a year, in January, with last year's receipts beside.
What about text to give and app based giving?
Text to give and platform apps lower friction for members already comfortable with them, and each adds a channel the office must reconcile. The rule of thumb from the platform decisions in the CMS guide applies: every channel added is a channel that must be explained on the page, reconciled in the books, and mourned when the provider sunsets it. A church serving an older membership gets more from a clean web page and a mailed check reminder than from a channel nobody under seventy uses.
Why must the link outlive the provider?
Churches change giving processors when fees shift, features lag or the platform folds, and every change strands the old habits: the bookmarked provider page, the app on members' phones, the text keyword on the refrigerator magnet. The durable pattern: members give through the church's own address, the giving page on the church site, which embeds or links whatever provider serves today. The address on the bulletin, the slide and the newsletter never changes; behind it, the office swaps processors without a single re teaching. This is the same stability discipline the streaming guide applies to the watch link.
How does the page treat the hesitant giver?
Some members will not give electronically, from conviction or caution, and the page should say plainly how else to give: the plate, the mail, the office hours. A page that treats the check as an embarrassment has misread its congregation. The wording habits belong to the writing guide: plain sentences, no pressure language, the theology of giving stated once and gently rather than repeated in every button.
Where does a team start on Monday?
Open the current giving page and answer, as a stranger would, four questions: what funds this, what does it cost the church, how do I stop it, and what receipt do I get. Any question without a clear answer on the page is the Monday's work. Then check where the link lives: header and footer, one stable address on the church domain, described in the tools section as part of the wider stack. The finance team reads the IRS acknowledgment rules once, in January, and the page stays honest for the year.