ACH payment processing for nonprofits.

What ACH payment processing means for a nonprofit

ACH, short for Automated Clearing House, moves electronic payments between bank accounts. For a nonprofit, an ACH donation usually means the donor authorizes a withdrawal from a checking or savings account. Your organization submits the payment through its bank or provider, and the participating banks exchange the entry through the ACH Network. Nacha calls this type of authorized withdrawal a Direct Payment. [1]

That can support a one-time gift, a monthly sustainer program, or another agreed schedule. The payment method is one part of the arrangement: your donation form collects the donor’s choice, your recurring-giving system schedules future gifts, and your records connect each payment to a person and purpose.

A bank debit and an incoming bank transfer are different workflows

In an ACH debit, the nonprofit initiates a withdrawal with permission. In an ACH credit, the donor or grantmaker initiates a payment to the nonprofit. A foundation sending a grant from its treasury system may use the second approach. Online consumer donations commonly use the first. The authorization channel and account type affect how the payment is classified. [1]

Start by describing the giving experience you need. “We want supporters to authorize $40 monthly on our website” is a more useful provider brief than “We need ACH.” It identifies the channel, schedule, typical amount, and team workflow that must work together.

ACH versus cards: give each method a useful role

Consider ACH for an established monthly giving program, donors who prefer paying from their bank accounts, and larger gifts for which transaction costs deserve closer attention. Nacha’s nonprofit resources identify potentially lower processing costs as a benefit of electronic bank transfers. That is a reason to compare written terms, not proof that every ACH arrangement costs less. [2]

Cards can remain useful for donors who already prefer them, event giving, and familiar checkout experiences. A bank-payment option should earn its place through a clear experience and workable economics. Making another method harder to find can obscure whether supporters actually want to switch.

For example, a food pantry could invite existing sustainers to consider bank payments while keeping the card option on its public appeal. Track completed gifts, abandoned forms, support requests, payment failures, and net receipts for each method. Compare similar donor groups and time periods before attributing a change in giving to the payment method.

Bank accounts do not have card expiration dates, but they can close, change, or lack funds. Treat ACH as another supported giving option with its own maintenance needs.

Compare the full cost of collecting donations

Ask for every charge that applies to your proposed setup: transaction percentages, per-payment amounts, monthly charges, account validation, returns, refunds, and any separate fundraising software. Confirm what creates a billable event and whether a cap applies to the percentage component, the whole transaction charge, or neither.

Use the same donation amounts and counts on both sides. Keep returned donation principal separate from processing fees. A $100 gift that is returned and a fee charged for handling the return are different entries in your records. Our processing fees guide offers a broader cost-inventory approach.

A fictional monthly-giving comparison

Imagine an invented nonprofit receives 200 gifts of $75 each: $15,000 in a month. For this exercise, the fictional card price is 2.9% plus $0.30 per successful payment. The fictional ACH price is 0.8% per successful payment, capped at $5 per gift.

These are invented inputs, not NUMUS pricing, market averages, or an available offer. The example assumes no monthly or other charges and excludes returns, refunds, validation, and software costs. Both options receive the same 200 successful gifts. Each payment’s fee is rounded to the nearest cent before multiplying.

The $376 difference follows only from these assumptions. It is not a savings forecast or a bank-deposit reconciliation. A separate $20 monthly charge would add $20 to the relevant setup. Fixed charges matter more as a share of donations in quieter months; percentage caps may matter more for larger gifts.

Use the donation cost calculator to explore your own inputs, then add any excluded charges from the written proposals. Also assess implementation time and donor support. A smaller fee total does not answer whether the complete program works better.

Build recurring donations around clear permission

A recurring gift is an ongoing instruction to collect money. Donors should understand the amount, frequency, first payment date, and how to stop future withdrawals before they agree.

For recurring electronic transfers from a consumer account, Regulation E requires written authorization signed or similarly authenticated by the consumer, and a copy must be provided to them. Its official interpretation allows qualifying electronic records and signatures and requires clear, understandable terms. [3]

Make the permission easy to understand and retrieve

Nacha’s nonprofit authorization guide identifies the recurring amount, payment dates, cancellation instructions, account type, and banking information among the elements to address. It also explains the need to retain authorization records. Use a provider-approved process appropriate to the channel; a website enrollment and a telephone conversation have different requirements. [4]

For a hypothetical $40 monthly gift, the donor-facing experience should answer: When is the first withdrawal? Which day is used afterward? How do I change or cancel it? What name will appear on my bank statement? Staff should be able to retrieve the donor’s actual authorization and the version of the terms they accepted.

Keep the confirmation useful: donation amount, schedule, organization name, support contact, and a copy of the authorization. Avoid putting full banking details in routine email. Assign ownership for cancellations across the donation platform and any separate payment scheduler so an acknowledged request reaches the system that initiates the next debit.

Validate the account before the first online debit

Nacha requires account validation as part of a commercially reasonable fraud-detection system for WEB debits, before first use of an account number and when the donor changes it. The minimum checks whether the account is open and accepts ACH entries; it does not, by itself, establish ownership or guarantee sufficient funds. Risk may call for additional checks. [5]

Ask the provider to demonstrate validation, incomplete enrollment, account changes, and cancellation. Before changing amounts or dates, confirm applicable notice and authorization requirements. Our recurring-payment responsibilities guide helps map which tool and person owns each step.

Separate settlement, availability, and return risk

“How long does ACH take?” contains three different questions. Ask your provider to answer each for the specific donation flow.

1. Network settlement: when the banks settle the ACH entry. Nacha explains that ACH debits settle the same banking day or the next banking day after network processing. Your provider’s submission cutoff still matters. [6]
2. Availability to the nonprofit: when the provider releases a payout and when the money is usable in your account. Obtain the actual release schedule, any holding conditions, and the meaning of dashboard status labels.
3. Return exposure: whether an entry can still be returned under an applicable rule. A settled entry is not a promise that the donation can never be returned. Nacha identifies both standard and extended return rights. [7]

