PayPal for Churches vs Tap.Giving: 5-Year Cost Compared (2026)

The Short Answer in Dollars

PayPal is a payment processor with no monthly subscription. Tap.Giving is a hardware company with no monthly subscription. They overlap in zero places. The choice most churches think they are making in their church giving technology stack, PayPal or Tap.Giving, is actually two choices: which processor handles the money, and what physical experience lives on the seat backs during the offering.

If your church already takes online donations through PayPal, you are paying fees per transaction. The current published rate for enrolled US nonprofits on the PayPal Donate product is 1.99% plus $0.49 per donation. A 200-seat church averaging $3,000 a month in online giving (the rough midpoint for that size in 2026) pays about $84 a month in PayPal fees. Five years of that is $5,050.

NFC tap plates do not change that processing cost. They change where the giving happens. Lifeway research and our own customer data point the same direction: when people are willing to give but the in-service path is awkward, you lose them. Going from about 24% giving in-service to about 81% with NFC tap plates is the line item that actually moves the budget, and the plates that capture it are a one-time $800 buy for that same 200-seat room.

What PayPal Actually Does for a Church

PayPal sells two things a church might use: a PayPal Donate button (a direct merchant account for the church) and PayPal Giving Fund (a 501(c)(3) charity that collects on behalf of enrolled nonprofits and grants the money in batches). For most churches the Donate button is the practical choice because the money lands in the church account directly, not as a batched grant 15 to 45 days later.

The PayPal Donate URL looks like paypal.com/donate?hosted_button_id=YOUR_ID. That URL is mobile friendly and works in any phone browser. It is also the exact kind of URL that can be encoded onto an NFC chip, which is where Tap.Giving comes in.

What Tap.Giving Actually Does for a Church

Tap.Giving is hardware, not software, and not a processor. Each NFC tap plate is a 4-inch printed disc with a passive NFC chip that holds one URL. The plate mounts to a pew back, a chair back, or a connect-card pocket. When a member holds a phone within an inch or two, the phone reads the URL and offers to open it in the browser. The browser is whatever the phone already uses. The URL points to the church's existing giving page (a PayPal Donate link, a Tithely page, a Pushpay page, anything). The donation runs through the processor that already serves the church, and the money lands where it already lands.

Because the plate is just a URL, tap to give and tap to donate work with anything. PayPal, Tithely, Pushpay, Subsplash, Donorbox, Givelify, Anedot, Planning Center Giving, Nucleus Giving, a custom Stripe checkout, all of it. We do not need to integrate, the church does not have to switch processors, and the plate cannot be locked to a single vendor.

The point of NFC tap plates is the moment of the offering. A first-time NFC giver completes the donation in about 8 seconds, no app, no signup, no QR scan, no URL to type. The same chip standard powers Apple Pay and Google Pay, so any phone that taps to pay at a coffee shop can tap a plate. Tap technology for churches is the same NFC stack consumers already use at the grocery store, which is why no setup or app is required on the giver side. Our how-it-works page walks through the giver experience step by step.

The 5-Year Cost Table, Side by Side

Numbers below assume a 200-seat US church that processes about $3,000 a month online (a typical figure for that size by 2026), with an average gift of $60 and about 50 online transactions a month. Rates are public, the math is plain.

The extra $800 over 5 years is $160 a year, less than $14 a month, to give every seat a tap to give path. Even a small lift in giving (one extra $50 gift per Sunday across the year) pays the plates back many times over. Our ROI breakdown runs the same math at multiple church sizes.

Compared to a Tithely subscription ($99 a month for the full Pro tier, see Tithely pricing 2026) or Pushpay (typically $1,475 a month for a 200-seat church, see Pushpay vs Tap.Giving), PayPal is by far the cheapest processor by sticker price. The dollars saved by skipping a SaaS subscription are real. But those dollars only matter if the in-service path is good enough to actually capture giving, which is what the plates do.

Feature Comparison: PayPal vs Tap.Giving

A row-by-row look at what each one actually does. The shorthand: PayPal is in the green column for processing, Tap.Giving is in the green column for the in-service experience, and most churches are best served using both.

When PayPal Alone Is the Right Call

We sell plates, but plates are not the answer for every situation. Be honest about a few cases where PayPal as the only digital giving setup makes sense.

• Pop-up congregations, house churches, or short-term plants. If the church does not have permanent seating to mount to, the plates do not have a home. Use the PayPal Donate URL in a printed flyer for now, revisit when there are pews or chairs.
• Online-only ministries. If 100% of giving is online and 0% is in-service, the PayPal page is the whole experience. Tap plates are designed for the room.
• Under 50 seats. Our minimum order is 100 plates. Below that, you are better off with a single PayPal QR sign at the back wall and revisiting plates when the congregation grows.
• Pre-launch, no giving URL yet. Set up the PayPal page first, get one real donation, confirm the URL is mobile friendly, then call us. The plates encode whatever URL you point them at, get the URL right before printing 200 of them.

For everyone else (a permanent room with seats, a real Sunday service, members who use phones), tap plates plus your existing PayPal account is the combo that turns a fine processor into a great giving experience.

How to Use PayPal and Tap Plates Together

The setup is simpler than most church tech projects. Five steps, no integration work, no API keys, no migration.

That is the whole project. No integration, no migration. The plates work the day they arrive, and they will keep working in 5 years when the next staff turnover happens and someone tries to remember what to do with them. There is nothing to remember, the chip stores a URL.

FAQ