How to Take Deposits for Bookings (Without Annoying Guests)

To take a deposit for a restaurant booking, use a booking system that captures a card payment at the moment the guest confirms their reservation. With TableNest, deposits unlock on the Business tier and above: you set a per-head or per-booking amount, choose which bookings it applies to (large groups, peak nights, ticketed events), and the guest pays through your embeddable widget or hosted booking page before the table is locked in. The deposit is either credited against the final bill or forfeited if the guest no-shows, depending on the rules you set. There is no per-cover commission and TableNest takes no cut of the deposit — you pay one flat monthly fee. The whole point is to protect your covers without adding friction, so the payment step feels like a natural part of confirming, not a hurdle that scares diners off.

How does a booking deposit actually work?

A booking deposit is a small upfront payment the guest makes when they reserve, held against their attendance. Here is the flow in practice:

A guest selects a date, time and party size on your booking widget or hosted page.
If the booking matches a rule you have set — say, six or more people on a Friday — the system asks for a deposit before confirming.
The guest enters their card details and pays. Only then is the table locked in and the confirmation sent.
When they turn up, you credit the deposit against their bill or refund it after service — whichever your policy says.
If they do not show and do not cancel in time, you keep the deposit as compensation for the empty seats.

With TableNest, deposits are built into the Business tier and above. The payment runs through your own connected Stripe or Square account, so the money lands with you rather than with us: we take no cut of a deposit and no commission per cover, which is a common sting with legacy platforms. Business is $49/mo AUD or $34/mo USD, flat.

When should you ask for a deposit — and when shouldn't you?

Deposits are a tool, not a blanket policy. Apply them where the risk of a no-show actually costs you money, and leave them off where they would just annoy a low-risk guest.

Good candidates for a deposit:

Large groups — the bookings that hurt most when they vanish.
Peak service periods like Friday and Saturday nights, or public holidays.
Special events, set menus or ticketed nights where you have committed stock and staff.
Bookings from guests with a history of not turning up.

When to skip it:

A table for two on a quiet Tuesday — the friction is not worth it.
Regulars you trust and want to keep feeling welcome.
Walk-ins and same-day bookings, where a deposit step slows momentum.

The best approach is targeted. In TableNest a deposit policy is scoped by the things that actually predict risk: minimum and maximum party size, days of the week, a time window, a specific area of the room, or a particular service or event. Everything else books as normal, so most diners never see a payment prompt at all — only the ones worth protecting do.

How much should a deposit be?

Set the deposit high enough to make a guest think twice about ghosting, but low enough that it does not feel like buying a ticket. A per-head amount usually works best because it scales with the risk — a table of twelve failing to show costs far more than a table of two.

TableNest gives you three shapes to choose from:

Per booking — one flat amount to hold the table, regardless of size.
Per head — an amount multiplied by the party size, so exposure and deposit move together.
A percentage of an estimated bill per person, for set menus and events where you already know roughly what the night is worth.

Whatever number you choose, credit it against the bill wherever you can. A deposit that comes off the final cheque feels fair to the guest — it is not an extra charge, just an early one. The framing matters as much as the figure. For more on keeping costs predictable across the board, see our take on running an affordable booking system.

What happens when a guest cancels?

This is where your policy earns its keep. Set a clear cancellation window — for example, 24 or 48 hours before the booking — and communicate it upfront. Inside that window, the guest cancels and gets their deposit back. After it, the deposit is forfeited.

TableNest lets you set that window in hours per policy, and you can add a middle tier if a hard cliff feels harsh: a shorter window closer to the booking that refunds an agreed percentage rather than all or nothing. For set menus and events where your costs are already sunk, a policy can be marked non-refundable outright.

The system also handles the reminding for you. Every booking gets an SMS confirmation and a reminder before service, and both carry a one-tap cancel link that takes the guest straight to their booking — there is nothing to remember and nothing to type. That link is what turns a wavering guest into an early cancellation, which is exactly what you want: an empty seat you know about in advance can be refilled. SMS is included in every plan (in Australia, 120 a month on Starter, 240 on Business, 400 on Pro; US Starter includes 240 a month), so reminders do not come as a surprise line item.

Be transparent about the rules at the point of booking. A guest who forfeits a deposit they were warned about rarely complains; a guest surprised by a charge they never saw coming will. Clarity is what stops a deposit policy from becoming a review problem.

Do deposits actually reduce no-shows?

Yes — because they change the guest's relationship to the booking. A free reservation costs nothing to abandon; a booking with money attached carries a small, real consequence. That shift in mindset is the mechanism. Even a modest deposit turns a casual "we'll see" into a genuine commitment, and it gives waverers a reason to actively cancel — via that one-tap cancel link — rather than simply not turning up.

Deposits also work best alongside good reminders rather than instead of them. A confirmation at the time of booking plus a reminder before service catches the honest forgetters, while the deposit deters the careless ones. Used together, they attack no-shows from both sides. If you would rather not charge a deposit at all — plenty of venues are right not to — the reminder-first playbook is in how to reduce no-shows at your restaurant without deposits. Deposits are the escalation, not the starting point.

We are an early-stage product and we will not quote invented figures at you — but the logic is straightforward and well understood across hospitality: attach a stake to the booking, make cancelling easy, and remind people they are expected. To see how the deposit tools fit with the rest of the platform, have a look at our restaurant reservation software.

Ready to protect your covers without upsetting your regulars? Start a free 30-day trial — no card required to sign up. TableNest is affordable, not free: one flat monthly fee, SMS included, and no per-cover commission ever. A card goes on file only when you are ready to go live to the public and to keep your dashboard past day 30. Set your deposit rules, keep every dollar you collect, and fill more of the seats you have already booked.