Nonprofits, donations, and fundraising

Do nonprofits need a merchant account?

A nonprofit needs access to merchant-account functionality to accept card payments, but it does not always need to open and manage a separate traditional merchant account. Some payment providers supply that functionality through a payment-facilitator or aggregated arrangement, while other setups give the organization a dedicated merchant account.

The practical question is not simply whether an account exists somewhere in the payment flow. It is which party provides the account structure, what the nonprofit must set up, and whether the resulting donation workflow fits its channels, records, and support needs.

The short answer

A nonprofit that wants to accept credit or debit cards needs a payment service connected to the card-acceptance system. Visa describes an acquiring bank as the business-side bank that holds funds in a merchant account during the payment flow. Visa also describes payment facilitators as platforms that let businesses accept payments through a shared account with an acquiring bank instead of requiring each business to establish its own account directly.

That means a nonprofit may use either a dedicated merchant-account arrangement or a provider that bundles merchant-account functionality into its service. Stripe makes the same distinction in its current merchant-account guidance: organizations need access to the functionality, but an end-to-end provider can supply it without the organization opening a separate account on its own. For a broader definition, see what a merchant account is.

Two common ways nonprofits accept card donations

A dedicated merchant account

The nonprofit works with a merchant-services provider and receives an account structure associated with its organization and payment activity. The gateway, donation form, terminal, and reporting tools may come from the same provider or from connected services. The organization should confirm the complete arrangement rather than assuming the merchant account includes every tool it needs.

A provider-supplied arrangement

A payment facilitator, aggregator, or fundraising platform may extend payment-acceptance functionality through its own acquiring relationship. The nonprofit creates an account with that service and follows its onboarding process, but it may not open a separate traditional merchant account directly with an acquiring bank.

Both models can support legitimate donation acceptance. The labels used by providers are not always identical, so ask who holds the acquiring relationship, whose name appears in donor-facing payment details, where funds are sent, and which organization provides support. The guide to fundraising platforms and merchant accounts explains the operational distinction.

What a nonprofit should identify before choosing

Donation channels

List the places where donations will be accepted: a website, hosted donation page, events, a front desk, invoices, recurring campaigns, or mobile outreach. A setup should cover the channels actually used without forcing staff to maintain disconnected records.

Organization records

Determine which organization and authorized-contact details the provider requests. PayPal's current nonprofit setup guidance, for example, describes a business-account registration, selection of the nonprofit organization type, organization information, identity verification for the authorized user, and connection of the nonprofit's bank account. Requirements vary by provider.

Fund movement

Ask where completed donations appear, which bank account receives transfers, how each deposit is identified, and how adjustments are represented. The account used to accept and route electronic payments is not the same thing as the nonprofit's ordinary operating bank account.

Reporting needs

Confirm that reports separate gross donations, adjustments, refunds, and net transfers in a way the organization can reconcile. Also decide which donor details belong in the fundraising or donor-management system and which payment details should remain with the payment provider.

A simple decision path

  • Start with the fundraising workflow. Document the donation channels, recurring-gift needs, event activity, and reporting handoffs before comparing account structures.
  • Ask whether a separate account is required. Have each provider state whether it supplies merchant-account functionality, uses a sponsored or shared structure, or expects the nonprofit to establish a dedicated account.
  • Map the full toolset. Confirm how the donation form, gateway, card-present equipment, recurring-payment tools, donor records, reporting, and bank transfers work together.
  • Use exact provider documents. Review the current agreement and setup instructions for the particular service. Do not assume one provider's account model, terminology, or process applies to another.
  • Confirm operations before launch. Test a non-sensitive demonstration workflow, staff access, receipts, reports, and reconciliation using the provider's approved test method.

Nonprofits comparing the larger mix can also review which payment methods a nonprofit should offer and the broader nonprofit fundraising FAQ.

What the account choice does not establish

Using a dedicated account does not by itself prove that every donation tool, device, software connection, or fundraising workflow will work with it. Likewise, using a bundled provider does not mean every feature is included or that the same onboarding and fund-transfer process applies to every nonprofit. Verify the exact service, organization type, channels, and configuration.

The account model also does not determine how an organization should describe contributions, issue donor acknowledgments, classify restricted funds, or handle tax and legal questions. Those subjects depend on the organization's circumstances and qualified professional guidance. This page is limited to the payment-acceptance structure.

For a general card-acceptance comparison, read whether a merchant account is needed to accept credit cards.

Keep the evaluation privacy-safe

A nonprofit can compare providers using its public organization name, donation channels, approximate operational needs, authorized business contacts, and high-level reporting requirements. Use the provider's verified onboarding system for any identity or banking information it legitimately requires.

Do not place cardholder data, complete account numbers, security codes, passwords, bank credentials, donor payment details, identity documents, or secret API keys in a general contact form, email, or chat. Never use a real donor's card to demonstrate a workflow outside the provider's documented production process. Keep staff permissions limited to the duties each person performs.

Map the donation-payment setup

Bring a list of donation channels, recurring-gift needs, bank-transfer expectations, reporting fields, and staff roles to a payment-provider discussion. Ask the provider to identify the account structure and every component needed from donation entry through reconciliation.

Discuss a nonprofit payment workflow

Share business contact details and a high-level workflow only. Do not send cardholder data, donor payment details, passwords, bank credentials, complete account numbers, identity documents, or secret API keys.

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.

CONTACT US