A restaurant can know its processor’s advertised rate and still not know what card acceptance actually costs.
The statement may contain percentage charges, per-transaction fees, card-type differences, authorization or network charges, monthly account fees, chargebacks, refund effects, equipment or gateway fees and separate online-ordering costs. Deposits may arrive net of fees or fees may be debited later.
The most useful management number is the effective payment cost for the period: total relevant processing cost divided by the card sales volume being analyzed.
Start with a clean period
Use one processor statement period and reconcile it to the same period’s POS/card sales as closely as possible. Mixing a calendar-month P&L with a processor cycle that cuts off several days earlier can create apparent differences that are only timing.
Calculate the effective rate
Effective processing rate = total included processing fees ÷ card payment volume × 100.
Illustrative example: if a restaurant processes $120,000 in card payments and the included processor costs for that same scope are $3,420, the effective rate is 2.85%.
That example is not a benchmark. The purpose is to create a comparable internal measure using the restaurant’s actual statement.
Define what is included
Before comparing periods or processors, decide which costs belong in the numerator.
- Percentage-based processing fees.
- Per-transaction charges.
- Network, assessment or similar pass-through charges shown on the statement.
- Gateway or payment-platform fees if they are part of card acceptance.
- Monthly statement/account fees tied to payment processing.
- Chargeback fees where management wants them included in the payment-cost view.
- Equipment/software fees only if the analysis deliberately treats them as payment cost.
Keep the definition consistent. A comparison is unreliable if one month includes the gateway fee and the next does not.
Separate processing cost from POS software cost
A bundled vendor may invoice payments, POS subscription, online ordering and hardware together. Separate the payment-processing component from software and equipment when possible.
That lets management compare payment economics without pretending the entire technology stack is a card fee.
Reconcile gross card sales to deposits
| Step | Control question |
|---|---|
| POS card sales | What card volume did the restaurant record? |
| Processor settled volume | What volume did the processor accept/settle? |
| Refunds/adjustments | Which transactions reduced settlement? |
| Processor fees | Were fees withheld from deposits or billed separately? |
| Net deposits | What actually reached the bank? |
| Timing items | Which batches settled in a different bank/accounting period? |
The deposit should be explainable even when it does not equal gross card sales.
Understand per-transaction cost
A flat charge per transaction affects concepts differently. A high-ticket restaurant processes fewer transactions for the same sales volume than a low-ticket counter-service concept.
Track average card ticket and transaction count so the manager can see how much of cost comes from transaction frequency versus percentage fees.
Analyze channel mix
Dine-in, keyed/manual entry, direct online ordering and third-party channels can have different payment economics.
Create an effective-rate view by channel where the data are available and the fee allocation is reliable. Do not force a channel allocation if the statement does not support it.
Review debit, credit and card mix only with real statement data
Different card types and transaction methods can affect processor cost, but the restaurant should use its own processor reporting rather than general assumptions.
The management question is not which card is “expensive” in theory. It is which transaction mix and fee components actually drive this restaurant’s statement.
Separate refunds from fees
A refund can reduce net sales or settlement while some transaction fees may not reverse in the same way. Read the processor statement and contract rather than assuming the economics.
For management, track refund volume and associated payment cost separately from normal sales when it is material.
Track chargebacks as an exception
Chargebacks can create the transaction loss, a fee and management time. Do not bury repeated chargebacks inside the normal effective rate without also monitoring their cause.
Group chargebacks by channel and reason where reliable data exist. Repeated online-order disputes may require a different control than an isolated in-person dispute.
Watch monthly and minimum fees
Fixed fees have greater percentage impact in low-volume months. That means the effective rate can rise even when the processor’s variable pricing did not change.
Separate fixed and variable components so the manager understands why the rate moved.
Calculate cost per transaction
Payment cost per transaction = included processing cost ÷ settled transaction count.
This is useful when comparing order channels or concept types, but it should be read with average ticket. A high cost per transaction can still be efficient if the average sale is much higher.
Build a monthly payment-cost bridge
| Driver | Question |
|---|---|
| Card sales volume | Did more sales move to card? |
| Transaction count | Did frequency change? |
| Average ticket | Did ticket size change? |
| Channel mix | Did online/manual transactions grow? |
| Rate/fee changes | Did the processor change pricing? |
| Refunds/chargebacks | Did exceptions increase? |
| Fixed fees | Did volume fall while monthly fees stayed constant? |
Compare processors on total cost, not headline rate
When evaluating a proposal, model the restaurant’s actual monthly volume, transaction count, average ticket and channel mix. Include all known recurring fees under the proposed structure.
A lower advertised percentage can be offset by higher transaction charges or additional platform fees. A higher stated rate can still be competitive if it includes services currently billed elsewhere.
Normalize a proposal before comparing
1. Use the same recent card-sales volume.
2. Use the same transaction count.
3. Separate in-person and online/manual volume if pricing differs.
4. Add all known monthly and per-transaction charges.
5. Identify hardware or software charges separately.
6. Model any introductory pricing only for its actual duration.
7. Compare total expected dollars and effective rate under the same assumptions.
Do not assume surcharging is a simple cost fix
Rules, card-network requirements, processor capabilities and state/local law can affect surcharging, cash-discount and other fee-recovery models.
If the restaurant considers passing fees to guests, verify the current legal, network and processor requirements that apply to the business before implementation. This article does not provide a universal surcharge rule.
Reconcile to the general ledger
Payment processing expense on the P&L should be explainable from processor statements and other payment vendors. If the accounting line is materially different, check timing, misclassification, bundled software fees and missing statements.
For the deposit side of this check, see Restaurant Bank Reconciliation for Operators: Match Deposits, Cards and Cash to the Books.
Example: why the effective rate moved
Assume total card volume is nearly flat month to month, but the effective payment cost rises. The bridge shows direct online orders increased, transaction count rose while average ticket fell, and two chargebacks appeared.
The correct conclusion is not automatically “the processor raised rates.” Management now has several specific drivers to investigate.
Monthly manager checklist
- Card sales reconcile reasonably to processor settled volume.
- Net bank deposits are explained by settlement, refunds, fees and timing.
- Total processing cost is calculated using a consistent scope.
- Effective rate and cost per transaction are recorded.
- Fixed versus variable fees are separated.
- Channel changes are reviewed.
- Refunds and chargebacks are monitored.
- Any new or unusual fee line has an explanation.
Build a statement fee map
Processor statements can use labels that are difficult for operators to compare. Create a simple fee map that groups each line into percentage/volume charges, per-transaction charges, fixed monthly charges, exception charges and non-processing technology charges.
Keep the original statement line description beside the management category. That preserves traceability while giving the owner a cleaner monthly view.
Separate settlement timing from fee variance
A weekend or holiday can move one or more batches into the next bank period. Before investigating a “missing deposit,” compare batch close time, processor settlement date and bank posting date.
Timing should be documented, not forced into the wrong period by changing POS sales or deposit records. The bank reconciliation can carry the timing item until it clears.
Include tips and service components consistently
Where the processor statement includes authorized amounts, adjusted tips or other settlement components, make sure the denominator used for the effective rate is consistent from period to period. A denominator based on gross card volume should not suddenly exclude a component that was included last month.
The correct treatment depends on the restaurant’s reporting structure and processor data. The key control is consistency and a reconciliation that explains the difference.
Review online-ordering payment stacks
A direct online order may include a payment gateway, ordering-platform subscription and processing fee. A third-party marketplace may settle net of commissions and other charges. Do not compare those channels using a single “card fee” number unless the underlying costs are truly comparable.
For channel profitability, separate payment acceptance from marketplace commission, delivery cost, marketing fees and software subscription.
Create a proposal comparison worksheet
- Current monthly card volume and transaction count.
- In-person versus online/manual volume where relevant.
- Current total processing dollars under the chosen scope.
- Proposed percentage charges and per-transaction charges.
- All recurring monthly fees.
- Gateway, equipment or required software charges shown separately.
- Contract term, pricing-review clauses and any temporary promotional period.
- Estimated total dollars and effective rate using the same operating assumptions.
Watch for fee-category drift
If a processor introduces a new statement line or a bundled provider changes how it labels a charge, do not automatically treat it as normal. Compare the statement with the prior period and ask for an explanation when a material new line appears.
The objective is not to challenge every penny. It is to prevent a recurring fee from becoming permanent simply because nobody noticed the first month.
Use payment cost in channel and menu decisions
Payment cost is usually small relative to food, labor and occupancy, but it can matter when comparing channels with different economics. A direct-order channel and a marketplace channel may produce the same menu revenue while leaving very different contribution after payment and platform costs.
Keep payment fees as one component of the full channel-profitability view rather than treating them as the only reason to prefer a channel.
Assign a monthly owner and evidence package
One role should own the monthly processor review. The evidence package can include the processor statement, POS card-sales summary, settlement report and bank deposits. The owner marks material timing items and unexplained fees before the financial review.
This makes card fees auditable and prevents the P&L line from becoming a number that management simply accepts each month.
Common payment-cost mistakes
Comparing only the advertised percentage
Per-transaction and fixed fees disappear from the decision.
Using bank deposits as card sales
Deposits may already be net of fees and refunds.
Mixing software subscriptions into processing cost without disclosure
Processor comparisons become misleading.
Ignoring transaction count
A concept with many small tickets experiences flat per-transaction fees differently.
Assuming a fee-recovery program is universally allowed
The restaurant can create compliance and guest-trust problems.
Frequently asked questions
What is a good credit-card processing rate for a restaurant?
Use your own statement and comparable processor proposals rather than a universal benchmark. Effective cost depends on transaction mix, card types, channels, ticket size, contract structure and fees.
Should card fees be treated as food cost?
Usually they are analyzed separately from ingredient food cost. Follow the restaurant’s accounting policy and management reporting structure.
Why does the effective rate change every month?
Volume, transaction count, card/channel mix, refunds, chargebacks, fixed fees and processor pricing can all move the result.
Can restaurants charge customers for card fees?
Potentially under certain structures, but implementation depends on current law, card-network rules and processor requirements. Verify those requirements before acting.
Next action
Take the most recent processor statement. Write down settled card volume, total transaction count, every fee line and net deposits. Calculate total included payment cost, effective rate and cost per transaction. Then compare those three numbers with the prior two periods using the same definition.
Related guides: