Credit Card Holds for Reservations: How They Work
What a card hold actually is, how Stripe-style holds work behind the scenes, the disclosure rules that make a no-show fee chargeable, and who takes a cut on each platform.
July 2, 2026 · 7 min read
A credit card hold for a reservation saves a guest's card at booking without charging it, so the restaurant can charge a disclosed fee only if the party no-shows or cancels late. It is the gentlest form of no-show protection: no money moves for the guests who show up, which is nearly all of them. Here is how it works mechanically, what you must disclose, and where the money goes on each platform.
What actually happens to the card
Despite the name, most reservation "holds" do not freeze money on the card the way a hotel does. The common pattern (this is how Stripe implements it, and how TableHelm uses Stripe) has two steps. At booking, the card is saved securely with the payment processor: the guest enters details into the processor's own form, the restaurant's system stores only a token, and no charge or authorization amount appears. Later, and only if the policy is broken, the restaurant triggers a charge against the saved card for the published fee. In Stripe's vocabulary that is a SetupIntent at booking and a PaymentIntent using the saved payment method if a no-show happens.
- The guest's statement shows nothing at booking; there is no pending amount.
- The card number never touches the restaurant's database; the processor holds it and the restaurant keeps a token.
- The charge, if ever made, is for the exact disclosed fee, initiated by the restaurant.
The disclosure rules that make the fee stick
A saved card only helps if the eventual charge survives a dispute. Card networks side with the guest unless the merchant can show the guest agreed to the fee at booking. Practical requirements:
- State the exact fee and conditions where the card is entered: "No-shows without notice are charged $15 per guest" next to the card field, not in a linked page.
- Repeat it in the confirmation email, with the free-cancellation deadline and a working cancel link.
- Keep evidence: the booking record, the policy text shown, timestamps, and your call attempt at 15 minutes past.
- Charge the disclosed amount exactly. A $15 policy charged at $20 loses the chargeback and the regular.
- Waive on contact. Guests who called and were charged anyway are the chargebacks you cannot win and the reviews you cannot delete. Press coverage notes chargebacks remain a pain even with well-run fees, so pick battles.
Do holds work? The documented answer
“We implemented this policy via Resy and later OpenTable anyways and they have essentially gone to zero.”
Operators running $10-25 per-head policies report the same shape: no-shows collapse once a card secures the booking, and the fee is rarely charged. The card is a commitment device first and compensation second.
Who takes a cut of your no-show fee
| Platform | Platform take on the fee | Source |
|---|---|---|
| OpenTable | 2% service fee (since 2026), absorb or pass on | Philadelphia Inquirer |
| Tock | 2-3% of prepayments by tier | resy.com plans page |
| Resy | Deposits/prepays require Tock-powered tiers (2-3%) | resy.com plans page |
| resOS | 2% surcharge + Stripe fees | resOS transaction-fees FAQ |
| SevenRooms | Holds/deposits via FreedomPay; cost not published | sevenrooms.com |
| TableHelm | 0%; runs on your own Stripe account, only Stripe's processing applies | Product fact (that is us) |
The structural difference is whose payment account the charge runs on. When the platform processes the fee, it can skim it; when the charge runs on the restaurant's own Stripe account (Stripe Connect, the way TableHelm Pro works), there is nothing between the guest's card and the restaurant's bank except Stripe's standard processing.
Hold, deposit or prepayment?
Holds for everyday tables, deposits for high-stakes bookings, full prepayment for ticketed experiences. The next guide compares the first two properly; the short version is that a hold's superpower is invisibility for the 95%, and a deposit's superpower is certainty for the 5%.
When a deposit beats a hold, with the wording for both.
Read: deposit vs card holdPolicy text ready to paste next to your card field.
Get the policy templatesCommon questions
Does a reservation card hold charge the guest anything?
No. The card is saved with the payment processor at booking, nothing is charged and no pending amount appears. A charge happens only if the disclosed policy is broken, and only for the published fee.
Is it safe to take card details for reservations?
Done properly, the restaurant never sees the card: the guest enters it into the processor's secure form (Stripe or similar) and the restaurant stores a token. Never write card numbers in a book or a spreadsheet; that is both a breach risk and a compliance violation.
Can a guest dispute a no-show fee?
Yes, and some will. You win disputes with disclosure evidence: the fee shown at booking where the card was entered, the confirmation email, and your call attempt. You avoid disputes by waiving for anyone who made contact.