Refunds and Chargebacks on Donations: A Small Nonprofit Guide
By HeartBridge Team · · 6 min read
Key takeaways
- Refunds are initiated by your nonprofit, chargebacks are initiated by the donor’s card issuer.
- Keep a complete record of every gift, refund, and donor message.
- Fast, calm communication can sometimes prevent a dispute from escalating.
- Clear donation page language and clean donor records reduce confusion.
- Small teams should assign one person to review and one person to approve.
What should you do first when a donor asks for a refund?
If you run a small nonprofit, donation refunds chargebacks nonprofit teams deal with can feel urgent fast. The best first step is to pause, look at the original gift record, and decide whether the issue is a refund request or a card dispute.
A refund is something you initiate. A chargeback is something the donor starts through their card issuer. Those are different processes, and treating them the same can create confusion in your books and in donor communication.
Start by confirming three things: the gift amount, the date, and whether the donation was one-time or recurring. Then check whether the donor has already contacted you, because a quick reply can sometimes resolve the issue before it becomes a dispute.
How do refunds and chargebacks differ?
Use this simple comparison to keep your team aligned.
| Topic | Refund | Chargeback |
|---|---|---|
| Who starts it | Your nonprofit | The donor through their card issuer |
| Where it happens | Inside your payment workflow | Through the card network and issuer process |
| Best use case | Duplicate gift, mistaken amount, donor request | Donor disputes the charge with their bank |
| What you need | Gift record, approval, accounting entry | Documentation, timeline, and response file |
If your nonprofit uses Stripe, remember this: each nonprofit connects its own Stripe account, HeartBridge is never merchant of record, and HeartBridge adds no per-gift platform fee. Stripe's standard 2.9% + $0.30 applies to each transaction.
That matters because your records should show exactly what was processed, what was refunded, and what fees were charged by Stripe. If you want a broader primer on fee handling, see Stripe Fees Explained for Nonprofits and What Merchant of Record Means, and Why It Matters.
What records should you keep?
When a refund or chargeback happens, documentation is your best protection. Keep the original donation receipt, any email thread with the donor, the refund approval, and the accounting note showing how the gift was handled.
Also save any notes about restricted intent, event registration, or recurring giving status if those details affected the decision. Clear records help you answer questions later and keep your treasurer from rebuilding the story from memory.
- Donation date and amount
- Donor name and email
- Payment method and last four digits, if available
- Reason for refund or dispute
- Who approved the action
- Date the refund or response was sent
How should you respond to a refund request?
Respond quickly, even if you do not have the final answer yet. A short reply that confirms receipt and explains the next step can reduce frustration and may prevent a chargeback.
Keep the tone factual and calm. Do not argue about the donor's feelings, and do not promise a refund until your internal review is complete. If the gift was processed through Stripe, document the refund in the same place your team tracks other payment activity so your books stay consistent.
For small teams, it helps to assign one person to review the request and one person to approve the final action. If you are still tightening your payment workflow, our post on Setting Up a Nonprofit Bank Account and Stripe Together may help.
How can you reduce chargebacks before they happen?
You cannot prevent every dispute, but you can lower the odds. Clear donation page language, accurate receipts, and prompt donor follow-up all help.
Make sure donors can recognize the charge on their statement. If your nonprofit uses recurring giving, tell donors what to expect, including timing and frequency. If you use text-to-give, make the instructions easy to understand and consistent with your other giving channels.
It also helps to keep your CRM clean. If a donor has multiple records or old contact information, your team may miss a question that could have been resolved early. A clean donor file supports faster responses and fewer mistakes.
What does a simple refund workflow look like?
Here is a practical workflow a small nonprofit can use.
- Receive the request and log it immediately.
- Confirm the gift details and reason for the request.
- Check whether the gift was one-time, recurring, or tied to an event.
- Decide whether a refund is appropriate under your internal policy.
- Send the donor a clear update.
- Record the action in your accounting and donor systems.
If you need a place to keep donation records, recurring gifts, and donor notes together, HeartBridge includes a donor CRM with CSV import, donation forms, recurring giving, and smart emails. You can compare plans on Pricing or create an account at Register.
Do this this week
- Write a one-page refund policy for your board or finance lead to approve.
- Decide who can approve refunds and who can send donor replies.
- Review your donation receipt wording so it matches your refund process.
- Check whether your donation form clearly identifies your nonprofit on the donor statement.
- Set up a simple log for refund requests and chargeback notices.
What if a chargeback arrives anyway?
If a chargeback arrives, move quickly. Gather the original donation record, any donor communication, and proof that the gift was authorized and processed correctly.
Then respond through the channel your payment processor requires, and keep a copy of everything you submit. Even if the outcome is not in your favor, a complete file helps your team learn what to improve next time.
If you are evaluating whether your current platform gives you enough control over records and response steps, you may also want to read Donation Pro Alternative and Software4Nonprofits Alternative.
Key takeaways
- Refunds are initiated by your nonprofit, chargebacks are initiated by the donor’s card issuer.
- Keep a complete record of every gift, refund, and donor message.
- Fast, calm communication can sometimes prevent a dispute from escalating.
- Clear donation page language and clean donor records reduce confusion.
- Small teams should assign one person to review and one person to approve.
FAQ
Is a refund the same as a chargeback?
No. A refund is processed by your nonprofit. A chargeback is a dispute started by the donor through their card issuer.
Should we refund first and ask questions later?
Not usually. Review the gift details first so you understand whether the request is valid and how it should be recorded.
What if the donor says they do not recognize the charge?
Reply promptly with the date, amount, and any description that may appear on their statement. Sometimes that clears up the issue without a dispute.
Do recurring gifts need special handling?
Yes. Check whether the donor understood the timing and frequency, and confirm whether the cancellation or refund applies to one payment or multiple payments.
How should we document a refund?
Keep the original gift record, the reason for the refund, the approval, the date, and the accounting entry together in one place.
Where can I learn more about giving and payment basics?
Stripe has general payment information at stripe.com, and the IRS provides nonprofit guidance at irs.gov.
For a small nonprofit, the goal is not to eliminate every refund or dispute. The goal is to handle each one quickly, consistently, and with a paper trail you can trust.
Sources: Stripe, IRS guidance, and nonprofit sector resources can help you build a clearer process. See stripe.com, irs.gov, councilofnonprofits.org, and candid.org.
Frequently asked questions
Sources
Stripe · IRS · Council of Nonprofits · Candid
Start free on HeartBridge
No credit card required. Run your fundraising on your own Stripe account, with AI built in.
Start free on HeartBridge