How to Set Up Online Giving for Your Church: 10 Steps
Learn how to set up online giving for your church with a secure, practical 10-step plan covering providers, funds, testing, communication, and reporting.
Here is how to set up online giving for your church: choose a platform and a payment provider your church can use, configure the church's payment connection, create clear funds, and test the donor journey before sharing the link. Assign an owner for donor questions and a finance owner for reconciliation. These ten steps explain what to verify from setup through the first monthly review.
This step-by-step guide will help you launch a simple system and improve it over time. Payment rules and tax requirements vary by country. Confirm local legal, accounting, and receipt requirements with qualified advisers.
Online giving setup at a glance
A church can use this ten-step sequence:
- Define goals and ownership.
- Choose an online giving platform.
- Connect the church's payment account.
- Create clear funds.
- Configure donor options.
- Set roles and permissions.
- Build the giving page.
- Test the entire donation journey.
- Launch and explain it.
- Reconcile and improve monthly.
Do not launch until at least two people have tested the donor and administrator experiences.
1. Define the goal and the owner
Write down why the church is adding online giving. Common goals include making giving available beyond Sunday, supporting recurring contributions, reducing manual data entry, and improving fund reporting.
Assign two owners:
- A ministry or operations owner for the donor experience
- A finance owner for payouts, reconciliation, refunds, and records
This separation creates accountability. It also prevents the online giving system from becoming one person's undocumented responsibility.
2. Choose an online giving platform
Compare platforms with the same checklist. Look beyond the headline subscription price.
| Area | What to verify |
|---|---|
| Donor experience | Mobile layout, sign-in requirements or guest giving where available, recurring options |
| Payments | Supported providers, currencies, payout timing |
| Funds | Designated funds, campaigns, closing dates |
| Records | Donor history, receipts, exports, corrections |
| Security | Roles, access controls, account protection |
| Cost | Platform price, transaction fees, messaging fees |
| Support | Setup help, documentation, response channels |
TheFaithApp connects giving with church management, member records, funds, and reporting. Other churches may prefer a standalone giving provider that integrates with their existing database. Choose the model that reduces duplicate work.
3. Connect the church's payment account
Most platforms use a payment processor to collect and transfer funds. The church will normally need an account in its legal name, a verified bank account, and authorized representatives.
Prepare the information requested by the processor. This may include registration details, banking information, identity verification, and tax information. Enter these details only on the provider's secure onboarding page.
Ask these questions before connecting:
- Who owns and can recover the payment account?
- How often are payouts sent?
- Which currencies and payment methods are supported?
- How are refunds and disputes handled?
- Where can the finance team download settlement reports?
Avoid using a personal payment account for church donations.
In TheFaithApp, open Settings → Payment Providers to connect Stripe, Flutterwave, or PayPal. Use the church-owned Stripe or PayPal account, or the church receiving connection available for Flutterwave. Review provider eligibility, currencies, payment methods, and fees. Finish Stripe’s onboarding and confirm in Stripe that the church’s account can accept payments and receive payouts before sharing the giving link. See the Giving setup documentation for the current connection steps.
For eligible churches in Cameroon, follow the Fapshi setup steps to connect your church’s own account for one-time gifts through MTN Mobile Money or Orange Money. Gifts use whole XAF amounts starting at 100 XAF.
4. Create clear giving funds
Start with a short list. A general fund and a few active designated funds are easier to understand than dozens of overlapping choices.
For each fund, document:
- The public name
- A one-sentence purpose
- The internal accounting code
- The owner who approves changes
- The start and end date, if temporary
Use the same names in the giving platform and accounting system. Consistent naming makes reconciliation faster.
TheFaithApp Free includes up to 3 open giving funds for a church with up to 100 members. Standard includes up to 10 open funds and 500 members at US$39 per month. Payment-processing charges remain separate. Check the full plan limits against the funds your church actually needs.
5. Configure donor choices
Decide which options donors should see. Useful choices may include:
- One-time or recurring giving
- A fund selector
- An optional note or designation
- Donor contact details
- A fee preference, where legally allowed
- An email confirmation or receipt
Keep the form short. Only request information that the church needs and is prepared to protect.
Recurring giving can help members build a consistent rhythm. Explain that donors can review or stop a recurring contribution according to the provider's process.
Available recurring options depend on the connected account. In TheFaithApp, Flutterwave recurring giving requires approval for automated tokenized card charges, and PayPal recurring giving requires the church's partner Subscriptions capability. Confirm the option appears and works for the church before promising it in launch announcements.
6. Set roles, permissions, and controls
Giving information is sensitive. Access should follow each person's responsibility.
A healthy setup can separate these tasks:
- Platform administration
- Viewing donor records
- Reconciling payouts
- Issuing refunds
- Editing funds
- Producing reports
Use individual accounts instead of shared passwords. Enable strong account protection when available. Review access whenever a staff member or volunteer changes roles.
Create a written process for corrections and refunds. The record should show who made the change and why.
7. Build a trustworthy giving page
The page should answer four questions immediately:
- Is this the correct church?
- Is the form secure?
- What can I give toward?
- What happens after I submit?
Use the church's name and recognizable branding. Add a short stewardship statement, fund descriptions, and a support contact. Avoid guilt-based language or artificial urgency.
Make the page easy to reach from the main website navigation. Also link it from the church app and relevant campaign pages.
Supporters sign in when your church has configured sign-in. If your church has no sign-in configured and Fapshi appears on the giving page, supporters can give as guests. Open your church’s giving link while signed out and review how a supporter enters, which funds and payment methods appear, and what the payment summary shows.
If you share the giving page through QR codes, NFC tags or text keywords, use the giving-access asset checklist to check each one before it goes out.
8. Test the complete donation journey
Testing is more than loading the form. Use the provider's test environment where available. Have an authorized church owner approve any live test gift and review its fees and refund handling before proceeding. Follow the result through every stage.
Test these scenarios:
- Signed-out entry. Check the sign-in prompt or the Fapshi guest path, whichever your church’s page offers.
- One-time gift on a phone
- Recurring gift setup
- Different funds
- Confirmation email or receipt
- Donor record creation or matching
- Payment-provider record
- Payout and settlement report
- Refund or correction procedure
- Failed payment message
Check the page with a slow connection and a small screen. Ask someone outside the finance team to test it without instructions.
Do not publish bank details or sensitive screenshots while asking for help.
Rehearse the finance handoff with a fictional example
Before a payment test, ask two colleagues to review this fictional record sequence. The amounts are illustrative, not real gifts or a fee quote.
| Record | What the team checks | What it can conclude |
|---|---|---|
| A USD 20 payment attempt is pending | Check the provider result and recorded status | Keep it out of received-gift totals while it remains pending |
| The USD 20 gift is confirmed received, but its payout has not reached the bank | Retain the provider confirmation and review the payout separately | Receipt of a gift does not establish a settled bank deposit |
| A separate UGX 50,000 gift is received | Review its own currency and provider record | Keep USD and UGX totals separate; do not add them into one unconverted total |
Name who checks payment status and who reviews the deposit record. At reconciliation, compare the actual gross amount, fees, refunds or adjustments and net deposit. This is a discussion exercise; it does not establish that checkout, payment or settlement has been tested.
9. Launch with clear communication
Introduce online giving as an additional option, not the only faithful way to give. Members may still prefer cash, checks, bank transfer, or other local methods.
Use a simple launch plan:
Before launch
Train staff and ministry leaders. Prepare a short help page and decide who answers donor questions.
Launch week
Explain the purpose during announcements, email, and the church app. Share the official link. Demonstrate the process without displaying private information.
After launch
Repeat the link at relevant moments. Avoid promoting it so frequently that it overshadows worship, care, or the church's mission.
Consistent, respectful communication builds more trust than a one-time campaign.
10. Reconcile and improve every month
The finance team should match gross donations, fees, refunds, and net payouts with the accounting records. Do not record only the amount deposited in the bank. The settlement report usually provides the full breakdown.
Review a small set of measures:
- Number of online donors
- One-time and recurring gifts
- Failed recurring payments
- Fund allocation
- Refunds or disputes
- Processing costs
- Donor support requests
In TheFaithApp, received-gift totals exclude pending, failed, and cancelled payment attempts. A checkout page closing does not prove that a gift completed; confirm the provider result and recorded status. Keep currencies separate when reviewing totals.
These measures help the church find friction. They should not be used to rank people's generosity.
Common online giving mistakes
Choosing on price alone
The cheapest tool can become expensive if it creates manual reconciliation or poor donor support.
Creating too many funds
A long list confuses donors and complicates reporting. Archive completed campaigns promptly.
Giving too many people access
Limit financial permissions. Review them regularly.
Skipping real transaction tests
A form can look correct while receipts, records, or payouts are misconfigured.
Treating online giving as a fundraising trick
Digital giving should support stewardship and convenience. It should not pressure people.
Forgetting data exports
Confirm that donor and transaction information can be exported for accounting, audit, and migration needs.
Frequently asked questions
How long does it take to set up online giving?
The form may be created quickly, but payment verification and internal approval can take longer. Allow time for account verification, testing, and staff training.
What fees should a church expect?
Costs can include a platform subscription and payment-processing fees. Rates vary by provider, country, currency, and payment method. Confirm the full fee schedule before launch.
Is online giving secure?
It can be secure when the church uses reputable providers, limits access, protects administrator accounts, and follows responsible data practices. No system removes the need for good internal controls.
Should donors cover processing fees?
Some providers offer an optional fee contribution. Review local rules and present the choice clearly. Never make the wording misleading.
Can online giving support designated funds?
Many platforms support multiple funds. The church still needs clear policies for accepting, tracking, and using designated contributions.
How should recurring gifts be handled?
Explain the schedule and cancellation process. Monitor failed payments without embarrassing the donor.
Start small and build trust
Begin with a few funds, clear ownership, careful testing, and monthly reconciliation. Explore TheFaithApp Giving to review the product and plan the setup your church needs. New church-admin requests are reviewed before setup; downloading the member app does not create an administrator account.
Keep reading
Related articles
Online Giving Announcement: A Church Launch Kit
Write an online giving announcement with church email, Sunday notice, and FAQ templates, plus a practical launch checklist and donor support process.
Read articleTest your church giving QR code before you print it
Test the complete church giving journey before sharing a QR code, NFC tag, or text keyword. Check the destination, sign-in, providers, and finished assets.
Read articleChurch Donation Statements: A Year-End Preparation Checklist
Prepare church giving statements with verified received gifts, correct recipients, per-currency totals, and a clear review and correction process.
Read articleReady for the next step?
See what the free plan covers
Compare plans, understand the free tier, and choose the right setup for your church.