Handling credit card chargebacks for service work

Why chargebacks hit service companies

A chargeback is a forced refund: the customer disputes a card payment with their bank, the bank pulls the money back from your processor, and you have to prove the charge was valid to get it back. Most processors also charge a fee per dispute, and a high dispute rate can put your merchant account at risk.

Home service work invites disputes in a way retail doesn't. The product is labor in someone's house, often bought under stress, with a final price that can change during the job. Many households have thin margins for surprises: the Federal Reserve found 63% of adults would cover a $400 emergency expense completely with cash or its equivalent^[3]. A large repair bill paid on a card is exactly the kind of charge a stressed customer later questions.

How a dispute moves

1. 01

   The customer contacts their card issuer

   They describe the problem: unauthorized charge, work not done, work not as agreed, wrong amount, or a refund that never arrived.

2. 02

   The issuer reverses the charge

   The money is pulled back provisionally and a reason code is assigned.

3. 03

   Your processor notifies you

   The notice shows the reason, the amount and a response deadline. Missing the deadline usually means losing by default.

4. 04

   You respond with evidence

   Or accept the dispute. Your evidence goes to the issuer through your processor.

5. 05

   The issuer decides

   If you win, the funds return. Some disputes go another round if the customer pushes back, with a new deadline.

On the consumer side, the FTC explains that for billing errors, a customer's letter should reach the issuer within 60 days after the first bill with the error was sent, and that for problems with the quality of goods or services the customer must first have tried to resolve the dispute with the seller^[2]. Card networks have their own, longer windows for some dispute types. The practical lesson: the customer will often call you before calling the bank. That call is your best chance to settle it.

Evidence by dispute reason

Build the evidence before the dispute

You can't create good evidence after the fact. Make these part of every job, so the file is ready if a dispute ever arrives.

• Signed estimate or contract with the scope, price and cancellation terms.
• Written approval for any change, with photos and the price, before the extra work.
• Before and after photos with time stamps, attached to the job.
• Completion sign-off from the customer, on a tablet or by reply to a message.
• The invoice, matching the estimate and changes line by line.
• Payment record: card-present transaction or a payment link the customer used, with the email or phone it went to.
• Notes of every conversation about the job, including complaints and what you offered.

Call recordings can help, but follow consent law. Federal law allows recording when one party consents^[4], while some states, such as Florida, require all parties to consent^[5]. Use a clear recording notice at the start of calls if you record at all.

Responding: a five-part evidence letter

1. One-paragraph summary: who the customer is, what was purchased, the date and amount, and why the charge is valid.
2. Timeline: estimate, approval, visit dates, completion, invoice, payment, any complaint and your response.
3. Evidence matched to the reason code, each item labeled and referenced in the summary.
4. Your attempts to resolve: calls, offers to return and fix, any partial refund offered.
5. Policies the customer agreed to, with where and when they saw them.

When to refund instead of fighting

Not every dispute is worth contesting. Refund, or offer a partial refund before the customer files, when:

• You can't produce a signed approval for the disputed amount.
• The customer has a legitimate quality complaint you haven't fixed.
• The cost of building the response is more than the amount disputed.
• The customer will not be a repeat customer and a review fight would cost more.
• The dispute is really a misunderstanding that a phone call and a small concession can resolve.

Fight when you have clear evidence, the amount matters, and the claim is plainly false, such as ‘work not done’ when you have photos and a sign-off.

Prevention that costs almost nothing

• Use a statement descriptor customers recognize: your trading name and phone number, not a parent company name.
• Send a receipt immediately with the job address and a short work summary.
• Answer complaint calls the same day. A customer who reaches you rarely calls the bank.
• Prefer card-present or payment links over keying card numbers from a phone call.
• Put your cancellation and refund policy on the estimate, not only on the website.
• Never charge a card on file without telling the customer the amount first.

Deposits, financing and cancellations

Large jobs paid partly up front create a specific risk: the customer pays a deposit by card, the start date slips, and the customer disputes the deposit as ‘services not provided’. Protect deposits with paperwork that explains what the money is for and when it becomes non-refundable, within what your state allows.

• Tie the deposit to a concrete step, such as ordering custom materials, and send the order confirmation to the customer.
• Give written start-date updates whenever the schedule moves, with the reason.
• If the customer cancels, respond in writing with what was spent, what is refundable and when the refund will be issued.
• Where the sale was made in the customer's home, honor the three-day cancellation right and keep the signed notice in the file.
• For jobs paid through a finance company, keep the lender's completion certificate signed by the customer, because disputes go to the lender too.

Track disputes like callbacks

Log every dispute with the reason code, the job type, the technician, the amount, whether you won and what was missing from the file. After a few months, patterns show. Disputes on large replacements may point to unclear financing conversations; disputes on small service calls may point to a diagnostic fee that wasn't explained at booking. Fix the process at its source and the disputes drop with it. Share the patterns with technicians and CSRs without blame; most gaps are in the process, not in a person.

Example: the disputed diagnostic fee

Example: a fictional appliance repair company kept losing small disputes over diagnostic fees when customers declined the repair. The booking script mentioned the fee, but nothing was written down. The company added the fee to the booking confirmation, asked customers to accept it on the technician's tablet before diagnosis, and printed that acceptance on the invoice. Disputes for diagnostic fees became rare, and the ones that came in were won with a single screenshot.

Related reading

Most disputes are invoice disputes in disguise; start with invoices customers understand. Your evidence files also hold customer data, so read protecting customer data at a small service company for how to store them safely.