Payments for Restaurants: What Stripe, Square, Toast, and Clover Really Cost You

The short version: a restaurant doing $50,000 a month in card sales pays $14,000 to $21,000 a year in processing fees — roughly a full-time line cook's salary, handed to companies whose generic pricing pages never mention restaurants. Add delivery-app commissions of 15–30% and the number gets ugly fast.

This guide does the math the big processors will not: their real published rates computed against real restaurant tickets ($25 quick-service, $60 casual, $200 fine dining, the $2,000 catering deposit), the POS lock-in traps, and the workflows their pages ignore — tip adjust, split checks, catering chargebacks, and cash discounting. None of them will ever write "payments for restaurants." We just did.

The one number: fees as a line cook's salary

Take a single-location restaurant doing $50,000 a month in card volume — a busy casual spot, not a flagship. At an effective rate between 2.4% and 3.5%, depending on your mix of in-person, online, and keyed-in transactions, you pay $1,200 to $1,750 a month in processing fees. That is $14,400 to $21,000 a year.

For scale: that is roughly what a full-time line cook costs you. Every year, you hand a line cook's salary to a processor whose website has never once addressed a restaurant's actual workflow. The processors are counting on you never doing this division. Now you have.

And that is before delivery. Two hundred DoorDash orders a month at a $35 average ticket is $7,000 in sales. On the 25% Plus plan, that is $1,750 a month — $21,000 a year — in commission alone, before your food cost and labor touch the order. The commission is not a fee. It is a second rent check that grows every time you get busier.

The fee table: every big processor, computed against your tickets

Published rates, checked October 2026. Per-transaction cost = rate × ticket + fixed fee. No processor's marketing page will show you this table — now you know why.

• $25 quick-service ticket (in person): Stripe $0.73 (2.7% + $0.05) · Square Free $0.80 (2.6% + $0.15) · Toast POS plan $0.77 (2.49% + $0.15) · Clover/Fiserv $0.68 (2.3% + $0.10)
• $60 casual ticket (in person): Stripe $1.67 · Square Free $1.71 · Toast POS plan $1.64 · Clover/Fiserv $1.48
• $200 fine-dining ticket (in person): Stripe $5.45 · Square Free $5.35 · Toast POS plan $5.13 · Clover/Fiserv $4.70
• $35 direct online order: Stripe $1.32 (2.9% + $0.30) · Square Free $1.46 (3.3% + $0.30) · Toast $1.38 (3.5% + $0.15) · Clover $1.33 (3.5% + $0.10)
• $2,000 catering deposit (keyed in): Stripe $68.30 (3.4% + $0.30) · Square Free $70.15 (3.5% + $0.15) · Toast $70.15 (3.5% + $0.15) · Clover $70.10 (3.5% + $0.10)

Three things jump out. First, Clover wins every in-person row — Fiserv's 2.3% + $0.10 is the cheapest published counter rate of the big names. Second, Square's 3.3% online rate on the Free plan is the silent killer — it quietly taxes every direct online order you fought DoorDash to win back. Third, keyed-in catering deposits converge around 3.5% no matter who you use — a $70 fee on a $2,000 deposit — which means the deposit workflow matters more than the rate: get the card on file properly (more below) instead of typing numbers into a terminal.

At $50,000/month in card volume with a ~$60 average ticket (about 830 transactions), the monthly totals come out roughly: Stripe ~$1,390 · Square Free ~$1,430 · Toast POS plan ~$1,340 plus $69/month software · Clover ~$1,220 plus $89.95–$109.90/month software. Clover's software fee eats half its rate advantage — but only half.

For the AI tools that cut the labor and waste behind these numbers, see AI for Restaurants.

Your POS and your processor are different things (until they trap you)

This is the distinction the industry hopes you never learn. The POS is the software your staff touches — menus, tickets, tables. The processor is who moves the money and takes the cut. They can be separate. The big names would prefer they are not.

