The lunch rush is won or lost a few cents at a time.
Restaurants create many small, card-present payments in a short window. That makes the per-transaction markup, tip workflow and way tabs are closed more important than a blended headline rate suggests.
Target markup, never a promise or guarantee · Final pricing decided by the processor's underwriting department
A cafe month, shown as payments rather than menu items
This example assumes $30,000.00 in card volume at an average payment of $15.00. The calculator derives 2,000 transactions and applies the same count to every model.
The target result is arithmetic, not a quote. It is never a promise or guarantee; the processor's underwriting department determines the account's final markup and approval.
This compares processor markup and monthly fees only. Interchange and card-brand assessments are set by the card networks, apply equally to all providers, and are not included.
One service can create several payment moments
Counter orders
Quick-service tickets put pressure on the fixed charge. A percentage difference may look louder on a rate sheet, but transaction count often decides the cafe's monthly markup.
Open tabs
An authorization should be completed cleanly when the table closes. Duplicate authorizations, abandoned tabs and separate charges create operational work as well as additional payment events.
Tips
The base amount may be authorized before the final tip is known. Staff training and correctly configured equipment matter because a properly adjusted transaction should settle as the intended final amount.
Card-present pricing should reflect a card-present room
A chip or contactless payment at the table generally carries different network economics from an online order. Interchange-plus pricing leaves that distinction visible instead of charging every diner as though the card were absent.
Delivery orders, keyed transactions and stored credentials belong in a separate conversation. If a restaurant mixes those channels, the statement should make the mix legible rather than compressing it into one unexplained rate.
When flat rate is actually better
A weekend stall, seasonal cart or new counter doing only a few thousand dollars in monthly card sales may be better served by a flat-rate reader. Avoiding formal setup can be worth more than optimizing a small processing statement.
That answer changes as transaction count becomes steady. Use the calculator with the average payment customers actually make, not the average table check before split tender.
Questions from behind the counter
Can a holiday weekend trigger a funding review?
Yes. A sharp departure from normal volume or ticket size can trigger the processor’s risk controls. Pcnaid does not underwrite, fund transactions or promise that funds will never be held.
What happens if a terminal fails during service?
The support front line is an AI voice agent that records and triages the issue before routing it. Funding, holds and account-balance decisions must go to the processor because only the processor can act on them.
Does every restaurant receive the target markup?
No. The target is never a promise or guarantee. The processor’s underwriting department sets final pricing from the restaurant’s application, history and risk profile.
Price the payments that actually cross your counter.
Use settled card volume and the average charged ticket. If guests commonly split checks, account for the payments rather than the number of tables.
Applying carries no obligation. Underwriting, approval and final rates are determined by the processor.
Not sure this is the right account? See every way to apply →