When a donor disputes a gift, build the evidence packet first

When a nonprofit donation chargeback arrives, do three things before responding: read the stated reason and deadline, stop any separate refund action, and build one evidence packet around the cardholder’s actual claim. Then choose one path—accept, contact the donor, or challenge—based on what your records support.

More files do not make a stronger response. Relevant records do.

Treat the notice as a case with a clock

A chargeback is an issuer-led payment reversal. The cardholder disputes the transaction with their bank, the nonprofit receives a notice through its processor or fundraising platform, and the issuing bank decides the outcome after reviewing the response. Visa describes that sequence, including the merchant’s opportunity to submit supporting evidence.

Open a case row as soon as the notice arrives. Record:

• dispute ID, donation ID, donor or contact ID, amount, and transaction date;
• the exact reason category or code;
• response deadline and the time zone shown in the notice;
• current refund, dispute, and payout status;
• one owner and one backup owner.

The processor notice controls the deadline and submission method. Do not copy a deadline from another platform. GoFundMe Pro, for example, currently gives some customers five days to respond, while another processor may show a different window.

Freeze separate money movement while you investigate. On Stripe, a disputed charge cannot be refunded until the issuer decides in the nonprofit’s favor. Other systems may behave differently, so check the open case before anyone attempts a refund outside the dispute flow.

Build a reason-specific evidence packet

Start with the claim, not with every document you can find. Stripe groups network reason codes into categories such as fraudulent, duplicate, and canceled recurring payments because each category calls for different evidence.

Use one working folder with six sections:

1. Case header: dispute ID, reason, deadline, owner, and the action under review.
2. Transaction record: processor transaction ID, amount, date, payment method, statement descriptor, and any available verification results.
3. Donation context: form or campaign name, selected fund, recurring terms when relevant, and the contact information submitted with the gift.
4. Donor communication: receipt, confirmation message, prior questions, cancellation or refund requests, and your replies.
5. Claim-specific proof: the record that directly answers the reason. For a duplicate claim, compare both transactions. For a canceled recurring claim, show the schedule and cancellation timeline. For an event payment, include ticket delivery or check-in only when the dispute concerns that event.
6. Money timeline: payout status, any prior refund or credit, and the current disputed amount.

Stripe’s evidence guidance lists background records such as customer details, payment IP, receipts, communications, and the description presented at payment. Use only records that exist and address the claim. Do not create a statement after the fact and present it as something the donor saw before paying.

Keep the packet short. Stripe currently allows only one response and says the submission cannot be amended after it is sent, so assemble and review the evidence before submitting. Your processor may use different fields, but the same editorial rule holds: one clear timeline beats a folder of unexplained screenshots.

Choose one of three responses

Accept the dispute when your records support the cardholder’s claim, the payment appears genuinely unauthorized, or the organization lacks evidence that addresses the stated reason. Stripe’s current fraud guidance says to accept rather than challenge when you believe the payment was fraudulent.

Contact the donor when the charge may be unrecognized or misunderstood. HCB’s current nonprofit chargeback guidance recommends a direct explanation because some donors do not recognize the statement charge. Keep the message factual: identify the date, amount, and campaign; ask whether they recognize the gift; and record the reply.

Donor contact does not pause the evidence deadline. If the donor says they will withdraw the dispute, follow your processor’s instructions and retain written confirmation. Stripe warns that a withdrawal can still resolve as a loss when the merchant submits no evidence.

Challenge only when the available records directly contradict the claim and the response is worth the staff time. Name the claim, state the contradictory fact, attach the supporting record, and stop. The issuing bank—not the nonprofit or processor—still decides the result.

Close the case into one operating change

After the decision, record the outcome beside the original gift. Keep the dispute ID, action, submitted evidence, final date, amount lost or restored, and any follow-up owner connected to the payment record.

Then fix one upstream weakness. An unrecognized charge may point to a confusing statement descriptor or receipt. A duplicate claim may expose a retry or form problem. Repeated small fraudulent gifts belong in your security review, while scattered case records are a reason to keep payments, contacts, receipts, subscriptions, and payouts in one fundraising system.