A one-off donation form and a regular-giving system are different jobs. A form handles a stranger giving once. A tithing system handles the same forty households giving every month for years — and that creates work a form never sees: cards expire and commitments quietly stop; amounts change; a member wants their gift split between the general offering and the building fund; and in January, every one of them wants a statement.
Those four problems — the expiring card, the changing gift, the designated split, the January statement — are the next four sections of this page.
If you are mainly looking for one-time online giving and event ticketing, start with our church donation software instead.
Members give once or set up support that renews automatically. It runs on card or on ACH bank draft — and a monthly bank draft is how a large share of committed givers actually tithe — with automatic payments set up by the member or by church staff.
The member manages it themselves in their own portal: update a card, switch to ACH, change the amount, pause or cancel — without emailing the office. The church secretary stops being the change-of-card desk. And every time a recurring gift processes, the giver is thanked automatically.
An expired card is a giving commitment that quietly stops — and nobody notices for four months. Here, declined recurring gifts are retried automatically, and a failed-recurring-payment report shows the office exactly which commitments need a human touch.
A gift can be directed to a specific fund, program or campaign, with a managed fund list behind the scenes. You name the funds your church actually uses — general offering, building fund, missions, benevolence, whatever the budget calls them — and the giver picks one when they give. A tithe and a designated offering are both gifts carrying a fund designation; the naming is yours.
Reporting follows: campaign performance reporting is built in, and the custom report builder lets the office build reports on its own fields and filters and re-run them. And for benevolence gifts especially, givers can choose to keep a gift private on receipts and public records.
When your church runs an annual commitment drive, the commitment is recorded: pledge commitments are tracked, and members see and manage their recurring pledges from their own portal. When a pledge comes due, an automation can act on it — an email or a text goes out without anyone in the office keeping a spreadsheet of who to chase.
The product documentation names church narthexes by name as a setting its in-person tools were built for — the one place in the entire feature set where a church setting is called out directly.
Card readers for the lobby or the welcome desk
Tap to Phone — a volunteer’s own phone becomes the giving device, with no hardware to buy
A self-serve kiosk with preset amount buttons
Offline batch capture — gifts still process when the building’s Wi-Fi drops, and settle when it reconnects
The point underneath all of it: online, in-person and kiosk giving land in one ledger and one reconciliation. The envelope table and the website are not two sets of books.
And for the member who left the envelope at home: publish a keyword and short code and they text to give, with the gift and their record captured automatically. How the whole texting side works — carrier registration, consent, reminders — is on our Text-to-Give page.
Every completed gift triggers an instant receipt automatically, and receipts carry the required "no goods or services were provided" IRS disclosure language — the compliance line a church treasurer checks for first. Annual giving summaries generate in bulk. Members can also pull their own complete giving history and statements from their portal any time, which collapses the "can you resend my receipt?" pile.
Households group members together for accurate giving totals and cleaner outreach. And because church rolls accumulate the same family three times over the years, duplicate records can be found and merged with a full audit trail. (One note so nothing surprises you in a demo: the platform labels these records "donors.")
January stops being a volunteer’s lost Saturday: summaries run in bulk, and members serve themselves.
The ready-made library of 30+ built-in reports covers what a church board asks for: recurring donors, donor retention, donation summary — and LYBUNT and SYBUNT, which in plain English means who gave last year and hasn’t yet this year. Any saved report can be scheduled and emailed automatically, so the monthly board number arrives without anyone opening the system.
For whoever keeps the books: a built-in general ledger view, transaction batches that reconcile against the actual deposits, and sync with QuickBooks Online, QuickBooks Desktop and Xero — because that is where most church books live. The full feature list has the rest.
Recurring donors, donor retention, donation summary, LYBUNT and SYBUNT.
General ledger view and transaction batches that reconcile against the actual deposits.
Sync with QuickBooks Online, QuickBooks Desktop and Xero.
$0 per month, 0% platform fee, everything included — and no charge that scales with the size of your membership roll. Adding every household on the roll costs nothing, so there is no reason to keep anyone out of the system.
How the company earns, in one sentence: Cloud Donor Manager is built by Host Merchant Services, a payment processor, and processing is quoted to your organization based on your actual giving volume and average gift size rather than set by a software vendor’s price sheet. Givers can also opt in, with one checkbox, to cover the processing cost so the full intended gift reaches the ministry. The published numbers are on the pricing page.
A multi-campus church sees each campus and the whole church: branch-level scoping with org-wide rollups. Staff are added with granular role-based permissions scoped by branch — the nursery coordinator does not see giving records — and sign-off can be required on large gifts, refunds and sensitive record changes, with a reviewable queue, supporting the internal controls your church already has.
Guided CSV import with automatic field mapping, managed migration batches, and an import history — your giving history comes across, not retyped. And if the first import looks wrong, there is an undo: you can back it out.