Fighting restaurant credit card chargebacks

Why a dispute arrives three weeks after a normal dinner

Most owners first meet a chargeback as a letter or portal notice about a meal nobody remembers. The time gap is built into the system. The cardholder sees the charge only when they review a statement, and the bank then forwards the dispute through the card network to your processor, which notifies you. Under federal law, the Fair Credit Billing Act, consumers disputing a billing error on a credit card generally have to get a written dispute to the issuer within 60 days after the first statement showing the error was sent, according to the Federal Trade Commission's consumer guide Using Credit Cards and Disputing Charges. That is a consumer-side federal rule; card network rules and issuer policies can allow other dispute windows, so the practical lesson is that a restaurant has to be able to find a receipt from two or three months ago quickly.

The second reason disputes feel unwinnable is that the restaurant does not control the decision. The issuing bank reviews what you send through your processor. You are not arguing with the diner; you are handing a bank reviewer a short file that either answers the stated reason or does not. A long angry letter about a rude guest does nothing. A signed receipt that matches the charged amount does a great deal.

Sort the dispute by its reason before you gather anything

Every dispute notice includes a reason, usually as a code plus a short description. The codes differ by card network, but restaurant disputes tend to fall into four families, and each family is answered by a different kind of evidence. Treat the reason as the question you must answer. Sending general proof that the guest ate at your restaurant does not answer a claim that the amount is wrong.

The family also tells you whether to fight at all. An unrecognized-charge dispute is often cured by showing the guest that the business name on their statement belongs to the restaurant they visited. A processing error such as a duplicate charge is usually your mistake, and the fastest path is to confirm it in the POS and accept. A quality complaint about a meal that was eaten is a harder conversation, because the federal guide notes cardholders disputing quality are expected to have tried to resolve the problem with the seller first, so your record of how you responded to the complaint matters.

The evidence that must exist before the dispute does

Chargebacks are lost at the point of sale, not at the response stage. If the server did not keep the signed copy, or the POS does not record who adjusted a tip, no amount of effort later recreates it. Build the capture into closing duties so it happens on every check, not just suspicious ones.

For dine-in, the most important document is the merchant copy with the guest's handwritten tip and total, if your restaurant still uses paper tip lines, or the device record of the tip the guest selected if payment happens at the table. For pickup and delivery orders paid online, the important records are the order confirmation, the account or email used, the time the order was marked ready, who handed it over and, where your system supports it, a photo of the sealed bag with the order number visible. A commenter in an r/restaurantowners thread about missing takeout items suggested exactly that: photograph each takeout order labeled with the order number or name (Reddit discussion). That suggestion came from a forum excerpt, not a tested study, but it is a cheap record that answers one of the most common online-order disputes.

• Keep signed merchant copies or device tip records in date order, filed by business day, for at least as long as your processor says disputes can arrive.
• Turn on POS settings that log every tip adjustment, void, comp and refund with employee name and time.
• Print or store itemized receipts, not only the card slip, so a reviewer can see what was ordered.
• Save online order confirmations and any guest emails or texts about the order in the order record.
• Record the statement descriptor your processor sends, and know how it differs from your sign.

Tip adjustments: the restaurant-specific weak point

Restaurants that authorize the card before the tip is added and then adjust the amount afterward carry a dispute risk most retailers never see. If a server keys 25 instead of 15, or reads a messy 7 as a 9, the guest is charged an amount they did not approve. An amount dispute then asks a simple question: what did the guest write? If you cannot produce the signed slip, you usually cannot show the charge was correct.

Treat tip-adjust mistakes as a control problem, not only a dispute problem. Pull the POS tip-adjust report weekly and look for adjustments that exceed a set percentage of the check, adjustments made long after close, and one employee whose adjustments run consistently higher than peers. Unusual patterns are not proof of misconduct; a server may simply have bad handwriting-reading habits. But they tell a manager which slips to compare against the device total. If a mistake is found, refund the difference before the guest disputes it, and keep the refund record.

Working a real-looking case from notice to response

