What should a restaurant do when a guest disputes a no-show deposit charge?

Understand what a dispute actually is before you react

A chargeback begins when a cardholder tells their bank that a charge should not stand. The bank provisionally reverses the money, assigns a reason code, and passes the case to your processor, who notifies you and gives you a deadline to respond with evidence. For no-show deposits, the common reason codes are that the cardholder does not recognize the transaction, that the service was not provided, or that the charge was cancelled or not authorized. Each requires a slightly different response, so read the reason code carefully rather than sending a generic defense.

There is usually a fee attached to every dispute, charged to you whether or not you win, and processors watch your dispute rate as a share of transactions. A single chargeback on a modest deposit is a nuisance. A pattern of them is a signal that something in your booking flow is unclear, and at high enough rates a processor can raise fees or restrict your account. So the first reaction should not be indignation; it should be to pull the reservation record and figure out whether the guest has a point, whether you have the evidence to answer, and whether this is a one-off or a symptom. Related: How a Deposit Changes Behavior

Keep reading: Why No Shows Hurt Restaurants So Much, How a Deposit Changes Behavior, Making Deposits Guest Friendly. See how HoldTabl helps you no-show deposit collection for restaurant reservations.

Assemble the evidence the bank actually weighs

Banks reviewing a dispute want to see that the cardholder knowingly agreed to the charge and that the conditions for it were met. For a forfeited deposit, that means the policy text exactly as it appeared at booking, a timestamped record that the guest accepted it (a checkbox, a confirmation click, or a recorded phone acceptance), the confirmation message that restated the deposit terms, any reminder messages sent before the reservation, and the reservation record showing the party did not arrive or cancelled after the cutoff. If the guest contacted you at any point, include that correspondence too. Related: Which Bookings Need a Deposit

Presentation matters. Write a short cover statement that walks the reviewer through the timeline in plain language: when the booking was made, what the guest agreed to, when reminders went out, when the cutoff passed, and what happened on the night. Attach the supporting documents in that order. Reviewers handle many cases quickly, and a clear one-page narrative with labeled attachments is far more persuasive than a pile of screenshots. If your booking system can export a dispute packet automatically, use it, but still read it before sending to make sure it tells the story correctly.

Decide whether to fight, refund, or split the difference

Not every dispute is worth contesting. If the guest has a plausible story, such as a confirmation that went to spam, a cancellation attempt your system did not record, or a genuine emergency, refunding may be the right call for the relationship and the review it prevents. If the deposit is small and the dispute fee is close to the amount at stake, some operators simply accept the loss and move on. On the other hand, a guest who booked, ignored reminders, never showed, and then claimed not to recognize the charge is a case worth answering, both for the money and because the same person will do it again elsewhere.

A middle path is to contact the guest directly before the response deadline. Many disputes are filed because the cardholder saw an unfamiliar line on a statement and tapped a button in their banking app, not because they have a grievance with you. A short, courteous message explaining the charge and offering to talk often ends with the guest withdrawing the dispute, which is faster and cheaper than winning it. Keep a note of what was offered and agreed so you can reference it if the dispute proceeds anyway.

Fix the upstream causes so the next one does not happen

The most effective response to disputes is to prevent them. Check that the name on the guest's statement is recognizable as your restaurant rather than a processor's name or a shortened code; unrecognized descriptors are behind many filings where the guest claims not to know the charge. Make sure the deposit amount, the trigger for forfeiting it, and the exact deadline appear in the booking flow and in the confirmation, not only in a linked policy page. Send a reminder before the cutoff that restates the terms and gives a one-tap way to cancel. Each of these removes a reason a guest can honestly say they did not know. Related: Making Deposits Guest Friendly

Then look at how forfeitures are handled internally. Charge the deposit promptly after the no-show and send a receipt that explains why, so the guest learns about it from you rather than from a statement weeks later. Give your host team a script for guests who call upset, with a clear escalation path and the authority to refund in defined situations. Keep a simple log of every dispute, its reason code, and the outcome. After a few months, that log will show you exactly where your process leaks, and fixing those points cuts disputes far more than any amount of evidence gathering after the fact. Related: Handling Deposits Fairly