Credit card holds for restaurant reservations: guide

A party of eight booked for Saturday night, a special menu ordered, an extra server scheduled... and nobody shows up. Faced with no-shows, more and more restaurants ask for a credit card hold (sometimes called a bank imprint or card guarantee) at the moment of booking. The guest enters their card details, nothing is charged, but both sides know a commitment has been made.

The practice raises plenty of questions, though. What exactly happens to the guest's money? How is a hold different from a deposit or a prepaid reservation (or booking, as UK diners would say)? When are you actually allowed to charge the card? And how do you announce it without losing bookings? This guide answers each question, point by point, for both US and UK restaurants.

In short:

a credit card hold secures the card at booking; nothing is charged unless the guest fails to show up or cancels too late;
it is legal in both the US and the UK, on one central condition: the guest must be clearly told the amount and the conditions before booking;
a hold is not a deposit and not a prepayment: those involve money actually changing hands on the day of booking;
a reasonable amount (roughly the price of a main course or a set menu per cover) deters no-shows without punishing honest guests;
reserve it for high-stakes situations: large parties, fully booked nights, special events.

What is a credit card hold on a restaurant reservation?

A credit card hold means the guest's card is registered at the time of booking and serves as a guarantee for the reservation. Two important things happen, and one thing does not:

the card is verified and stored securely by the payment processor (the restaurant itself never sees the full card number);
the restaurant gains the right, disclosed in advance, to charge an agreed no-show fee if the guest neither shows up nor cancels in time;
but nothing is charged at booking. If the guest honors the reservation, or cancels within the free-cancellation window, no money ever moves.

This is the gentlest form of no-show protection, and it works. According to OpenTable's own data, guests who book with a credit card hold are up to 16% less likely to no-show and 15% less likely to cancel late than guests who book at restaurants with no booking policy at all.

The scale of the problem justifies the tool. Research by Zonal and CGA, reported by The Caterer, estimated that no-shows cost UK hospitality around £17.6 billion a year, with one in seven consumers admitting they had failed to honor a booking. At ViteUneTable, the reservation system we build for independent restaurants, the pattern we see is the classic one: in the vast majority of cases the mere existence of the guarantee is enough to make the guest show up, or cancel in time so the table can be resold.

How the hold actually works with Stripe-style processors

Behind the scenes, "taking a card hold" covers two distinct technical mechanisms, and it helps to know which one your software uses:

A true pre-authorization. The processor asks the guest's bank to authorize a specific amount, which is ring-fenced on the account: the guest cannot spend it, but it has not been debited. This is the hotel and car-rental model. Its limitation is time: per Stripe's documentation on holds, an online card authorization is generally valid for 7 days (5 days for some Visa transactions), after which the funds are released automatically. That makes true pre-authorizations practical only for reservations a few days out.
A saved card with delayed charging. The card is tokenized and stored at booking, no amount is blocked, and the restaurant charges the agreed fee only if the no-show actually happens. This is what most restaurant reservation systems do, precisely because reservations are often made weeks ahead, far beyond any authorization window. For the guest it is even lighter: nothing on their account moves, not even temporarily.

Either way, if the guest shows up, the hold simply ends: a pre-authorization is canceled and the funds released, a stored card is never charged. Stripe also lets a merchant capture less than the authorized amount, so a hold never forces you to charge the full figure.

Card hold or immediate charge: do not confuse the two

Some restaurants charge money the moment the booking is made: a prepaid tasting menu, a ticketed event, a chef's counter experience. That is a real payment with a real debit. A credit card hold moves no money as long as the guest keeps their side of the bargain. For the guest, the difference is enormous: their statement shows nothing, and at worst (with a true pre-authorization) part of their card limit is temporarily tied up.

Hold, deposit, prepaid booking: three different regimes

The three tools are often mixed up, in the US and the UK alike. Here is the practical difference:

Mechanism	Money taken at booking?	How it works
Credit card hold	No	Card secured as a guarantee; an agreed fee is charged only on a no-show or late cancellation
Deposit	Yes	A partial amount (per cover or per party) is paid upfront, then credited against the final check (or bill) or refunded per your policy
Prepaid booking	Yes, in full	The menu or event is paid at booking, like a theater ticket; usually non-refundable past a stated deadline

One nuance for UK restaurateurs: whatever you keep when a guest cancels must stay proportionate. The Competition and Markets Authority's guidance on writing fair consumer contracts says non-refundable prepayments and cancellation charges are more likely to be fair when they reflect a genuine estimate of what the business actually loses, and that blanket "no refund in any circumstances" terms are likely to be unfair. The same logic is simply good practice in the US.

Are credit card holds for reservations legal?

Yes. Neither the US nor the UK has a law that prohibits requiring a card to guarantee a reservation or charging a disclosed no-show fee. What the law and the card networks do demand, in both countries, is clear disclosure before the guest commits. In the UK, unfair or hidden cancellation terms can be challenged under consumer protection law, as the CMA guidance makes explicit; in the US, an undisclosed or surprise fee is exactly the kind of charge a cardholder wins a dispute over.

Concretely, to be beyond reproach:

Announce the policy before the booking is confirmed, not after. The guest must know, at the moment they book, that a card is required and a fee may apply.
State the exact amount that will be charged in case of a no-show, per cover or per party.
Spell out the conditions: until when cancellation is free, what happens if the party is late or smaller than booked, and how to cancel.
Keep proof of that disclosure: the booking page, the confirmation email restating the conditions. If the guest later disputes the charge with their bank, this evidence is what protects you; card processors like Stripe let you submit your cancellation policy and its disclosure as dispute evidence.
Never charge more than the announced amount, and only in the cases you announced.