Hypothetical example, for illustration only: a neighborhood restaurant receives a dispute on a $142.60 dinner charge, reason family unrecognized transaction, 23 days after the meal. The manager searches the POS by date and the last four digits and finds the check: four entrees, a bottle of wine, the card read by chip, and a signed merchant copy showing a $24.00 tip written on a $118.60 subtotal. The arithmetic matches: $118.60 plus $24.00 is $142.60. The processor statement descriptor reads as the owner's holding company, not the restaurant name.

The response therefore answers the reason directly. It includes the itemized check, the chip-read transaction record, the signed slip, a one-paragraph explanation that the descriptor name belongs to the restaurant at a stated address, and the restaurant's public website page showing that address. It does not include commentary about the guest. The manager also files a request with the processor to change the descriptor to the trading name, which addresses the actual cause. A different dispute the same month, a $38.75 online pickup order claimed as never received, had no bag photo and no record of who handed it over. Without evidence that answers that reason, the manager accepts it and adds a pickup handoff step instead.

Response deadlines: find yours, then build slack

There is no single deadline a restaurant can memorize. Card networks set timelines for each stage, and your processor sets its own internal deadline for receiving your response, often shorter than the network allows so it has time to package your file. The binding number is the one in your processor's dispute notice and merchant agreement. Read that number on every notice and enter it on a calendar the day the notice arrives.

Build slack by assigning one person to check the processor portal and dispute email on a fixed schedule, with a named backup for vacations. Many lost disputes are not lost on the merits; the notice sat in an unread inbox until the window closed. If your processor mails paper notices, confirm the mailing address on file is one someone actually reads. Owners regularly look for outside help with this step; an r/restaurantowners AMA offered by a self-described payments dispute specialist drew questions from operators (AMA - Chargeback advice). Only a short search excerpt of that thread was recorded and the poster's credentials are self-reported, so none of the deadline guidance here is drawn from it; your processor's notice remains the authority.

Preventing the next dispute instead of winning this one

Each accepted or lost dispute should produce one process change. Unrecognized-charge disputes point to the descriptor and to guest-facing receipts that do not show your trading name, phone number or website. Amount disputes point to tip-adjust handling. Not-received disputes point to the pickup shelf, the handoff and the delivery-app relationship, which is covered in more detail in related guides on missing-item claims and delivery-app refund documentation.

Guest-facing friction also prevents disputes. A diner who can reach the restaurant easily is more likely to call than to call their bank. Print a phone number and email on the receipt, answer refund requests promptly, and when a manager agrees to a refund, run it while the guest is present or send written confirmation. A promised refund that never posts is one of the easiest disputes for a guest to win.

Watch for patterns that may signal card misuse rather than ordinary confusion: several large online orders on different cards to one pickup name, orders where the pickup person cannot confirm the order details, or a run of disputes tied to one channel. Report suspected fraud to your processor and follow its guidance; do not confront or detain anyone yourself.

When accepting the chargeback is the right call

Fighting every dispute costs labor and rarely changes outcomes when the evidence is thin. Accept when the dispute is correct, such as a duplicate charge or an over-adjusted tip; when the evidence that answers the stated reason does not exist; or when the amount is small and the staff time to assemble a file costs more than the charge. Accepting is not an admission of anything beyond that transaction, and it closes the item quickly.

Do fight, and fight promptly, when you hold evidence that directly answers the reason: a signed slip for an amount dispute, a chip-read and itemized receipt for an unrecognized charge, a pickup scan and photo for a not-received claim. Keep a simple log of each dispute's reason, amount, decision and outcome. After a few months the log shows which channel and which reason produce most of your losses, and that is where the next process fix belongs.

Monthly chargeback checklist for a small restaurant

This checklist is an operational routine, not a legal or network requirement. Adjust the frequency to your volume and to the deadlines your processor states.

• Daily: file signed slips or confirm device tip records saved for the business day.
• Daily: check processor portal and dispute email; calendar any deadline on arrival.
• Weekly: review tip-adjust, void and refund reports for unusual adjustments.
• Weekly: confirm takeout bag photos and pickup handoffs are being recorded.
• Per dispute: identify the reason family, gather only evidence that answers it, submit before the processor deadline.
• Monthly: review the dispute log by reason and channel; pick one process change.
• Quarterly: verify the statement descriptor, receipt contact details and the processor's mailing address on file.