Tithe.ly built its name on online giving, and it is fair to call it one of the more capable payment tools aimed at churches: recurring gifts, a giver-facing app, text-to-give, and a database wrapped around all of it so a treasurer is not reconciling two systems by hand. For a congregation that wants members to give from their phone on a Tuesday, that is real engineering, and Tithe.ly did not stumble into it.
The question a lot of small churches never quite ask out loud is simpler than a feature comparison: how much of that giving engineering do we actually use? If the honest answer is “most of our giving still comes in an envelope on Sunday,” the pricing built around payments is a cost you are carrying for a job your church is not doing yet. This is not an argument that Tithe.ly is overpriced for what it does. It is an argument that what it does and what a specific small church needs are two different questions, and worth separating before you sign up.
What Tithe.ly is actually pricing
Tithe.ly's plans are built around its payments platform first — the database, messaging, and other tools sit alongside a giving engine designed to process online and recurring gifts, take a transaction fee on each one, and hand a treasurer statements and reconciliation reports at the end of the process. That is a reasonable way to price a payments company: the product earns money on every gift it moves, and the platform features around it are part of what makes moving those gifts convenient.
The trade is that a church which does not move much giving online is still buying access to a system built for exactly that job. The database and records live inside the same product, but they were not the reason the product exists, and it shows in how the pricing is structured around transaction volume rather than a flat number per church regardless of how it gives.
The transaction fee is the part easiest to miss
A per-transaction fee on online gifts is standard across every church giving platform, not unique to Tithe.ly — card networks and processors take a cut on every payment, and someone has to absorb it. The number worth calculating before signing up is not the fee itself, it is the fee multiplied by your actual online giving volume. A church where three or four families give online each month pays a small, almost invisible amount. A church that pushes most of its congregation toward online giving pays those fees against a much larger base, and that number compounds over a year in a way a flat software subscription never does.
Neither outcome is a hidden trick. It is simply the honest arithmetic of a payments product: more volume through the system means more fees through the system, by design.
What a small church actually uses in a typical week
Most congregations of 60 to 250 people, run by a bivocational pastor and a part-time secretary or a volunteer treasurer, spend their week on a narrower set of jobs than a broad giving platform is built to serve: someone records what came in the plate, someone follows up with the visitor from two Sundays ago, someone checks whether the new volunteer's background check cleared. Our guide to the weekly church admin rhythm walks through what that week actually looks like in most small offices, and payment processing rarely shows up as the thing eating the most time.
If your church's real week matches that description, a platform priced around moving money is solving a problem you do not have most weeks, even if it solves it well.
Recording giving is not the same job as processing it
There is an honest distinction worth naming plainly: a giving system that records a gift — who gave, how much, which fund, ready for a year-end statement — is a different piece of software than one that processes the payment itself. A church that mostly collects giving by check, cash, or a bank transfer set up outside any church software does not need the processing half at all. What it needs is accurate records and a statement it can hand a giver in January. Our guide on tracking giving that respects the giver and our piece on year-end giving statements both cover what that half of the job looks like on its own, without a payment processor attached.
Paying for the processing half when your church does not use it is the specific cost this whole comparison is about.
Setup and account approval take real time
Turning on a payments module is not a checkbox — it typically means a merchant account, an approval process, bank verification, and a waiting period before your church can actually accept a card. None of that is wasted effort if your congregation wants online giving. But if the plan is to keep collecting most gifts the way you always have and add online giving “eventually,” that setup cost is one you are paying up front for a feature that sits unused in the meantime.
A church weighing this is often better served naming its actual priority first. Our guide to choosing church management software walks through listing your church's real weekly jobs before comparing any feature list, which is exactly the exercise that surfaces whether payments belong on this year's list at all.
Where a flat-rate tool changes the calculation
A tool priced as one flat monthly number, with no payments module to configure, approve, or pay a transaction fee against, is a different bet entirely — it assumes your church is not trying to move money through the software, only track people, follow-up, serving, and giving records. SundayBridge is built on that bet: $19 a month, one plan, records for giving rather than processing for it. That is not a criticism of Tithe.ly's approach so much as a different answer to a different starting question. A church that genuinely wants online giving as a working feature should expect to pay for the infrastructure that makes it work, wherever it buys that infrastructure.
If your office is currently juggling this decision alongside a pile of spreadsheets, our guide on moving off spreadsheets covers the record-keeping side of that move regardless of which giving approach you land on.
A worked example, and how to read your own numbers
Take a congregation of 120 people. Suppose fifteen households give online in a typical month, averaging a modest gift each, and the rest of the giving — the majority of it — still arrives by check or in the plate on Sunday. The transaction fees on those fifteen online gifts are small in absolute terms, and nobody would notice them on a monthly statement. What is easy to miss is the other side of the ledger: the platform price is not scaled down because most of the congregation still gives offline. The church is paying a payments-company price for a database that, for most of its giving, is doing the same job a flat-rate giving record would do for less.
Now flip the numbers. If that same church of 120 had eighty households giving online every month, the payments infrastructure would be earning its keep every single week, and the fee structure would look like a fair exchange for real convenience — no separate merchant account to manage, no second login for the treasurer, one statement covering everything. The product does not change between these two churches. What changes is how much of it gets used, and that is the number worth writing down before comparing prices.
The fastest way to answer this for your own church is not to read another comparison article — it is to pull last year's giving records and sort them by how the gift arrived. Count the gifts that came through a card or bank transfer versus the ones that came by check, cash, or mail. If online gifts are a small minority, you already have your answer: a payments platform is solving a problem most of your congregation is not handing you yet. If online giving is already the majority and growing, the calculation tips the other way, and paying for a mature payments product starts to look like the obvious choice rather than an open question.
This is also a useful moment to look at how your giving trends have moved over the past few years, since a congregation shifting steadily toward online giving is answering this question for you in real time, even if nobody in the office has said so out loud yet.
The honest answer
Tithe.ly is worth it for a church that wants online giving to work well and is willing to pay a transaction fee proportional to how much giving moves through it — that is a fair trade for real payment infrastructure. It is a harder sell for a church whose giving is still mostly plate, check, and mail, where the payments module sits mostly idle while the pricing is still built around it being the point. The way to know which church you are is to look at last year's numbers, not this year's feature list, and let that answer decide rather than the sales page.