Skip to content

How Should a Small Business Respond to a Chargeback?

A chargeback happens when a customer asks their card company to reverse a payment, and the money is pulled back from your account while the dispute is decided. You win by having proof ready: the signed agreement, proof the work was done, the customer’s approval, and your messages. Respond inside your processor’s deadline with clear, organized evidence, and try to settle it with the customer directly when that makes sense.

Federal law gives card users the right to dispute billing errors. The Federal Trade Commission (FTC) explains that a customer generally has 60 days after the first bill with the error to send a dispute to their card issuer. For complaints about the quality of goods or services, the customer is expected to try to work it out with the seller first.

When a dispute is filed, your payment processor tells you. The amount is usually pulled from your account, often with a fee. You get a short window to send evidence. The card company then decides. Each processor and card network sets its own deadlines and fees, so check yours.

Your response procedure covers two things: saving evidence on every job before there’s any dispute, and responding quickly when one arrives.

Made-up example: A homeowner disputes a $1,800 charge from Summit Gutter Co., saying the work was never done. Summit’s office pulls the signed estimate, before and after photos with dates, the homeowner’s “looks great” text, and the paid invoice. They upload it all to the processor within 3 days with a one-page summary. The card company sides with Summit.

  • You lose the money while it’s being decided, sometimes for weeks, plus a fee.
  • Missing the deadline usually means you lose, even if you did everything right.
  • Too many chargebacks can cost you your processor. Processors watch dispute rates closely.
  • No paperwork means no case. Your word against the customer’s rarely wins.

Every business that accepts credit or debit cards. Businesses that do large jobs, work over the phone or online, or charge before work is done see more disputes and need stronger records.

  1. Use a clear billing name. Make sure the name on customers’ card statements matches your public business name. A name customers don’t recognize is a common cause of disputes.
  2. Save evidence on every job: signed agreement or estimate, scope of work, change orders, photos, sign-off, invoice, and messages (see 11.1.1 Service Agreement and 10.7.4 Final Payment).
  3. Put your cancellation and refund terms in writing and get the customer to accept them (see 11.1.7 Cancellation Policy and 11.1.8 Refund Policy).
  4. Turn on dispute alerts in your processor so they go to an email someone checks daily.
  5. When a dispute comes in, note the deadline right away and pick one person to own it.
  6. Contact the customer if it’s safe and makes sense. Many disputes are confusion or a problem you can fix. If you agree to a refund, follow your processor’s steps so you don’t pay twice.
  7. Build the response: a one-page summary in plain words, then the evidence in order. Match it to the reason code the processor gives you.
  8. Submit before the deadline, and save a copy of everything you sent.
  9. Record the outcome and what caused it, so you can fix the root problem.
  • The job file for every sale: agreement, approvals, photos, invoice, and messages
  • Each dispute notice, your response, and the final decision
  • A simple log of disputes by month with the reason and result

Store job files in your customer records and dispute files in your financial records folder.

  • Ignoring the notice email. Deadlines are short.
  • Sending a long angry letter. Card companies want facts in order, not feelings.
  • Refunding outside the processor and also losing the dispute. You can end up paying twice.
  • No proof of delivery or completion. Photos and sign-offs matter.
  • Billing a card for more than the customer approved, or without written approval for recurring charges.
  • Replying to the customer’s review with details of the dispute. Keep private payment matters private (see 14.6.3 Review Responses).

Your payment processor’s support team can explain reason codes and deadlines. An attorney can help with large disputes or a pattern of fraud. Questions to ask:

  • What’s my deadline to respond, and what fees apply if I lose?
  • What evidence works best for this reason code?
  • Should I treat this as fraud and report it anywhere else?

[Bill: add a short note. For example, a chargeback you or a client fought, what evidence mattered most, or how clear billing names cut down on “I don’t recognize this charge” disputes.]

  • [Date I did this:]
  • [What I actually did, step by step: dispute alerts, evidence checklist, and who handles disputes]
  • [What it cost and how long it took:]
  • [What surprised me or what I’d do differently:]
  • [Screenshot or photo to add, with private info blurred: processor dispute alert settings]
  • [Result so far:]

What is a chargeback? It’s when a customer’s card company reverses a charge after the customer disputes it. The money comes out of your account while it’s reviewed.

How long do I have to respond? Your processor sets the deadline. It’s often short, so check the notice the day it arrives.

What evidence helps most? Proof the customer agreed to the price, proof the work was done or the item was delivered, and messages showing the customer was satisfied or was offered a fix.

Can I just call the customer? Yes, if it’s safe. Many disputes end with a simple conversation. Put any agreement in writing.

LineQuestionPass looks likeFail looks likeEvidence to collect
10.7.7 ChargebacksDoes every job have the evidence needed to answer a dispute?Each job file holds the agreement, approvals, photos, invoice, and messages.Missing agreements or proof of completion.5 random job files checked against the evidence list
16.6.7 Chargeback responseAre disputes owned, answered before the deadline, and logged?Alerts go to a checked inbox. Every dispute answered on time. Log kept.Missed deadlines. No log. No owner.Dispute log, processor dispute history

Where this fits

Do this first: 10.7.6 Payment Security

Do this next: 10.7.8 Refunds

Related pages: 10.7.4 Final Payment, 10.7.5 Invoices, 11.1.1 Service Agreement, 11.1.4 Scope of Work, 11.1.7 Cancellation Policy, 17.8 Complaint Handling, 14.6.4 Negative Review Escalation

Sources

This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.

Get free updates

I'll send you a short email when new guide pages and videos go up.

No sales pitches. Unsubscribe any time.