Key takeaways
- San Francisco restaurants live with service charges and mandate fees; SB 478 and the restaurant-specific rule govern how they appear on the menu.
- Card-present sales are cheap and safe; delivery and reservation deposits are where disputes come from.
- Interchange-plus pricing and tip-on-device keep effective rates down.
Restaurants payment processing in San Francisco has a set of quirks that operators in other cities never encounter. A taqueria in the Mission, a dim sum house on Clement, a tasting-menu restaurant in Hayes Valley, a bar in SoMa and a cafe in the Sunset all deal with service charges tied to the city's health-care mandate, some of the highest labor costs in the country, delivery apps that own the customer relationship, and reservation deposits that no-show diners dispute. This guide walks through the payment decisions that matter for a San Francisco restaurant.
Service charges, mandate fees and SB 478
Many SF restaurants add a percentage charge to cover the city's Health Care Security Ordinance obligations or to fund service-included pay models. California's SB 478, effective July 2024, requires advertised prices to include mandatory fees, and a follow-up law carved out specific treatment for restaurants that clearly and conspicuously display mandatory charges on the menu. The details of what counts as clear display, and how it interacts with San Francisco's own disclosure rules for surcharges, are exactly the kind of thing to confirm with counsel and check against the current rule rather than assume. From a processing standpoint, a service charge is part of the sale amount, not a tip, and is taxed and reported differently. Set your POS to keep them separate.
Card-present is your friend
Dine-in and counter sales with tap or chip carry the lowest interchange and shift fraud liability to the issuer. Tipping on the device at the time of sale, rather than adjusting after the batch, avoids interchange downgrades on some card types and matches what the guest signed. Pay-at-table and QR-code ordering reduce the number of card-not-present transactions and speed table turns on a Friday in North Beach. Ask for card processing hardware with an offline mode; connectivity in a basement kitchen on Grant Avenue is not reliable.
Delivery apps and your own online ordering
Orders that come through third-party apps are the app's transactions, and the disputes are theirs to fight, though you eat the refunds through their policies. Orders through your own website are card-not-present transactions on your merchant account, which is where restaurant chargebacks concentrate: order not received, wrong items, not recognized. Use hosted checkout with AVS and CVV, name the descriptor exactly as the restaurant is known, text an order confirmation, and keep the delivery photo. If you offer a subscription, a monthly wine club or a meal plan, California's Automatic Renewal Law requires clear consent and easy cancellation.
Reservation deposits and no-show fees
Prepaid tasting menus and cancellation fees are common at the high end and generate disputes from guests who did not read the terms. To win those, the terms must be presented before the card is entered, acknowledged with a checkbox, and repeated in the confirmation. Charge the fee as a separate, clearly described transaction. Keep the reservation log. And keep the total dispute ratio far below the 0.9-1 percent range where Visa and Mastercard monitoring programs begin, since fine dining's low transaction counts mean a few disputes move the ratio quickly.
Pricing model for restaurants
Interchange-plus is the structure to ask for. A restaurant's card mix is heavy on debit and mid-tier credit, and a flat rate charges all of it as if it were premium rewards. Ask for the markup separately and audit the first statement against published interchange. Watch for PCI non-compliance fees, statement fees, and equipment leases; a leased terminal package for a three-station restaurant can cost thousands over a term. Restaurants that change concepts or move, common in this city, should avoid contracts longer than the lease.
Tips, labor and settlement timing
Card settlements land in 1-2 business days, which matters when tips are paid out on the next shift. Some restaurants pay card tips through payroll to avoid cash handling; check how your POS reports tips per employee and per day. Ask the processor for the batch cutoff time, since a late close on Saturday can push weekend funds to Tuesday. For catering and private events billed to companies, invoices with payment links that accept ACH cost a flat fee and settle in 1-3 business days with no card chargebacks. A one-way push into QuickBooks reconciles sales, tips, service charges and fees without a spreadsheet.
Data and compliance
Online ordering collects customer data, so CCPA and CPRA apply above certain thresholds; use hosted payment fields so card numbers never touch your server, and complete the annual PCI questionnaire. Restaurants have been targets for POS malware in the past; keep terminals updated and on a segmented network.
San Francisco restaurants operate under more rules and thinner margins than almost anywhere, and the processing setup should reflect that: inclusive, clearly displayed pricing, cheap card-present acceptance, careful handling of deposits and online orders, and a contract that will not outlive the lease.
Ready to get set up with Flux?
Cards, ACH, and stablecoins in one platform, with volume-based pricing. No setup fees or contracts.
Get Started