Taking Donations: Payment Acceptance for Nonprofits

A donation form looks like a checkout page and behaves nothing like one. There's no order to fulfil, so the usual risk model doesn't apply. There's a receipting obligation on every gift. Funds given for a purpose can't be spent on another one. And donation forms attract a fraud pattern that retail sites mostly don't see, because a page accepting any amount from anyone with no account is exactly what someone testing stolen card numbers is looking for. Most of what goes wrong here is specific to the category and preventable in configuration.

How donations differ

	Retail	Donation
Amount	Set by price	Chosen by the payer
Goods to deliver	Yes	None
Account required	Frequently	Rarely
Obligation on receipt	Deliver the goods	Acknowledge, and honour any designation
A dispute means	A lost sale	An upset supporter
Recurring	A subscription	A gift nobody thinks about

Rows one to three together describe the fraud problem, and row five describes why the response has to be different — a nonprofit can't treat a disputing donor as a loss to be written off.

And row two removes the exposure that per our processor review guide drives most merchant monitoring. There's nothing undelivered, which is genuinely favourable — but it also means the usual reassurance a nonprofit could offer a reviewing processor doesn't apply.

Card testing on donation forms

The category-specific fraud pattern, and it catches organizations unprepared.

Someone with a list of stolen card numbers needs to find which ones work. A donation form is ideal: any amount, no account, no address, no relationship.

What it looks like:

• Many small transactions in a short period.
• High decline rates alongside them.
• Unusual amounts — small, and sometimes identical.
• No donor detail, or obviously fabricated detail.
• Activity at unusual hours, and from unexpected places.

What it costs you:

• Processing fees on every attempt, including declines in some arrangements.
• Disputes on the ones that succeed.
• A processor review, per our processor review guide — this pattern looks exactly like what monitoring is built to catch.
• Staff time and the work of explaining it.

What reduces it:

• Rate limiting by address and by session.
• A minimum gift amount, which removes the economics of testing.
• A challenge on the form, which costs some legitimate donors and is usually worth it.
• Address verification where available.
• Alerting on decline rate rather than only on volume — the decline rate spikes first and is the earliest signal available.
• Blocking repeated attempts from the same source.

Recurring gifts that vanish

The largest quiet revenue loss in nonprofit payments.

Per our stored card analysis, stored cards decay — they expire, get reissued after fraud, or are replaced — and the charge simply stops working.

Why it's worse for donations than for subscriptions:

• The donor isn't using a service, so nothing prompts them to notice.
• Recurring gifts are set up once and forgotten, deliberately.
• The lifetime value is long, so each loss is large.
• Nobody decided to stop — the donor still supports you.

What to do:

1. Enable card updating with your processor, which resolves a large share automatically.
2. Use tokenization where the scheme supports it, which survives reissue.
3. Reach out before expiry, not after failure — per our stored card analysis, asking before a failure recovers far more than any attempt afterwards.
4. Offer bank payment as an alternative, per our bank payments guide — it doesn't expire, which for a long-lived recurring gift is a substantial advantage.
5. Retry soft failures sensibly, per our failed payment guide, and never retry hard declines.
6. Report on lapsed recurring gifts as a standing item — most organizations don't have this number.

Item four is underused and fits the use case unusually well. A donor committing to a monthly gift for years is exactly the case where a non-expiring instrument beats a card.

Disputes from supporters

Where the nonprofit context changes the response entirely.

A disputing donor is a supporter who didn't recognize something, usually rather than someone claiming fraud.

Per our descriptor guide, the common causes:

• An unrecognizable descriptor — a legal name rather than the name donors know.
• A recurring gift they forgot setting up.
• An annual gift, where twelve months is long enough to forget.
• A family member's gift on a shared card.

What to do:

• Use the name donors actually know in the descriptor, with a contact number.
• Confirm every gift immediately, including recurring ones.
• Notify before each recurring charge, or at least before an annual one.
• Make cancelling easy and obvious — per our subscription guide, a donor who can't find how to cancel disputes instead, which costs more and ends the relationship badly.
• Refund rather than contest where a donor is confused, per our refunds guide — the relationship is worth more than the gift.
• Watch the dispute rate, since per our processor review guide it drives reviews.

Restricted funds

The obligation that has to be captured in the payment rather than reconstructed afterwards.

Funds given for a stated purpose generally can't be spent on something else. Which makes the record of what each gift was for an obligation rather than a reporting nicety.

What that requires:

• Capture designation as structured data at the point of giving — a field, not free text.
• Carry it through to accounting automatically, per our bookkeeping guide.
• Handle campaign-specific pages so the designation follows the source.
• Deal with partial designations and with gifts that arrive without one.
• Report the restricted balance, which is money you hold and can't freely use — the same structure as the customer deposits in our deposits guide.
• Reconcile restricted receipts against restricted spending regularly.

Reconstructing designations afterwards is unreliable exactly when it matters — a campaign that raised a lot, where the question is later asked, is the case where free-text and correspondence-based records fail.

Handling and reporting of restricted funds is an accounting and legal question that varies. Get your accountant's and counsel's view on the requirements before designing the form, since the form determines what you can report.

Receipting

An obligation attached to the transaction, which makes it a payments question.

• Automate it from the payment event, so nothing depends on someone remembering.
• Include what's required — a question for your accountant, since requirements are specific and vary.
• Handle recurring gifts, which may need periodic or annual summaries.
• Handle the fee-cover option, where the amount charged differs from the gift.
• Handle refunds and disputes, which may require correcting a receipt already issued.
• Keep the records, per our records guide.
• Reconcile receipts issued against gifts received as a control — a gap means someone didn't get one.

The fourth is the one that produces errors where fee-covering is offered. The gift and the charge are different numbers and the receipt has to reflect the right one — which depends on the requirements and is worth confirming rather than assuming.

Fees and whether to ask

The design question most organizations face and few test.

Many nonprofits offer donors the option to cover processing costs, and a substantial share accept. What to consider:

• Present it as an option rather than pre-ticked. Per our defaults analysis, a pre-selection is a decision made for the donor — and with supporters that's a relationship question as much as a compliance one.
• Be honest in the framing about what the fee is.
• Check what your processor agreement and jurisdiction permit, per our surcharging guide — the rules are specific.
• Test it rather than assuming, since effects on average gift and completion vary.
• Consider bank payment for large gifts, where the fee difference is material.

And per our fees guide, check whether you qualify for nonprofit rates, which many processors offer and many organizations never ask about. That's a conversation worth having annually.

Reconciling gross

The accounting detail that causes persistent discrepancies.

Processors frequently deduct fees before depositing, so the bank shows net while the gift was gross. An organization reconciling from the bank statement records the wrong gift amounts and loses the fee as an expense line entirely.

What to do:

1. Reconcile from the processor's transaction report, not from the deposit.
2. Record gifts gross and fees as an expense.
3. Match deposits to batches, per our reconciliation guide.
4. Account for refunds and disputes separately.
5. Check the timing, since batches and deposits cross period ends.

Recording gross matters beyond accuracy. Donors and funders ask what proportion of income goes to costs — and an organization that has never recorded processing fees as an expense cannot answer a question it will definitely be asked.

Frequently asked questions

---

This guide is educational and does not constitute legal, tax, or accounting advice. Requirements for donation acknowledgement and substantiation, the treatment and reporting of restricted funds, charitable solicitation registration, and the permissibility of passing processing costs to donors vary by jurisdiction and by circumstance. Consult a qualified attorney and an accountant experienced with nonprofit organizations.