Interchange-Plus vs Flat-Rate Processing: Which Business Profiles Fit Each?

By Raied Muheisen | Merchant services and Clover POS experience | Last reviewed June 18, 2026

Interchange-plus and flat-rate processing describe how pricing is presented to a merchant. Neither structure is automatically cheapest or best. The useful comparison depends on transaction count, ticket size, card-present and card-not-present mix, card types, monthly fees, software, equipment, contract terms, and how clearly the statement can be reconciled.

How the models differ

Factor	Interchange-plus	Flat-rate
Presentation	Underlying card costs plus stated processor markup	One or several bundled rates for defined transaction types
Statement detail	Usually more line-item detail	Often simpler, but exceptions still matter
Cost variability	Changes with underlying transaction mix	Merchant price may look steadier within qualifying categories
Evaluation need	Verify markup, pass-through costs, fees, and qualification	Verify which transactions receive each rate and all non-rate charges

What interchange-plus means

The provider generally passes through underlying interchange and assessment components and adds a disclosed markup, often a percentage, per-item charge, or both. A proposal is not transparent merely because it uses the term “interchange-plus.” Confirm the markup, monthly charges, gateway, PCI, minimums, equipment, software, chargeback, and other account fees.

What flat-rate means

The merchant pays a stated rate for a defined category, such as an eligible in-person transaction, with separate rates or fees possible for keyed, online, invoice, or other activity. Simplicity can make budgeting and statement review easier, but the headline rate does not reveal the provider’s margin or cover every product and service.

Business-profile comparison

Profile	Questions that matter
Low volume or seasonal	Do monthly minimums and account fees outweigh rate differences?
High transaction count, lower tickets	How large is the per-item component?
Higher tickets or varied card mix	How does the underlying mix change modeled cost?
Mostly card-not-present	Which gateway, token, AVS, keyed, and online charges apply?
Multi-location or software-heavy	Are location, register, user, app, and support costs larger than processing differences?

Use actual business data

Collect several representative statements. Record total sales, transaction count, refunds, chargebacks, card-present and card-not-present volume, total fees, software, equipment, and non-processing charges. Read the statement guide before modeling a new proposal.

A comparison using only volume can miss the transaction-count effect. A comparison using only an effective rate can hide software, equipment, or one-time charges. Use the proposal comparison worksheet to keep assumptions visible.

Questions for an interchange-plus proposal

• What exact markup applies?
• Are assessments and network fees passed through without additional markup?
• Which monthly, annual, PCI, minimum, gateway, and support fees apply?
• Are some transactions priced outside interchange-plus?
• How are refunds and chargebacks treated?

Questions for a flat-rate proposal

• Which transaction types qualify for each stated rate?
• What rates apply to keyed, online, invoice, international, or manually entered activity?
• Which monthly, software, hardware, dispute, or instant-transfer charges apply?
• Can pricing change with plan or volume?
• How is data exported if the business leaves?

Effective rate is a diagnostic, not the entire answer

Dividing total processing-related fees by processing volume can help compare periods, but it must use consistent categories. It does not explain why cost changed, whether software is included, or whether the proposal fits the workflow. Break the difference into price, mix, transaction count, and non-processing services.

Verdict

Interchange-plus can be easier to audit when the markup is clearly stated and the merchant is prepared to review detailed statements. Flat-rate can be easier to operate when its categories and exceptions are understood. The better model is the one that produces an acceptable total cost, clear statement, workable contract, and suitable payment operation for the specific business.

Once a model is selected, use the onboarding checklist. If changing providers, follow the switching guide.

General business education only. Processing prices, rules, and agreements vary.

Re-evaluate the model when the business changes

A pricing structure that fits today may become less suitable after a location opens, online volume grows, ticket size changes, or a software bundle replaces separate services. Review the same normalized categories after a material operating change rather than assuming the original comparison remains valid.

Keep card-network cost changes separate from provider markup changes. When a statement changes, identify whether the cause is transaction mix, sales channel, card type, number of transactions, new services, or an amended provider price.

Break the statement into four cost layers

Pricing becomes easier to compare when every charge is assigned to a layer instead of being treated as one rate.

