Most church giving pages were never really designed. Someone on staff signed up for a giving platform, copied a snippet of code, pasted it onto a page called “Give,” and moved on to the next thing on a very long list. It works, in the sense that money can technically move from a member’s bank account to the church’s.
Whether it works well is a different question, and the answer usually shows up in small ways. A first-time visitor taps Give on their phone and lands on a page with a different logo and a web address they don’t recognize. A faithful member wants to set up a weekly gift but can’t find the option. The treasurer spends the last week of January reconciling two spreadsheets by hand so that contribution statements go out on time.
Most of those problems trace back to a handful of decisions that were made by default, or never made at all, before the form went live. Whether you’re setting up online giving for the first time or finally redoing a page that has been limping along for years, these are the seven decisions worth making on purpose before you embed anything.
One note before we start: this article is about setup choices. If your giving page already exists and you mainly want to keep it from quietly breaking, our guide to church website maintenance for events, giving, and contact forms covers testing and upkeep.
Where the form lives, and who holds the keys
The first decision is whether givers complete their gift on your church website or get sent somewhere else to do it. Nearly every giving platform offers both. You can embed a form directly on your Give page, or you can link out to a hosted giving page that lives on the platform’s own domain.
Sending people off-site is easier to set up, and for some churches it’s a reasonable choice. The trade-off is trust and momentum. When someone taps Give and suddenly finds themselves on an unfamiliar site with different colors, different fonts, and a long web address, a small number of them hesitate. Some of that hesitation is healthy caution; people have learned to be careful about where they type card numbers. On a phone, the jump can also mean a slow page load, a login prompt, or a layout that wasn’t built with your congregation in mind.
An embedded form keeps the giver on a page that looks like your church, with your name, your photos, and a short word about why giving matters to your ministry right above the form. That context does real work. It reminds people that they’re supporting a specific community, and it lets you answer common questions (Is this secure? Can I give by bank transfer? Where does the money go?) in the same place they’re deciding.
Embedding does come with a bit more responsibility. Your page has to load quickly, display properly on small screens, and use a secure connection, because the giving form now inherits whatever impression your website makes. Some features also need extra setup when the form lives on your own domain. Stripe’s documentation, for example, notes that Apple Pay works on hosted checkout pages without extra configuration, while embedded forms require the website’s domain to be registered before the button appears. Your platform will have its own version of that step, and it’s easy to miss.
A sensible default for most churches is to embed the form on a dedicated Give page and keep the platform’s hosted page as a backup link for text messages and emails. That gives you a consistent experience on the website without making every channel depend on a single page.
The second decision is less visible but matters even more: who owns the payment processor account and the logins that control it.
In a surprising number of churches, the giving account was opened by a volunteer or a former staff member using a personal email address. Sometimes the deposits even route to a bank account that was set up in a hurry and never revisited. Everything is fine until that person moves away, changes churches, or simply stops answering email, and suddenly nobody can update the bank details, issue a refund, or download last year’s records.
The fix is simple and worth doing before launch. Open the account in the church’s legal name, using the church’s tax ID and a role-based email address such as finance@ or giving@ at your church’s domain. Deposits should go to an account the church controls. At least two people, ideally a staff member and a member of your finance team or board, should have administrator access, with personal logins rather than a shared password. Write down where the account lives and who has access, and put that note somewhere your leadership can find it in five years.
This step is mostly about continuity, but it also supports good financial oversight. Many churches already require two people to count the Sunday offering; giving the online side the same kind of shared visibility is a natural extension of that habit.
What givers see when they get to the form
The third decision is how many funds or designations to offer. It’s tempting to list everything: general fund, building fund, missions, youth, benevolence, the spring retreat, the new sound system, and a memorial fund from three years ago that nobody remembers to remove.
Every option you add is one more choice a giver has to make before they can finish. A long dropdown makes people pause and wonder whether they’re picking the right one, and some of them decide to come back later. On the back end, a long fund list also means more categories for your treasurer to reconcile and more chances for gifts to land in the wrong bucket.
A good default is to keep the list to a few options, with the general fund selected automatically. Add a short-term designation for a specific campaign while it’s active, and remove it when the campaign ends. If a member needs to give to something unusual, a simple note field or a quick email to the office handles it without cluttering the form for everyone else.
The fourth decision has two parts: whether recurring giving is the easy, obvious choice, and whether you offer givers the option to cover processing fees.
Recurring gifts matter to churches for practical reasons. They smooth out the dips that come with summer travel, bad weather, and holiday weekends, and they make budgeting less of a guessing game. Yet on many giving forms, the recurring option is hidden behind a small checkbox or buried in a separate account setup flow. Members who would happily give every week end up giving once, when they remember.
Most platforms let you change how the form presents frequency. Showing one-time and recurring side by side, with weekly or monthly options clearly visible, makes it easy for a regular attender to set up a gift once and stop thinking about it. Whether you preselect recurring is a judgment call. Some churches prefer to leave one-time selected for first-time givers and invite recurring giving in the confirmation email or a follow-up. Either way, the option should be impossible to miss.
Processing fees are the other half of this decision. Card and bank payments carry fees, and many giving platforms include an optional checkbox that lets the giver add a small amount to cover them. Plenty of members appreciate the chance to make sure their full gift reaches the ministry. The key word is optional. Leave the box unchecked by default, explain it in a single plain sentence, and never make anyone feel guilty for skipping it. Pressure at the moment of giving tends to undercut the generosity you’re trying to encourage.
Giving from a phone, and making sure the records add up
The fifth decision is which mobile options to turn on. For many members, the phone is now the main way they interact with the church between Sundays, so the question is how quickly someone can give from one.
Text-to-give is the most familiar option. A giver texts an amount to a number your platform provides and receives a link to complete the gift, usually with a one-time setup the first time they use it. It’s especially handy during a service when you mention giving from the stage, or for members who don’t want to navigate a website at all. Mobile wallets like Apple Pay and Google Pay take friction out of the form itself, letting someone give with a fingerprint or face scan instead of typing a card number on a small screen.
Turning on every feature isn’t required. A reasonable default is to enable mobile wallets on the embedded form (remembering any domain registration step your platform requires) and add text-to-give if your church regularly mentions giving during services or events. Whatever you choose, test it from an actual phone, on both iPhone and Android if you can, before you announce it.
The sixth decision tends to come up in late January, when it’s much harder to fix: how online gifts flow into your church management system so year-end contribution statements are accurate.
Many churches use one system for online giving and another for member records, attendance, and in-person offerings. If those systems don’t talk to each other, someone has to match online gifts to member profiles by hand, and duplicates creep in when a giver uses a different email address online than the one on file. The result is a statement that undercounts a family’s giving, or splits it across two records.
The stakes are real. According to the IRS guidance on charitable contribution written acknowledgments, the acknowledgment required to substantiate a contribution of $250 or more must include the organization’s name, the amount of a cash contribution, and a statement about whether any goods or services were provided in return, including a statement when the only benefit was intangible religious benefits. IRS Publication 1771 explains that payments made by credit card, electronic fund transfer, or an online payment service count as monetary contributions, and that one acknowledgment, such as an annual summary, can cover several separate gifts. In other words, online gifts belong on the same year-end statement as everything else, and the statement needs to be right.
Before you launch, find out whether your giving platform integrates directly with your church management system, or whether you’ll need to export and import gifts on a schedule. Decide how online givers get matched to existing member records, who reviews unmatched gifts, and how often. Make sure your fund names are identical in both systems, which is one more reason to keep that fund list short. Your accountant or a church finance professional is the right person to confirm exactly what your statements should say; the goal on the website side is simply to make sure every online gift reaches the records cleanly.
Where the Give link lives on your site
The seventh decision is the one most churches never think about: where the Give link actually sits on your website.
On many church sites, giving is tucked under an “About” or “Connect” menu, or it only appears in the footer. Members who already know where to look will find it. Everyone else has to hunt, and a person who has to hunt for the Give button on a phone is a person who may close the tab and plan to give next week.
A clear default is to put a Give link in your main navigation, visible on both desktop and mobile, and to keep the label simple. “Give” works better than clever alternatives, because people scan menus for familiar words. It also helps to link to your Give page from the places where giving naturally comes up: the weekly announcements page, sermon pages, event pages for missions trips, and the confirmation emails you send after someone registers for something.
First-time visitors deserve a little extra thought. Most of them aren’t ready to give on their first visit, and that’s fine. What they’re usually looking for is service times, directions, and a sense of what your church is like, which is where our post on why church websites struggle to reach new visitors focuses. The Give link should be easy to find without crowding out the information a newcomer actually came for. A small, consistent link in the navigation does that well, while a large pop-up asking for a donation before someone has even seen your service times tends to push newcomers away.
On the Give page itself, a short paragraph about why your church gives and what giving supports goes a long way, along with a line about other ways to give, such as in person, by mail, or by text. Keep it short, make it feel like your church, and make the next step obvious.
A giving page worth trusting deserves a website you can count on
Once these seven decisions are made, the actual embedding is the easy part. The harder part is everything around it: a fast, secure website that renders the form properly on every device, a navigation menu that keeps the Give link visible, pages that stay current as campaigns start and end, and someone who notices when a platform update or a plugin conflict quietly breaks the form on a Saturday night.
Most church staff and volunteers have enough on their plates without also becoming the website department. That’s where a managed website service helps. With NorthMac, your church website is built, hosted, updated, secured, monitored, and supported for one monthly price. We set up pages like your Give page the right way, keep the site on current software, and handle your update requests, from swapping a campaign fund to adding a new event page, so your team can focus on ministry.
If you’re ready for your church website to be handled, you can see what’s included and start your managed website for $47.
