Eight months ago a steakhouse in Izmir Karşıyaka introduced a $5 refundable deposit — weekly empty tables fell from 14 to 4 and monthly revenue climbed by $1,400. The mechanics are simple: Stripe pre-auth, a tight refund window, and the right copy.
Why deposits work: the OpenTable data
OpenTable's 2024 global report shows 19% of reservations end as no-shows; Saturday 8 PM slots reach 26%. The same dataset finds restaurants charging a small deposit drop to 5.3% — a 72% reduction.
Behavioral economics explains it: loss aversion. Losing $5 hurts more than the inconvenience of showing up. The amount is secondary; the commitment is the real lever.
Stripe pre-auth: hold, don't charge
The cleanest setup is a hold, not a charge. Stripe Payment Intents support capture_method: manual, which authorizes the card for up to 7 days without moving funds. When the guest arrives, release; when they don't, capture.
- Pre-auth $5 on booking, send confirmation email and SMS
- Server taps "arrived" on a tablet — webhook releases the hold
- No-show triggers capture within 24h with a friendly note
Voice of copy: contract, not punishment
Karşıyaka's breakthrough was copy. Replacing "A deposit will be charged" with "We're holding your table; the $5 returns to your check on arrival" lifted booking conversion from 14% to 38%.
Cover three things in writing: refund conditions, cancellation window (24 hours is standard), and exceptions (weather, emergencies). Transparency converts; surprise fees kill bookings.
FAQ
Won't guests feel offended? Data says the opposite — conversion rises because guests trust the table is truly reserved for them.
What's the right deposit size? Roughly 15-20% of average check. $5-10 in the US is the psychological sweet spot; $40 deters, $1 does nothing.
How long should the refund window be? 24 hours is industry standard. Shorter feels unfair; longer loses behavioral effect. Always allow manual refunds for genuine emergencies.
Found this helpful? Share it.
Related articles
Why Digital Menus Increase Restaurant Revenue by Up to 30%
Studies show restaurants using digital QR menus see measurable increases in aver…
When a Customer Downgrades, What Happens to Old Features? — The Silent Feature-Drift Problem in SaaS
Most SaaS apps run a single line of code when a customer downgrades — but old fe…
JWT alg-confusion attack — why Supabase's HS256 → RS256/JWKS migration breaks legacy verifiers
Verifiers that never decode the JWT header are wide open to `alg=none` and alg-c…