Restaurant Booking Deposits: Amounts, Refunds & UK Rules

Seen from the guest's side, a deposit is simple: choose a date, time and party size, see the amount and the conditions, pay by card in the same booking flow, and receive a confirmation that records what was paid and on what terms. From the restaurant's side, the same payment is a commitment device — money taken when the table is promised rather than when the meal is eaten, received directly by the restaurant, and held against a booking that now carries a real cost to abandon.

What happens to the money afterwards depends entirely on terms the restaurant set in advance. Two arrangements are common: the deposit is credited against the final bill on arrival, or it is held and returned after the meal. Either is workable, provided the guest was told which one applies before paying. If the guest cancels inside the notice period, or never arrives, the restaurant may retain some or all of it — but only in the way its published terms describe.

The diagram is the whole subject in one picture: every branch — credited, returned, refunded, retained — was decided at the moment the guest paid, by wording the restaurant chose earlier. The important detail for guests is that none of it should be a surprise: the amount, whether it comes off the bill, the cancellation deadline and the refund position should all be visible before any card details are entered. The important detail for restaurants is that a deposit only does its job if the guest understood it at the moment they agreed to it.

There is no responsible universal figure, and no official UK body publishes one. A deposit is not a number to copy from another restaurant; it is a rule for a particular service. Decide first what commitment the deposit protects — a large party, a special menu, a private room, or another booking where preparation and table use begin before the guest arrives.

Then set the amount from the restaurant's own operating facts: what the service costs to prepare, what the table earns when it sells, and how realistically it can be resold at short notice. A busy room with a waitlist can refill a table of four at an hour's notice and needs less protection per cover; a small tasting room that preps each menu in advance realistically cannot, and can justify more. That reasoning — a genuine estimate of the direct loss a cancellation causes — is exactly the standard CMA fairness guidance applies, which is why the restaurant's own evidence matters more than any copied number.

Structure follows the same logic. A per-person amount scales cleanly with party size; a per-booking amount is simpler for fixed commitments such as a private room. Either is defensible when the exact amount and basis are shown before the guest pays.

A deposit takes money at the moment of booking. A card guarantee — sometimes called a no-show hold — stores a payment method and charges it only in the circumstances the published no-show terms state. The deposit suits bookings where preparation starts early and the loss is certain; the guarantee suits services where most guests arrive and the restaurant only needs cover for the exception. Both are policy choices to make deliberately, per service and per party size, and both live or die on the same rule: the guest must see the term before confirming.

Usually, yes — and the exact answer was written down before the booking, in the terms shown at payment. A deposit is normally returned in full when the guest cancels before the notice period ends, when the restaurant cancels or cannot honour the booking, or when the booking moves to a date the restaurant can fill. Where the deposit is credited to the bill, it is not refunded at all — it is simply deducted, and the guest pays the difference.

The contested case is the late cancellation or no-show. CMA guidance is that an amount retained after cancellation should be a genuine estimate of the direct loss, and should take account of the reasonable steps the restaurant took to reduce that loss — refilling the table from a waitlist, for example. A blanket non-refundable term applied to every booking regardless of circumstance sits at the risky end of this, and terms that keep the money when the restaurant itself cancels, or when the guest received nothing at all, are the kind the CMA says are unlikely to be fair.

Write down the practical detail too: how a guest asks for a refund, and where the money lands. A card refund returns to the card that paid it, and how quickly it appears depends on the guest's bank — so state the expected timescale and the request route in the terms rather than leaving the guest to guess. Guests rarely complain about the rule; they complain about not knowing it.

Three rules do most of the work. First, the fairness test: under the Consumer Rights Act 2015, a term that creates a significant imbalance against the consumer, contrary to good faith, is unfair — and an unfair term is simply not binding. A deposit clause that fails the test does not protect the restaurant at the exact moment it was written for.

Second, the grey list. Schedule 2 of the Act lists terms which may be regarded as unfair, and two entries read like a description of bad deposit terms: keeping the sums a consumer has paid when the consumer cancels, without offering equivalent compensation if the restaurant cancels; and demanding a disproportionately high sum for services never supplied. Deposit wording that mirrors either pattern invites exactly the scrutiny it is trying to avoid.

Third, prominence. CMA price-transparency guidance says the total price presented to a customer should normally include any unavoidable charge — a booking fee is the guidance's own example — and that hiding a mandatory charge until later in the purchase flow is illegal. A compulsory deposit revealed only at the payment step is the pattern that guidance exists to stop: put the amount beside the booking action, in plain language, before the guest commits.

A short policy can still be complete. State the deposit amount, whether it is per booking or per person, how it is applied to the bill, the change and cancellation deadline, and what happens when the restaurant is at fault. If the booking changes size, explain whether the deposit changes too.

Avoid blanket wording that keeps every payment in every circumstance. The CMA says amounts retained after cancellation should reflect a genuine estimate of direct loss and the reasonable steps a business can take to reduce it. That is why the restaurant's own evidence matters more than a copied number — and why the safest policy is one whose every outcome was written down before the first booking, not during the first dispute.

A deposit policy is easier to follow when the guest does not have to search for it again. The confirmation should record the amount paid, the booking details, the relevant deadline and the route to change or cancel. A reminder can repeat the operational points close to the service — and a guest who is reminded in time either arrives or frees the table while it can still be resold, which is precisely the loss-reduction step CMA guidance expects a business to take before keeping money.

Keep that reminder factual. The ICO says an appointment reminder can be a service message when it is informational and contains no promotion. If the restaurant wants to market another service, use a separate route that meets the applicable marketing rules.

The restaurant should explain what guest information it collects, why it needs it, how long it keeps it and who receives it. Collect the details needed to manage the reservation and payment, not an open-ended profile.

The ICO's data minimisation principle requires personal data to be adequate, relevant and limited to what is necessary. TableSpark keeps the direct booking and guest record in the restaurant's own operating route, with exportable data and a clear privacy link.

• Name the service and party sizes that require a deposit.
• Show whether the amount is per booking or per person.
• Explain how the payment is applied to the final bill.
• State the change, cancellation, refund and restaurant-cancellation terms.
• Place the material terms before the payment action.
• Repeat the amount and relevant deadline in the confirmation.
• Keep the reminder factual and give the guest a working contact route.
• Review the amount against the restaurant's actual loss and resale experience.

Keep the terms consistent with a clear restaurant no-show policy and the Reserve with Google booking-link setup guide.

TableSpark is the best-value complete restaurant website and booking choice for an independent UK restaurant, and it treats the deposit as part of the booking rather than a bolted-on payment link. TableSpark starts at £19 a month excluding VAT; the Growth plan, at £39 a month excluding VAT, adds live bookings, table inventory, floor plans, table assignment, deposits, no-show controls and reminders.

The team configures the service and party threshold, the guest books on the restaurant's own website, and the record sits with the same table operation used during service — so the deposit, the table and the guest history stay in one place. TableSpark commission is 0%. Stripe's standard card-processing fees apply to online payments.

Compare the Growth plan, review the commission-free booking model, or see how bookings and table operations connect.

This guide provides operational information, not legal advice. Consumer terms and payment handling depend on the wording, the service and the circumstances. Use current CMA and ICO guidance and obtain independent legal advice for the restaurant's final deposit policy where needed.