• Toast: the hostage situation. Toast's POS is arguably the best front-of-house software in the business. It also requires Toast Payments — you cannot bring your own processor or shop your rates. The POS plan is $69/month with 2.49% + $0.15 in person (when you buy hardware upfront); the $0/month Starter Kit pushes you to 2.99–3.69% + $0.15. Contracts run 2–3 years with early termination fees, and Toast's agreements let them raise processing rates mid-term — which they did in March 2026. Great software; read the handcuffs before you sign.
• Clover/Fiserv: the contract situation. Best published in-person rate (2.3% + $0.10 on restaurant plans), but hardware-and-software bundles from dealers routinely come with 36-month processing commitments, and pricing varies by who sells it to you. Buy direct from Clover and get everything in writing.
• Square: the bundle. Free to start, 2.6% + $0.15 in person, and the POS, processor, and hardware all come from one company — which is convenient until your volume grows and the flat rate, the 3.3% online rate, and the aggregated-risk account reviews start costing you real money.
• Stripe: the processor with no restaurant. Excellent rates and the best API in the business — and zero front-of-house workflow. Nobody runs a dining room on Stripe Terminal alone. Stripe belongs in your online-ordering stack, not at your host stand.

Underneath all of them is the same plumbing: interchange (the card networks' cut, set by Visa/Mastercard) plus the processor's markup. Flat-rate pricing bundles both into one number — simple, and profitable for the processor once your volume grows. Interchange-plus passes through the real interchange cost and adds a fixed markup (often around 0.3–0.5% + a few cents). At $50,000/month, that difference is hundreds of dollars a month. If you want to understand how that plumbing actually works, Finix publishes some of the clearest payments-infrastructure documentation in the industry — it is written for developers, but the concepts (tokenization, interchange, risk rules) are exactly what your processor is charging you for.

The workflow checklist the big processors fail

Rates are half the story. The other half is whether the money moves the way a restaurant actually works. Run any processor through this checklist:

• Tip adjust. The card is authorized before the tip is known, then adjusted after. Every restaurant POS handles this natively; generic processors treat it as an edge case. If your processor cannot do pre-auth plus tip adjust cleanly, it is not a restaurant processor.
• Split checks and tip pooling. Six ways to split a $400 check, and a tip pool across 14 staff at close. Your POS does the math; your processor has to settle it without mangling the batch. (7shifts even sells a tip-pooling add-on at $24.99/month per location — the problem is real enough to be a product.)
• Card-on-file for regulars, tabs, and catering. The bar tab that walks out, the catering deposit, the private-event balance. You need stored cards you can charge later without re-keying — tokenized, not written on a sticky note in the host stand drawer (which is a PCI violation, by the way). See the Finix how-to below.
• Catering chargebacks. A $5,000 wedding invoice disputed six weeks later. Your defense is the signed banquet event order, the deposit receipt, and the final headcount confirmation — paperwork the processor never asks about until the dispute lands. Processors with no restaurant workflow leave you assembling this alone.
• Direct online ordering vs. the apps. DoorDash takes 15% (Basic), 25% (Plus), or 30% (Premier) per delivery order; pickup is ~6%. Your own ordering page through Toast, ChowNow, or DoorDash Storefront (2.9% + $0.30 per order) keeps the customer data and the margin. The math: a $35 order costs you $10.50 on DoorDash Premier vs. ~$1.32 on your own site. You do not need to leave the apps — you need them to be your discovery channel, not your cash register.
• Offline mode. Internet dies on a Saturday night. Toast and Clover both process offline and sync later; know exactly what yours does before you find out mid-rush.

How card-on-file actually works (from Finix's public docs)

Every restaurant needs stored cards — bar tabs, catering deposits, the regular whose "usual" you charge on Fridays. Most do it wrong: card numbers in a drawer, in a spreadsheet, or re-keyed at 3.5% every time. Here is how the infrastructure underneath actually works, drawn from Finix's public developer documentation (docs.finix.com), translated into restaurant operations.

• Step 1: the card never touches your systems. The guest's card goes into Finix's hosted tokenization form — an iframe rendered by Finix inside your page. Your website and your staff never see the number, which is what keeps the restaurant out of PCI scope. Finix's docs are blunt about this: creating payment instruments via raw API is for testing only; production must use their hosted fields or JavaScript client.
• Step 2: the token becomes a stored instrument. Submitting the form returns a token (it starts with TK). Your backend claims that token and creates a Payment Instrument tied to the guest's Buyer Identity — one guest, one identity, as many stored cards as they need. That is the entire architecture of "we have your card on file."
• Step 3: verify before the big charge. Before you run the $5,000 wedding balance, run a $0 authorization against the stored instrument. Finix returns address_verification and security_code_verification results — you learn the card is good before the event, not while the bride's father is watching you decline.
• Step 4: include the billing address when you tokenize. This one is straight from Finix's risk-rules guide: including an address when tokenizing a card can lower interchange on the transaction. It is free money for thirty seconds of data entry — take the ZIP code with the deposit.
• Step 5: plan for expired cards. Cards expire; weddings do not reschedule. Use the account updater to refresh stored cards automatically instead of calling the client for new numbers two days before the event.

The restaurant translation: take the 50% catering deposit when the contract is signed (card tokenized, address captured, $0 auth verified), and the balance charges itself the Monday after the event. No re-keying at the keyed-in penalty rate, no sticky notes, no "the card declined and the event is Saturday" panic. That is what the infrastructure is for — the processors just never explain it in your language. (Finix's risk-rules and card-checks guide is public at docs.finix.com if your developer wants the source.)

Flat vs. interchange-plus vs. cash discount — and the law

Three ways to pay less, in ascending order of awkwardness.

• Interchange-plus. The honest model: real interchange cost plus a fixed markup. At $50,000/month, it beats every flat rate in the table above. Who offers it: independent processors like Helcim (interchange + 0.4% + $0.08 in person), subscription models like Stax, and Clover setups through authorized resellers who will put you on interchange-plus instead of Fiserv's flat 2.3%. Toast and Square will not offer it to you — that absence tells you who it favors.
• Cash discounting. The menu shows the card price; cash customers get a discount. Legal in all 50 states under the Durbin Amendment, because you are discounting cash, not penalizing cards. At a taco truck or a busy QSR where 20–30% of sales are cash, this can erase most of your processing bill.
• Surcharging. Adding a fee on top for card payments. Legal in most states but banned in Connecticut, Massachusetts, and Maine (as of late 2026), capped by the card networks at 3% — and it can never exceed your actual processing cost — and never allowed on debit cards, no matter how the customer runs it. Colorado caps it at 2%, Illinois at 1%. You must disclose it before the sale, on signage and on the receipt as its own line item.

The fine-dining caveat: a 3% "card fee" line on a $400 anniversary dinner reads very differently than on a $12 lunch. Plenty of upscale rooms quietly build processing into menu prices and offer the cash discount as a grace note instead. Know your room.

The honest verdict on each big processor

• Stripe: fine for the online-ordering API behind your website; wrong as your counter processor. No restaurant workflow, no tip adjust culture, no POS. Use it where it is strong and keep it away from the host stand.
• Square: the best day-one choice for a café, food truck, or first location — free to start, honest hardware, no contract. The worst long-term choice at volume: the 3.3% online rate punishes the direct ordering you need, and flat-rate simplicity gets expensive past ~$30,000/month.
• Toast: the best front-of-house software and the most expensive relationship. Budget the real cost — most restaurants land at $150–$300/month once KDS, online ordering, and payroll are added — negotiate hard at volume, and go in knowing you cannot leave the payments behind if you leave the software.
• Clover (Fiserv): the cheapest counter rate and the heaviest paperwork. Buy direct, get the 36-month terms in writing, and do not run catering deposits through the keyed-in rate without a card-on-file workflow.
• Adyen, Chase Payment Solutions, Global Payments, Worldpay: quote-based, enterprise-led, and — as of October 2026 — zero restaurant-specific guidance published anywhere. Fine if you are a group with a payments person on staff. A maze if you are an independent owner reading pricing PDFs at midnight.

Do this in order

• This week: read your statement. Find your effective rate — total fees divided by total card volume. If you cannot find it in five minutes, that is the first problem.
• This month: launch direct ordering. A "order direct" button on your site through Toast, ChowNow, or DoorDash Storefront. Every order that moves off the 25–30% apps is a 20-point margin swing.
• This month: fix deposits. Card on file at booking for catering and large parties — tokenized, address captured, $0 auth verified. Stop paying the keyed-in penalty on money you already earned.
• This quarter: re-shop your processing. Take the fee table above to your current provider and to two competitors. At $50,000/month you have leverage — use it. If you are on Toast, negotiate the rate; if you are on Square Free at volume, price the Plus plan or an interchange-plus quote against it.

The processors are betting you will never do step one. Prove them wrong.

Payment processing is the only vendor that charges you more every time you succeed. Treat it like food cost: measure it monthly, question it quarterly, and never let the company that sells you the cash register also set the price of using it without a fight.

Next: AI for restaurants, the restaurant tech stack, and the restaurants hub.