The OpenTable 2% Service Fee: What It Is and Who Pays It Published July 14, 2026
A guest is booking a Saturday table at your restaurant. Your cancellation policy requires a card, so under the credit card section they read a notice saying that no-shows, guest modifications, and any future charges for the reservation "will also incur an OpenTable service fee." Some of them pause right there. Some of them paste that exact sentence into Google to find out what it means -- which may be how you got to this page. Here is the plain-English version of what that fee is, what it applies to, and who ends up paying it, verified against OpenTable's own support documentation on July 14, 2026.
What is the OpenTable service fee? OpenTable charges a service fee on certain payments processed through its Stripe integration -- the payments layer behind deposits, credit card holds, and prepaid events. OpenTable's support documentation says the fee helps the company "maintain and invest" in its payments platform, and it is charged as a percentage of the transaction. OpenTable does not publish the percentage; it says the rate varies by country and directs restaurants to their account team. In the United States, The Philadelphia Inquirer reported in January 2026 that the fee is 2%, began rolling out to most US restaurants in the second half of 2025, and reaches the remainder in early 2026. This fee is separate from, and on top of, Stripe's own payment processing fee.
Which transactions it applies to Per OpenTable's support documentation, the service fee can apply to deposits, prepaid experiences, ticketed experiences, no-show charges, other charges, and instant booking -- with the exact list depending on your country. The pattern to notice: it applies to money moving through the platform, not to the reservation itself. A standard booking with no card on file does not trigger it. The moment a policy or event involves a payment -- a $25-a-head deposit, a $15 no-show fee, a prepaid tasting menu -- the fee attaches to that payment.
Transaction types OpenTable lists as subject to the service fee, per its support documentation as of July 14, 2026. Applicability varies by country. Transaction type Example Fee applies? Standard reservation, no card Tuesday two-top, no policy No No-show charge $15/person fee on a missed booking Yes Deposit or credit card hold $25/person hold for a party of 8 Yes Prepaid experience $150/head tasting menu Yes Ticketed event New Year's Eve seating Yes
Who pays it: you, unless you flip the toggle By default the restaurant pays. In the United States -- and only in the United States, per OpenTable's documentation -- restaurants can pass the fee to guests instead. The option lives at the bottom of each cancellation policy and each experience setup page in OpenTable for Restaurants, as a toggle asking whether to pass the fee to the guest. It is per-policy and per-experience, so you can absorb the fee on regular bookings but pass it on for a holiday event, or the reverse. If you have never looked for that toggle, you are on the default: you are paying it.
The exception: bookings from Google and other partner sites One case has no toggle. OpenTable's documentation states that service fees for reservations made through partner sites like Google cannot be charged to guests -- for those bookings, the restaurant pays the fee on any deposit, prepaid amount, or no-show charge. If a meaningful share of your covers arrives through Google rather than OpenTable's own app, that share of your payment-backed bookings carries a fee you cannot pass on. It is worth checking your source mix before deciding how much this costs you; the same booking traffic is also subject to OpenTable's per-cover network fees, which is a separate line item.
What it looks like in real dollars At the reported 2%, the fee is small per transaction and real at volume. The Inquirer's example: a South Philadelphia restaurant charging a $15-per-person no-show fee pays about 30 cents of it to OpenTable. Scale that up: a $500 deposit for a private-room buyout carries about $10; a prepaid wine dinner grossing $12,000 carries about $240. None of these numbers break a restaurant. The friction is that they were introduced onto transactions restaurants were already running, and the guest-facing notice appears under your restaurant's name -- so when a guest is confused by it, they call you, not OpenTable.
Passing it on is legal -- but the disclosure burden is yours If you flip the pass-on toggle, the compliance homework lands on you, not OpenTable. The regulatory climate around surprise fees has hardened: the FTC's Rule on Unfair or Deceptive Fees took effect May 12, 2025 -- restaurants were in the proposed version but the final rule covers live-event ticketing and short-term lodging, so restaurants are outside it (deceptive pricing is still reachable under the FTC's general Section 5 authority). States are a different story. California's SB 478 honest-pricing law has banned hidden mandatory fees since July 1, 2024, and the restaurant carve-out (SB 1524) only protects fees that are clearly and conspicuously displayed, with an explanation of their purpose, wherever the price is shown. The practical read for a California restaurant passing the service fee onto a deposit or event: the fee needs to be visible where the guest sees the price, not discovered on the receipt. Guests have also simply had it with fee lines -- the same fatigue behind the tip-screen backlash -- so even where passing it on is clearly legal, decide whether 30 cents is worth being the restaurant with one more fee at checkout.
Where the fee shows up in your books In the Stripe dashboard, the charge appears in the payment breakdown as an "OpenTable application fee," alongside Stripe's own processing fee. For prepaid experiences, OpenTable's Experience Report shows service fees per event under Reporting. Two bookkeeping notes from OpenTable's documentation: if you refund a guest, the service fee is refunded to whoever paid it; and if a guest wins a chargeback, the fee follows the money back the same way. There is currently no per-reservation fee view for deposits and no-show charges, so reconciling those means the Stripe payment breakdown or a reconciliation export with the application-fee column.
What this means for your no-show policy The math still favors having a policy. A $15 no-show fee that loses 30 cents to the platform still recovers $14.70 and, more importantly, changes guest behavior -- card-on-file policies are one of the most effective no-show deterrents there is. The South Philadelphia restaurant in the Inquirer's reporting is a useful blueprint regardless of platform: a 20-minute grace period, three reminder texts, and a courtesy call before any card is charged. That sequence is the policy; the fee is the backstop. Design yours the same way and the service fee becomes a rounding error on charges you rarely make -- see the no-show policy diners actually accept and how to cut no-shows without asking for a card.
The bigger picture: fees on fees The service fee is not a scandal. It is a pattern. Per-cover network fees, plan tiers, payment processing, and now a percentage on the payments layer -- each one defensible on its own, each one a line item that did not exist the year before, and the platform can introduce the next one the same way. That is the structural difference between percentage-based platforms and flat pricing: one scales with your success and changes on the platform's schedule, the other is a number you agreed to. For the full OpenTable picture, start with every fee OpenTable publishes or run your own volume through the OpenTable cost calculator. And if you want the flat version: TableLink runs $10 a month billed annually, $13 month-to-month, with no per-cover fees and no transaction service fees -- because we do not sit between you and your guests' money.