Opening a church merchant account through 2Accept gives your ministry giving that clears on the first attempt, settles into the church's own bank account, and never freezes during a year-end surge — by underwriting your congregation under MCC 8661 with nonprofit interchange, card-testing defense on your public giving page, and fund-level settlement reporting, instead of pooling your tithes inside an aggregator account that can hold funds the week you need them most. Our church merchant accounts include recurring tithing, ACH bank draft, text-to-give, giving kiosks, capital-campaign pledges, and multi-campus sub-MIDs under a single underwriting relationship.
The process of opening a church merchant account with 2Accept takes four steps. First, complete the online application with your EIN, Articles of Incorporation or church charter, a board resolution naming the authorized signer, last three months of bank statements, and either your 501(c)(3) determination letter or a statement of automatic exemption under IRC 508(c)(1)(A). Second, a dedicated nonprofit underwriter reviews your giving methods, average gift size, campus count, and fund structure within one business hour. Third, you receive your MID and connect it to Planning Center Giving, Pushpay, Tithe.ly, Subsplash, Breeze, or your own giving page after signing the merchant processing agreement. Fourth, you go live in 48 hours with account updater, card-testing rules, descriptor control, and fund-level settlement reporting already switched on.
Rates for a church merchant account on 2Accept start at 2.89% for card giving, because religious organizations underwrite at the low high-risk tier and qualify for reduced nonprofit interchange under MCC 8661. ACH bank draft prices at a flat per-gift fee rather than a percentage, which is why a $2,000 tithe costs a congregation cents instead of dollars. Pricing depends on monthly giving volume, average gift size, the card-to-ACH mix, campus count, and whether your donors cover the processing cost at checkout.
Church finance teams evaluate a payment processor on giving methods supported, nonprofit interchange qualification, recurring-gift retention, ChMS and giving-platform fit, fund-level reporting, and how the account behaves when December giving spikes. 2Accept's nonprofit desk covers each dimension below and underwrites the giving methods, ministry models, and compliance configurations listed here.
2Accept underwrites every channel a congregation actually gives through — online giving pages, recurring tithe schedules, text-to-give short codes, QR codes printed in the bulletin, lobby giving kiosks, in-app giving, and card-present terminals at events and conferences. Each channel maps to MCC 8661 (religious organizations), so the account qualifies for reduced nonprofit interchange rather than standard retail rates.
Congregations range from a single church plant collecting a few dozen gifts a week to multi-campus ministries processing capital-campaign pledges across several states. 2Accept underwrites at any size, with the MID structure matched to campus count and fund complexity.
Apply for a Giving Methods MID →Ministry models span the single-site congregation (one EIN, one bank account, one giving page), the multi-campus church (several campuses reporting into one general fund), the church-plant network (separate entities under a sponsoring body), and the parachurch ministry (missions agencies, camps, broadcast ministries, and schools operating alongside a congregation).
Each model changes the MID structure. A single site runs one account; a multi-campus church runs sub-MIDs so each campus settles and reconciles separately while the finance office sees one consolidated report.
Apply for a Ministry Model MID →Church underwriting turns on entity documentation rather than product legality. Churches are automatically exempt under IRC 508(c)(1)(A) and are not required to apply for a determination letter, so many congregations hold none — 2Accept accepts a church charter, bylaws, and a board resolution in its place instead of stalling the file.
Underwriting also confirms that the settlement bank account sits in the legal entity's name, that the authorized signer is named by the board, and that designated-fund gifts are tracked so restricted giving stays restricted.
Apply for a Compliance MID →Recurring giving carries a congregation between Sundays, so the account protects it directly. Tokenized card-on-file holds the donor's card, account updater refreshes expired and reissued cards automatically, and failed-gift retry logic re-presents a declined tithe instead of silently dropping the donor off the schedule.
ACH bank draft prices at a flat per-gift fee, donor-covered fees let givers add the processing cost at checkout, and settlement reporting breaks each batch down by fund so the general, missions, building, and benevolence lines reconcile without hand-sorting.
Apply for a Transaction Features MID →2Accept connects to the giving stacks churches already run — Planning Center Giving, Pushpay, Tithe.ly, Subsplash, Breeze, Realm, and Ministry Platform — through hosted checkout, REST API, or a gateway-level placement that leaves your donor experience untouched.
Accounting integrations push settled batches into QuickBooks, Aplos, and Shelby Financials with fund codes attached, so the treasurer reconciles the deposit to the fund ledger instead of rebuilding it from a CSV export.
Apply for an Integrations MID →An open giving page is the internet's preferred card-testing target, because it takes any amount, ships nothing, and asks for no address. Fraud rings run stolen card lists against it in bursts, and the resulting decline ratio — not the gifts themselves — is what triggers network monitoring and gets a giving page shut off. 2Accept tunes velocity, IP, and device rules on your specific form, adds an invisible challenge to the giving flow, and sets a minimum gift threshold that kills $1 probe traffic.
Descriptor control puts your church's name on the donor's statement rather than a platform's, which removes the most common source of "I don't recognise this charge" disputes, and Ethoca and Verifi alerts let the finance office refund a confused donor before a chargeback ever posts.
Apply for a Dispute Defense MID →Every high risk merchant account is priced by risk tier. Your vertical, volume, and chargeback ratio determine which tier underwrites you. Churches and ministries underwrite at the low tier and qualify for reduced nonprofit interchange under MCC 8661. Rates are average and may vary depending on individual circumstances and risk profile. Interchange may be passed to merchants for more challenging approvals.
Complete the 4-minute application. No credit pull, no application fee, no long-term contract.
A 2Accept nonprofit underwriter reviews your giving methods, volume, and entity documents within 1 business hour.
Sign your MPA, receive your MID, and connect it to Planning Center, Pushpay, Tithe.ly, or your own giving page.
Grow with account updater, card-testing rules, fund-level reporting, and headroom for December giving spikes.
Connect your merchant account to the storefront, POS, accounting, and CRM software you already run.
2Accept enables smooth payment operations across Shopify stores.
2Accept connects with Clover POS for seamless point-of-sale transactions.
2Accept syncs payments with QuickBooks to simplify accounting and reconciliation.
2Accept supports BigCommerce to facilitate online payment processing.
2Accept integrates with Authorize.net for secure transactions.
2Accept connects with Salesforce to streamline customer relationship management.
2Accept extends payment capabilities to WooCommerce-powered online stores.
Aggregators do accept churches — as sub-merchants inside a pooled master account, priced at a blended flat rate and monitored by an automated risk model. A dedicated MID from 2Accept belongs to your church alone, prices at interchange, and is watched by a person who knows why your giving triples on December 31.
| Feature | 2Accept | Stripe | Square | PayPal |
|---|---|---|---|---|
| Dedicated MID in the church's legal name | ✓ | ✕ | ✕ | ✕ |
| Nonprofit interchange pass-through (MCC 8661) | ✓ | ✕ | ✕ | ✕ |
| Fund-level settlement reporting | ✓ | ✕ | ✕ | ✕ |
| Year-end & Christmas spikes without a funding hold | ✓ | ✕ | ✕ | ✕ |
| Card-testing rules tuned by a human risk analyst | ✓ | ✕ | ✕ | ✕ |
| Named underwriter and support contact | ✓ | ✕ | ✕ | ✕ |
| Multi-campus sub-MIDs with per-campus settlement | ✓ | ✕ | ✕ | ✕ |
Every 2Accept church merchant account includes the monitoring and mitigation stack that keeps a public giving form from becoming a card-testing target — and keeps disputes under Visa's 1.0% threshold.
Ethoca and Verifi CDRN integrations catch disputes before they post, letting your finance office refund a confused donor pre-chargeback and protect the ratio.
Velocity, IP, and device rules plus a minimum gift threshold block BIN-attack bursts against your giving form before they wreck your decline ratio.
3D Secure shifts liability to the issuer on authenticated gifts, eliminating fraud-based chargebacks on compliant giving checkouts.
Our dispute team files evidence packages — gift receipt, donor login, and recurring-schedule history — against "not recognised" disputes, recovering funds within 45 days.
Expired and reissued cards refresh automatically, so recurring tithes keep clearing instead of dropping donors off the schedule without anyone noticing.
Your church's name appears on the donor's statement instead of a platform's, cutting "I don't recognise this charge" disputes by 40%+.
"Our giving page got hit with a card-testing attack in October and our processor shut us off two weeks before year-end. 2Accept had us on our own MID in two days with rules tuned to our form."
"We had no determination letter because we never needed one. Everyone else stopped the file there. 2Accept took our charter and a board resolution and moved on."
"Moving recurring giving to bank draft and turning on account updater changed our monthly numbers more than any campaign we ran."
A church merchant account is a payment-processing account that an acquiring bank issues directly to a congregation, ministry, or parachurch organization under MCC 8661, designed to handle recurring tithing, ACH bank draft, text-to-give, capital-campaign pledges, designated-fund tracking, and the seasonal giving spikes and card-testing exposure that aggregator platforms respond to by holding funds or closing the giving page.
The account accepts card-present and card-not-present gifts across online giving pages, lobby kiosks, mobile apps, text short codes, and event terminals, and it operates under nonprofit underwriting terms that include reduced MCC 8661 interchange, account updater on recurring schedules, church-name billing descriptors, card-testing rules tuned to your specific form, fund-level settlement reporting, and discount rates starting at 2.89%.
A church earns an elevated-risk classification for structural reasons rather than moral ones. A public giving form accepts any amount, ships no product, and requires no address, which makes it the preferred target for fraud rings validating stolen card numbers — and it is the resulting decline ratio, not the giving, that trips network monitoring. Giving is also violently seasonal, with Christmas Eve and the final week of December carrying a disproportionate share of annual receipts, and an automated risk model reads a 20× spike as fraud. Because a gift delivers no product, there is no shipment record to win a dispute with. Acquirers weigh whether your entity documents are in order, whether your descriptor names the church, whether your giving form is defended, and whether your fund structure keeps restricted gifts restricted.
Opening a church merchant account differs from opening a standard retail account in three ways. First, underwriting reviews your church charter, bylaws, board resolution, and either a determination letter or automatic exemption under IRC 508(c)(1)(A), rather than approving instantly against a product catalogue. Second, pricing sits at the low high-risk tier with nonprofit interchange, because a congregation carries almost no delivery risk even though it carries real fraud exposure. Third, the account issues a dedicated MID in the church's legal name, so a December surge settles instead of being held and a card-testing burst is tuned out instead of switching the giving page off.
2Accept underwrites church merchant accounts for single-site congregations, multi-campus churches, church plants and planting networks, missions agencies, camps and conference ministries, broadcast and online ministries, and faith-based schools across the United States. Applications are reviewed by a dedicated nonprofit underwriter within one business hour and approved in 48 hours depending on documentation, then connected to Planning Center Giving, Pushpay, Tithe.ly, Subsplash, Breeze, or your own giving page after signing the merchant processing agreement.
Acquiring banks segment faith-based organizations by entity structure, giving mix, and campus count. The ministries 2Accept underwrites most often are:
A dedicated church merchant account gives a congregation advantages no aggregator plan can match, because the account is underwritten by an acquiring bank that prices religious organizations correctly and watches the giving page personally:
Qualifying for a church merchant account requires meeting documentation and entity requirements that the acquiring bank reviews during underwriting. Standard qualification criteria include:
Keeping a church merchant account healthy long-term requires active stewardship of the giving page, because card-testing rings probe open forms continuously, recurring schedules decay as cards expire, and Visa's VDMP threshold (0.9%) and Mastercard's ECM threshold (1.5%) trigger fines above either limit. The strategies that protect a church MID are:
No. There is no long-term contract and no early-termination penalty — accounts are month-to-month once approved.
Your EIN and incorporation documents, church charter or bylaws, a board resolution naming the authorized signer, three months of bank statements, and government-issued ID for that signer.
Yes. Churches are automatically exempt under IRC 508(c)(1)(A) and are not required to hold a determination letter. We accept your charter, bylaws, and board resolution in its place.
Not in the way a business owner does. The board resolution names an authorized signer acting for the entity, and clergy personal guarantees are reviewed case by case rather than required by default.
Yes — that is one of the most common reasons churches come to us. A card-testing shutdown does not disqualify you; bring the context and we will place you on a dedicated MID.
Yes. New congregations are approved on a charter, a board resolution, and a bank statement in place of processing history.
Through a gateway-level placement behind Planning Center Giving, Pushpay, Tithe.ly, Subsplash, or Breeze, or via REST API and hosted checkout on your own giving page. Most churches are connected the same day credentials are issued.
No. The application and the underwriting review are free.
Religious organizations underwrite at the low high-risk tier, typically from 2.89% + $0.20 on card giving, with reduced nonprofit interchange under MCC 8661 quoted before you commit.
ACH prices at a flat fee per gift rather than a percentage, so the saving grows with gift size. A large recurring tithe is the clearest case for moving a donor to bank draft.
Interchange is the fee the card networks pay to issuers, and the networks publish reduced rates for qualifying charitable and religious organizations. An account boarded under MCC 8661 can qualify; a blended flat rate never passes that reduction through to you.
Yes. A checkout opt-in lets a giver add the processing cost to their gift, and most congregations find a majority of donors accept it.
No. Gateway, reserve, and per-transaction terms are disclosed in your merchant processing agreement up front — nothing is added silently.
Funding is typically next-day to 48 hours depending on the acquirer and your reserve schedule.
Usually not. A congregation delivers no product, so delivery risk is minimal and most church accounts board with no reserve or a nominal one.
Some acquirers set a small monthly minimum; it is disclosed before you sign and is waived on higher-volume accounts.
Not the ministry. A public giving form takes any amount, ships nothing, and asks for no address, which makes it a card-testing target; giving is extremely seasonal; and a gift produces no delivery record to defend a dispute with.
Yes. Each campus can run a sub-MID that settles and reconciles separately while the finance office reads one consolidated report.
Yes, though tuition and giving are usually boarded as separate MIDs under one master relationship so the reporting and the ratios stay clean.
Yes. Sending agencies, camps, recovery and benevolence ministries, and broadcast ministries are underwritten on the same nonprofit terms.
Yes. Pledges bill on scheduled installments, and the account reconciles pledge commitments against payments received.
Yes — Clover, PAX, and Verifone hardware is available for lobby kiosks and event terminals alongside your online MID, at card-present rates.
Yes. Settlement reporting breaks each batch down by fund, so general, missions, building, and benevolence giving reconciles without hand-sorting.
Yes. A master underwriting relationship can carry per-parish or per-congregation sub-MIDs with centralized reporting.
Approximately 98% of complete, compliant applications are approved. The most common cause of delay on a church file is a missing board resolution.
The initial review is a soft, no-credit-pull underwriting check. Because the applicant is an entity rather than an individual, personal credit carries far less weight than it does on a commercial file.
Most complete applications are reviewed within one business hour, with go-live inside 48 hours.
Yes. Church plants and newly incorporated ministries are approved on entity documents and bank statements.
Most commonly a settlement account that is not in the church's legal name, a missing board resolution, or a giving page with no published refund and contact policy.
Clean entity documents, a board resolution naming the signer, a settlement account in the entity name, and a giving page with visible policies and a named contact.
MATCH-listed entities are considered case by case. Bring the context and we will tell you honestly whether we can place you and on what terms.
You receive the specific reason and, where possible, a path to re-apply — on church files this is almost always a document gap that closes quickly.
Because it accepts any amount, ships no product, and requires no address, an open giving form is the cheapest way for a fraud ring to check whether a stolen card number still works.
Set a minimum gift amount, enable an invisible challenge on the form, and let us tune velocity, IP, and device rules to your specific giving page. Together these remove the economics of probing your form.
Yes — and this surprises most finance teams. It is the decline ratio that trips network monitoring, so a burst of failed probes is more dangerous to the MID than the handful that succeed.
Almost always because the billing descriptor shows a giving platform's name rather than the church's. Setting the descriptor to the name donors know removes most of these disputes.
Yes. Our dispute team files the gift receipt, donor login record, and recurring-schedule history as an evidence package, and most resolve within 45 days.
Sustained ratios above roughly 0.9% (Visa) risk monitoring programs. Church ratios are typically far below that, so we watch the decline ratio more closely than the dispute ratio.
Ethoca and Verifi notify you the moment a donor disputes, so the finance office can refund inside the window before it ever becomes a chargeback.
A refund is the church returning a gift voluntarily; a chargeback is the issuer reversing it on the donor's dispute — and only the chargeback counts against your ratio.
Stripe and Square accept churches as sub-merchants in a pooled account at a blended flat rate, watched by an automated model. 2Accept issues a dedicated MID in your church's name, prices at nonprofit interchange, and assigns a person who knows why your giving triples on December 31.
PayPal holds funds aggressively on volume spikes and shows its own name in the donor experience. A dedicated MID keeps the funds and the donor relationship under the church's control.
No. In most cases we place a new MID behind the giving platform you already use, so the donor experience and your staff workflow do not change.
No. A giving platform is software that collects the gift; a merchant account is the bank relationship that settles it. Most platforms resell an aggregator underneath — this replaces that layer with your own MID.
Giving companies sell software and resell processing. We are the acquiring side: nonprofit interchange, underwriting, risk tuning, and settlement — running behind whichever giving software you prefer.
In most cases yes — a new MID can be placed behind your existing gateway with minimal reintegration.
Yes. Multi-MID cascading load-balances volume across accounts and fails over automatically, which matters most during a year-end appeal.
Honestly, sometimes not. If annual giving is small and entirely card-based, a flat-rate platform may cost less to administer. The saving becomes real once recurring giving, large tithes, or ACH volume enter the picture — we will tell you which side of that line you are on.
Talk to an underwriter who knows what 508(c)(1)(A) means and why your giving triples in December. The review is free, there's no application fee, and you'll have an answer fast.
Start Your ApplicationChurches rarely process only tithes. A congregation adds a preschool that bills tuition, a bookstore and café that ring up card-present sales, a camp that collects registrations, and a missions arm that sends funds overseas — each of which underwrites differently from Sunday giving. 2Accept approves these adjacent categories under the same acquiring relationships, so one ministry can hold several MIDs without restarting underwriting for each entity.
If your ministry operates across multiple entities — say, the congregation itself, a separately incorporated preschool, and a 501(c)(3) missions arm — 2Accept can structure separate MIDs for each entity under one master underwriting relationship. Each MID settles to its own account and is monitored independently, so a card-testing burst against the public giving page never threatens the school's tuition processing.
Apply now and let's build your business — without hesitation.
SPEAK TO A PAYMENT EXPERT