How to Handle Credit Card Chargebacks at Your Restaurant

When a guest disputes a charge with their bank, the money is pulled out of your account first and questions get asked second — so the way to handle a restaurant chargeback is to respond inside the deadline (usually 7-15 days from notice) with dated proof that the guest was there and got the food: the signed or PIN-verified receipt, the itemized ticket, the delivery or pickup confirmation, and any notes from that night. Miss the deadline and you lose automatically, no matter how clearly you were right.

What a chargeback actually costs you

Owners tend to think of a chargeback as the lost ticket. It is closer to triple that, because you also gave away the food and paid a fee to be told so.

At a 30% food cost, you would need roughly $200 in new sales to earn back a single $30 chargeback. That math is why prevention beats fighting.

The three kinds you will see

True fraud — a stolen card was used at your counter. Rare in dine-in, more common on phone and online orders with big-ticket or last-minute pickup items.

Friendly fraud — the guest recognizes nothing on the statement and disputes it. This is the most common one restaurants face, and it is usually a naming problem: your statement descriptor reads like a processor code instead of your restaurant's name.

Service disputes — "the order never arrived," "we were double charged," "I never authorized the 20% auto-gratuity." These come from real operational gaps, and they are the ones you can fix permanently.

How to respond, step by step

1. Log it the day it lands. Date, amount, reason code, deadline. A dispute you find two weeks later is a dispute you have already lost.
2. Read the reason code. It tells you what evidence the bank wants. "Cardholder does not recognize" needs identity proof; "services not provided" needs fulfillment proof.
3. Pull the transaction record. Itemized ticket, timestamp, terminal ID, last four digits, chip or contactless indicator, tip adjustment, and the signature or PIN verification.
4. Add context. Loyalty account, phone number on the order, pickup or delivery confirmation, prior visits by the same card, and camera stills if you have them.
5. Write two plain paragraphs. What was sold, when, and how you know the cardholder was present. Bank reviewers skim — lead with the strongest fact.
6. Submit early and keep a copy. Note the outcome in your log either way. Patterns show up fast.

A chargeback is not a debate about who is right. It is an evidence deadline. Whoever files a clear, dated record inside the window usually wins.

Prevention that actually works

Most restaurant disputes are self-inflicted, and each one has a cheap fix.

The single highest-return change is the descriptor. A large share of "unrecognized charge" disputes simply go away when the name on the statement matches the sign on the building.

Where your POS does the heavy lifting

Everything above is a records problem, and how fast you can answer depends entirely on whether your system can hand you one transaction with its ticket, tip, timestamp, and terminal attached. A modern all-in-one system stores the itemized ticket with the payment record and lets you search by card last-four or guest name in seconds — a bank-ready packet in about two minutes instead of a night manager digging through paper. Cobblestone POS is free, folds payments, commission-free online ordering, and reporting into one system, and keeps order and payment records together, which is exactly the trail a dispute response needs. Owners running a legacy setup — separate POS, separate ordering platform, separate processor — end up reconciling three systems just to prove one $30 ticket, while also paying $470+/month to a platform like Toast for the privilege.

Keeping your own online ordering channel helps twice: you control the descriptor, the confirmation email, and the pickup record, instead of relying on a third-party app's dispute process. If a chunk of your volume runs through delivery apps, know how their liability terms differ — see our guide on using third-party delivery apps profitably.

Set a monthly 15-minute review

Once a month, count your disputes, total the real cost with the worksheet above, and sort them by cause. If more than 0.5% of your card transactions get disputed, treat it as an operations problem, not bad luck — processors start paying attention well under 1%, and excessive-dispute programs can cost you your merchant account. Pair this with your cash handling controls so both sides of the drawer are covered.

Two habits protect almost all of it: reconcile the batch before you close, and never let a dispute notice sit unopened. The window is short, the evidence is easy if your system keeps it, and every win pays for itself three times over.