No-Show Fee Chargebacks: How to Protect Your Restaurant

The $128 problem nobody warns you about

A guest books a table for four on a Saturday night. They don't show. You charge the no-show fee to the card they gave you at booking. Two weeks later, your payment processor sends a notification: the guest has filed a chargeback. Now you owe the fee back, plus a $15 to $100 processing penalty, and you have 20 to 45 days to prove the charge was legitimate.

The average chargeback costs a merchant $128 in fees and internal costs, not counting the original charge itself. For a $10 per-person no-show fee on a party of four, you're now out $168 on a table that sat empty.

This is the part of no-show fees that most guides skip over. Setting up the policy is straightforward. Collecting the card is easy. But if you can't prove the guest agreed to the charge, the card network sides with the cardholder almost every time.

Why restaurants lose no-show disputes

Credit card disputes aren't court proceedings, but they follow a similar logic. The cardholder says "I didn't authorize this charge." The burden of proof falls on you, the merchant, to show that they did.

Here's where restaurants get caught. The three most common reasons no-show fee chargebacks succeed:

No record of consent. The guest's card was on file, but there's no documentation showing they agreed to a no-show fee. Maybe the policy was mentioned verbally, or buried in small print on the website. That's not enough. Visa and Mastercard require clear evidence that the cardholder authorized the specific charge.

Vague policy language. "By booking, you agree to our terms" is common. It's also weak. If the cancellation policy isn't spelled out at the point where the card is collected, processors treat it as insufficient disclosure.

No confirmation trail. The guest booked by phone or DM. Someone on your team took a card number and wrote it on a sticky note. There's no timestamped record, no policy acknowledgment, no email confirmation. When the dispute arrives, you have nothing to submit.

The industry-wide merchant win rate on chargebacks is about 45%. But restaurants tend to perform worse than average because dining is a consumable service, and it's harder to produce the kind of before-and-after evidence that works for product sellers. For no-show fees specifically, the evidence gap is even wider because the guest never received anything.

What actually wins a no-show fee dispute

The good news: when consent is properly documented, the numbers flip dramatically. Restaurants that collect card authorization with documented policy agreement at booking win nearly 90% of disputes. Post-hoc charges, where you add the fee after the fact without clear prior consent, win less than a third.

The difference comes down to what the card networks call "compelling evidence." For a no-show fee, that means:

A timestamped record of the booking showing the guest's name, date, time, party size, and the card used. Your reservation system should generate this automatically.

The cancellation/no-show policy displayed at the point of card entry. Not on a separate terms page. Not in a confirmation email sent after the fact. Right there, on the screen where the guest enters their card details, before they hit confirm.

An explicit consent mechanism. The strongest version is a checkbox: "I understand that a fee of $X per person will be charged if I don't show up or cancel less than Y hours before my reservation." A checkbox doesn't guarantee you'll win every dispute, but it creates a timestamped record that the guest actively acknowledged the policy.

A confirmation message sent to the guest (email or SMS) that restates the policy. This serves double duty: it reminds the guest about the cancellation window, which reduces no-shows in the first place, and it gives you a second piece of evidence if a dispute arrives.

Building a chargeback-proof booking flow

You don't need a legal team. You need a booking flow that creates the right paper trail automatically. Here's what that looks like, step by step.

Step 1: Write the policy in plain language

Skip the legal boilerplate. Your cancellation policy should fit in two or three sentences that any guest can understand on a phone screen.

Good: "If you don't show up or cancel less than 24 hours before your reservation, a fee of $10 per person will be charged to the card on file."

Bad: "Guest acknowledges and agrees that failure to provide adequate notice of cancellation pursuant to the establishment's policies may result in the application of fees as outlined in the terms and conditions."

The second version might feel more official. It's actually worse for disputes because it's vague about the amount and the timeline, which gives the cardholder room to argue they didn't understand what they were agreeing to.

Step 2: Display the policy where the card is collected

This is non-negotiable. The policy text has to appear on the same screen, in the same flow, where the guest enters their card information. If your booking widget separates the card entry from the policy disclosure, you've created a gap that the cardholder's bank will exploit.

For phone bookings, read the policy to the guest before taking their card number, and note in your system that you did. Some reservation platforms let you send a card-collection link by text, which solves this problem by putting the guest through the same online flow.

Step 3: Add a consent checkbox

"I agree to the cancellation and no-show policy" with a link to the full text, or better yet, the policy displayed inline. The checkbox should be required. No check, no booking.

This creates a database record: guest X checked the consent box at timestamp Y. That's your strongest piece of evidence.

Step 4: Send a confirmation with the policy restated

Email is fine. SMS is better because the open rate is above 90%. Include the reservation details, the cancellation deadline, and the no-show fee amount. This isn't just a reminder. It's evidence.

Step 5: Send a reminder before the cancellation window closes

"Your reservation for 4 at 7:30 PM tomorrow is confirmed. To cancel without a fee, let us know by 5:30 PM today." This gives the guest a clear, final chance to cancel. If they don't respond and don't show up, your paper trail now includes: consent at booking, confirmation with policy, and a reminder with the deadline. That's a strong representment package.

Card-on-file vs. deposits vs. prepayment: the chargeback angle

Each approach to securing a reservation carries different chargeback risk.

Method	How it works	Chargeback risk	Best for
Card-on-file	Card saved via Setup Intent, charged only if guest no-shows	Medium. Guest may claim they didn't authorize the charge. Consent documentation is your defence.	Most reservations. Low friction for guests.
Deposit	Guest pays a portion upfront, applied to the bill	Low. Guest authorized a charge and received confirmation. Dispute window is narrower.	Large parties, special events, prix fixe
Full prepayment	Guest pays the full amount in advance	Lowest. Standard e-commerce transaction with clear authorization.	Ticketed events, tasting menus

Card-on-file has the highest chargeback exposure because the charge happens after the fact, when the guest isn't present to authenticate. This is what Stripe calls a merchant-initiated transaction (MIT). The card was saved with a Setup Intent, but the actual charge is a Payment Intent created later, off-session. Card networks allow this, but the exemption is at the discretion of the issuing bank.

That's exactly why consent documentation matters more for card-on-file than for deposits. With a deposit, the guest actively completed a payment. With card-on-file, you're charging a saved card based on a policy they agreed to earlier. The agreement is your only evidence.

Want to see how no-shows affect your bottom line? Try the No-Show Cost Calculator to put a real number on it.

What to do when a chargeback arrives

You'll get a notification from your payment processor with a reason code and a deadline. For no-show fees, the most common codes are Visa 13.1 (Merchandise/Services Not Received) or Mastercard 4853 (Cardholder Disputes). The guest is claiming they didn't receive what they paid for, which is technically true: they paid a fee for not showing up, not for a meal.

Your response window is typically 20 to 45 days depending on the network. Here's what to include in your representment:

Screenshot of the booking flow showing the policy text and consent checkbox as the guest would have seen it. Your reservation platform should be able to produce this.

The specific booking record with guest name, date, time, party size, card used, and the timestamp of the consent checkbox.

Confirmation and reminder messages sent to the guest. Include the full message content with timestamps, not just a note that they were sent.

Your cancellation policy as a standalone document, highlighting the relevant sections.

Communication log. If the guest contacted you to complain before filing the chargeback, include those messages too. If they didn't contact you at all, note that: it weakens their case.

Keep everything under 2 MB for Visa, 10 MB for Mastercard. PDF and JPEG formats only.

The real play: prevent the dispute before it starts

Chargebacks are expensive to fight even when you win. The processing fee doesn't get refunded. Your time doesn't get refunded. And if your chargeback ratio climbs above 1.5% of transactions, Visa's VAMP program hits you with $8 per dispute.

So the better strategy is making the chargeback unnecessary. Three things that work:

Make cancelling easier than disputing. If a guest can cancel with one tap from a text message, they'll cancel. If they have to call during business hours, they'll just skip the reservation and argue the fee later. Reduce the friction to cancel and you reduce both no-shows and chargebacks.

Reach out before you charge. When a guest no-shows, send a message before processing the fee: "We missed you tonight. If something came up, let us know. We'll be happy to rebook." This isn't about being soft. It's about creating a record that you attempted to resolve the situation, and giving the guest a chance to cancel the upcoming charge voluntarily. Guests who feel heard don't file chargebacks.

Offer the fee as a credit toward a future visit. This is the move that changes the math entirely. Instead of charging $40 to a guest who no-showed, offer to convert it to $40 in credit toward their next reservation. You keep the revenue. They keep the relationship. And nobody files a dispute over credit they plan to use.

The consent checklist

Before you charge your next no-show fee, make sure you can answer yes to all of these:

• Policy text was visible on the same screen where the guest entered their card
• Guest actively consented (checkbox or equivalent) with a timestamped record
• Confirmation was sent with the policy and cancellation deadline restated
• Reminder was sent before the cancellation window closed
• The charge amount matches what was disclosed in the policy
• The booking record links the guest to the consent, the card, and the reservation

If any answer is no, you're exposed. Fix the gap before the next dispute arrives.

Sources: Mastercard: True Cost of a Chargeback, PaymentsPlus: Chargebacks in Canada, Chargebacks911: Restaurant Chargebacks, Attenda: No-Show Fee Legal, Stripe: Setup Intents, Chargeflow: Visa Dispute Rules 2026, Maitre'D: Hospitality Chargebacks.

When you're ready to take reservations, Trudy's Table is built for Canadian independents. Card-on-file with documented consent, built right into the booking flow.

---