For example, a Friday enrollment after a provider’s cutoff may wait for a later submission. A holiday can affect the banking calendar. Even after settlement, a provider may apply its agreed release schedule. Plan an event budget from confirmed available funds rather than the total value of newly submitted donation forms.

Read the reason before deciding what happens next

An ACH return is a bank-network response explaining why an entry was returned. An incorrect amount is different from a claim that no authorization existed: Nacha distinguishes these through R11 and R10 and describes a 60-day return timeframe for these consumer authorization-related returns. [9]

Route each return to a named staff member. Record the reason, correct the donor record, and ask which next action is permitted. A refund request, cancellation, bank return, and payment retry should follow their respective procedures. Do not treat a short waiting period as eliminating all return or dispute exposure.

A practical setup plan for your nonprofit

Start with one giving program and make its full workflow dependable before expanding. A launch should leave the fundraising team and finance team looking at the same payment history.

1. Describe the program and its limits

Document expected monthly volume, gift count, typical and largest donations, seasonal spikes, and one-time versus recurring giving. Label projections as projections. Explain whether funds support unrestricted operations, a designated campaign, membership, or another purpose. These details help frame the provider’s review and your internal reporting needs.

2. Confirm the actual service arrangement

Ask your existing bank, payment provider, and fundraising-platform vendor which ACH functions they support and what requires a separate agreement. Resolve eligibility, permitted transaction types, limits, pricing, release timing, and support responsibilities in writing. Having card processing or ACH payroll does not establish that your proposed online donation collection is enabled.

3. Test the donor journey

Walk through enrollment on a phone as well as a desktop. Confirm readable authorization text, accessible labels, understandable validation instructions, and a usable cancellation route. Using approved test tools, check an incomplete bank verification, a declined or returned payment, a change of account, and a stopped recurring gift. Record the expected message and staff action for each.

4. Assign fraud monitoring and data access

Nacha’s fraud-monitoring requirements expanded to all non-consumer Originators during 2026. Covered parties must implement processes appropriate to their role to identify suspected unauthorized entries or entries authorized under false pretenses, and review those processes at least annually. Phase 2’s practical compliance date was June 22, 2026. A nonprofit initiating ACH entries should confirm its responsibilities with its provider. [10]

Translate that conversation into ownership: who watches unusual activity, who can change banking details, who investigates an alert, and who pauses suspicious processing? Use the provider’s approved collection and storage tools. Restrict access according to staff responsibilities, and keep sensitive account details out of shared planning sheets.

5. Reconcile a complete donation cycle

Connect each donation to a payment reference, donor record, campaign or restriction, fee entry, and bank deposit. Test how a later return changes those records. A platform’s gross fundraising total should not silently become the finance team’s available-cash total.

For a small pilot, compare submitted gifts, completed collections, fees, returns, and deposited amounts. Resolve exceptions before inviting the full sustainer list. Keep a brief operating guide so the program still works when the person who launched it is away.

Questions to bring to an ACH provider review

A useful proposal should connect the donor experience to costs, controls, and reporting. Bring these questions to the conversation:

• Fit: Can this arrangement support our organization, donation channels, account types, gift sizes, and recurring schedule?
• Authorization: Who supplies the enrollment language, delivers copies, retains proof, and handles changes or revocation?
• Validation: What is checked before an online debit, what does it cost, and what happens when verification is incomplete?
• Costs: Which transaction, monthly, return, refund, validation, and software charges apply? What events trigger them?
• Cash flow: What are the submission cutoffs, settlement expectations, payout schedule, limits, and possible holds?
• Operations: How do we receive return notices, reconcile deposits, stop future gifts, and reach someone who can investigate an exception?
• Portability: What records can we export if we change providers, and which authorizations or enrollments would need to be collected again?

Bring your current platform names, donation profile, and unanswered questions to request a processing-options review with NUMUS. ACH availability, pricing, eligibility, and integration requirements must be confirmed for the proposed arrangement.

Frequently asked questions

Sources and editorial notes

Primary sources checked September 24, 2026. This guide focuses on U.S. nonprofit donation collection. Examples are fictional; provider-specific services and terms require confirmation.

1. Nacha — How ACH Works. Network roles, credits, debits, and payment classifications; accessed September 24, 2026.
2. Nacha — Electronic Bank Transfers for Nonprofits. Nonprofit use cases and potential processing-cost benefits; accessed September 24, 2026.
3. CFPB — Regulation E, § 1005.10. Current regulation and official interpretation on preauthorized transfers; accessed September 24, 2026.
4. Nacha — How to Collect Donor Authorization for Direct Payment (PDF). Nonprofit toolkit authorization guidance, 2021; accessed September 24, 2026.
5. Nacha — Supplementing Fraud Detection Standards for WEB Debits. Rule effective March 19, 2021, and current FAQs; accessed September 24, 2026.
6. Nacha — ACH Settlement Timing. August 28, 2023; accessed September 24, 2026.
7. Nacha — RMAG Originator Essentials (PDF). 2024 guidance on cutoffs, returns, and classification; accessed September 24, 2026.
8. Nacha — Funds Availability Requirements for Non-Same Day Credit Entries. Effective September 18, 2026; accessed September 24, 2026.
9. Nacha — Differentiating Unauthorized Return Reasons. R10/R11 guidance; effective 2020–2021, accessed September 24, 2026.
10. Nacha — Fraud Monitoring, Phase 2. Effective June 19, 2026; practical compliance date June 22, 2026; accessed September 24, 2026.