Layer	Examples	Evaluation question
Transaction economics	Underlying card costs, processor percentage, per-item charges	How does actual channel and card mix affect the total?
Account and compliance	Monthly account, minimum, PCI, statement, support	Which charges remain during a low-volume month?
Technology	Gateway, token, ecommerce, software, apps, integrations	Which capabilities are required rather than optional?
Equipment and implementation	Devices, leasing, installation, replacement, connectivity	What is the full obligation and operating recovery plan?

Profile: seasonal or lower-volume business

Fixed account and software charges can have a larger effect when volume falls. Compare a slow month and confirm monthly minimums, inactivity rules, seasonal closure options, software commitments, and equipment payments. A visually lower processing rate may not offset a heavier fixed-cost stack.

Profile: high transaction count with smaller tickets

Per-item charges matter because transaction count can rise faster than sales volume. Model authorization, gateway, and processor transaction charges using actual counts. Confirm whether declined, refunded, or other transaction events create charges.

Profile: card-not-present or omnichannel

Separate ecommerce, keyed, invoice, recurring, virtual-terminal, and in-person transactions. Document gateway, token, AVS, account updater, fraud tools, and ecommerce platform costs. A flat rate advertised for in-person payments should not be applied to online volume unless the proposal says so.

Profile: software- and equipment-heavy operation

For a restaurant, retailer, or multi-location business, the difference between pricing models may be smaller than the difference in software, apps, devices, installation, and support. Evaluate the complete required configuration and the cost of changing it later.

Effective-rate decomposition worksheet

Period	Sales volume	Transactions	Transaction-related fees	Fixed account fees	Software/equipment	Notes on mix
Month 1
Month 2
Month 3

Calculate an effective rate only after defining which fees are included. Then explain the change: transaction mix, count, volume, fixed fees, technology, equipment, or provider pricing. The explanation is more useful than the percentage alone.

Decision tree

1. Can the provider explain every pricing category in writing?
2. Can the business supply representative statements and transaction counts?
3. Have both models been tested against the same scenarios?
4. Are software, equipment, and contract terms separated?
5. Does the statement remain understandable after implementation?
6. Can the business export data and exit using documented procedures?

If the answer to an early question is no, the proposal is not ready for a winner. Resolve the information gap before debating small rate differences.

Review triggers

Re-run the comparison after a new location, major volume change, ecommerce launch, significant shift in ticket size, new POS software, equipment replacement, acquisition, or provider pricing amendment. Keep the old model so changes can be traced instead of reconstructed from memory.

Run a statement-based pricing test

The most reliable comparison uses the business’s own processing mix rather than a generic monthly volume. Take two or three representative statements, remove account identifiers, and capture monthly volume, transaction count, average ticket, card-present versus keyed or online share, debit share when available, refunds, chargebacks, and every provider-controlled fee.

1. Calculate the current all-in cost for each month.
2. Ask each provider to model the same months and disclose every assumption.
3. Separate pass-through card-brand costs from provider markup where the model allows it.
4. Add software, gateway, device, compliance, statement, batch, and service charges.
5. Test one ordinary month and one difficult month with a different ticket or card mix.

Do not treat a modeled savings figure as guaranteed. It is useful only when the inputs are accurate and the proposal explains what can change.

Operational factors that can outweigh the headline rate

Factor	What to test	Potential consequence
Funding	Cutoffs, weekends, holidays, holds, and deposit reporting	Cash-flow friction even when processing cost is lower
Integrations	Accounting, ecommerce, loyalty, online ordering, and inventory	Manual work or duplicate systems
Support	Hours, escalation, device replacement, and ownership of third-party issues	Longer outages and unclear accountability
Contract	Term, renewal, notice, termination, equipment, and software commitments	Higher switching cost than the monthly quote suggests
Reporting	Batch detail, fees, tender types, locations, and exports	More reconciliation time and weaker cost visibility

Document the pricing decision

Keep a one-page decision record with the statements used, assumptions, excluded costs, expected operational benefits, contract risks, implementation owner, and review date. After launch, compare the first full month with that record. If volume or card mix changed, note the difference before judging the quote. If an undisclosed provider fee appears, escalate it with the signed pricing schedule and modeled comparison.

The right model is the one whose total economics, operating fit, and contract terms remain understandable after the sales presentation ends.

Ask who will explain the first two statements after launch and how billing questions are escalated. Pricing transparency is not only a sales-stage feature; it should remain available when transaction mix changes, new fees appear, or the business adds a location or payment channel.