One note of caution: no statute in either country specifically regulates restaurant card holds. The practice rests on ordinary contract law and general consumer-protection duties of transparency. If you plan an aggressive policy (high amounts, short cancellation windows), have your usual advisor review it.

How much should the hold be?

There is no official scale, on either side of the Atlantic. The right question is: what amount makes a no-show feel serious to the guest without turning the booking into an ordeal?

Some common-sense reference points:

Casual restaurant, bistro: roughly the price of a main course per cover, say $20 to $30 or £15 to £25. Enough to create commitment, not enough to frighten.
Fine dining, single tasting menu: the price of the menu per cover is defensible, since an empty table is close to a total loss.
Groups and private dining: a per-cover amount stated in the quote from day one, because a large party that vanishes can wreck an entire service.
Fixed-date events (New Year's Eve, Valentine's Day, Mother's Day): a higher amount, or outright prepayment of the menu, since the table cannot be resold elsewhere on the night.

Remember that a true pre-authorization ties up part of the guest's card limit until it is released, and can be declined if their limit is already reached. Stick to amounts you would be comfortable justifying to the guest face to face.

Finally, apply the rule with judgment: the goal is to deter "just in case" bookings, not to bill a regular who had a genuine emergency. Waiving one fee for a good customer usually buys more goodwill than the fee is worth.

How to tell guests without scaring them away

Fear of losing bookings is the number one objection restaurateurs raise. Almost all of it is solved by wording.

Explain the why: a sentence like "To guarantee your table, we ask for a card at booking. Nothing will be charged if you show up or cancel at least 24 hours ahead" defuses most resistance. Guests already know the principle from hotels.
Lead with the free cancellation, not the fee. The message is not "you will be charged", it is "just let us know, and nothing happens".
Stay consistent: the amount shown at booking must reappear identically in the confirmation email.
Make canceling effortless: a one-click cancellation link in every email turns would-be no-shows into early cancellations, and makes your hold policy all the more defensible.
Do not apologize: a clear, assumed policy inspires confidence. Serious guests, which is nearly all of them, have nothing to fear and understand that perfectly well.

When to require a hold, and when to skip it

A card hold is a powerful tool, not a default setting. It adds a step to the booking flow, and every extra step costs a few legitimate reservations.

Turn it on when the stakes justify it:

parties of 6 or 8 and up, where one no-show guts the service;
Friday and Saturday nights if you regularly turn people away;
special menus and fixed-date events;
small dining rooms, where every table counts double.

Skip it when the friction would cost more than it saves:

weekday lunch, tables of two, a strong base of regulars: an email reminder usually does the job;
a clientele uncomfortable with entering card details online, if it represents a large share of your covers;
a newly opened restaurant, where every won booking matters more than an avoided no-show.

The best approach is surgical: holds on the time slots and party sizes that actually hurt you, two-click booking everywhere else. Your no-show statistics (day, service, party size) will tell you exactly where to draw the line.

Setting up credit card holds with ViteUneTable

Technically, you have nothing to build: taking and charging card guarantees is your reservation software's job, together with its payment processor.

With ViteUneTable, credit card holds are part of the Standard + Anti No-Show pack, at €49 excl. VAT per month, with 0% commission on your covers. Concretely:

you enable the card hold in a few clicks and choose the amount per cover;
you target where it applies: only groups, only certain services, or every reservation;
the guest sees the amount and the conditions at the moment of booking, then again in the confirmation email, which covers your disclosure obligation;
if they show up or cancel in time, nothing is charged; on a no-show, you decide whether to charge, case by case;
the free plan remains available with no time limit and no commission if you want to establish online reservations first and add no-show protection later.

Frequently asked questions

Is there a maximum amount for a restaurant no-show fee?

No US or UK statute sets a specific cap for restaurants. The amount must be proportionate to the booking and clearly announced before the guest commits; UK guidance on fair consumer contracts explicitly expects charges to reflect your genuine loss. In practice, staying between the price of a main course and a full menu per cover keeps you out of trouble.

How long does a hold stay on the guest's card?

If your system uses a true pre-authorization, Stripe's documentation states an online card authorization generally lasts 7 days before the funds are released automatically. Most restaurant systems instead store the card without blocking anything, so there is no hold on the account at all until a no-show fee is actually charged.

Can a guest dispute the charge after a no-show?

Yes, any cardholder can dispute a transaction with their bank. Your best protection is proof of prior disclosure: the policy shown at booking, the exact amount announced, the confirmation email restating both. If the charge matches what was announced, you are in a strong position; if it does not, the dispute will almost certainly succeed.

What if the card has expired or has no funds on the day of the no-show?

The charge can simply fail: a card guarantee is not an absolute promise of payment. That is one more reason to have your software verify the card at booking, and to treat the hold primarily as a deterrent rather than as guaranteed revenue.

Card hold or deposit: which is better for large groups?

A deposit takes real money upfront, which secures big private events where you commit to spending (special menu, extra staff), and it is applied to the final check (or bill) when the party shows up. A hold takes nothing and suits ordinary group reservations. Many restaurants combine the two: holds up to a certain party size, deposits or prepayment beyond it.

Do card holds really drive guests away?

Some "just in case" bookings disappear, and that is precisely the point. OpenTable's published figures show guests booking with a card hold are up to 16% less likely to no-show, and guests who genuinely intend to come overwhelmingly accept a mechanism they already know from hotels, as long as free cancellation stays simple and the message is well worded. If you do see bookings drop, narrow the hold to your riskiest slots instead of abandoning it.

Credit card holds for restaurant reservations: the complete 2026 guide