Payment Processing Fees Explained: Interchange, Markup, and Monthly Costs

Overview

If you accept card payments online, your total cost is rarely just one flat rate. Even simple pricing plans sit on top of several moving parts: interchange paid through the card networks, assessment or network-related costs, processor markup, gateway or platform fees, and occasional monthly or event-based charges. For many merchants, the confusion starts because providers present these costs in different formats.

The safest evergreen way to think about payment processing fees is to separate them into three layers:

• Wholesale costs: charges tied to the payment ecosystem itself, typically including interchange and network-related fees.
• Processor markup: what the processor, merchant account provider, or payment gateway adds for access, risk handling, support, and margin.
• Operational fees: monthly platform charges, PCI programs, chargeback fees, payout fees, cross-border surcharges, and other line items that depend on your setup.

That structure matters because not all fees are equally negotiable. Interchange usually follows card type and transaction characteristics. Processor markup is often the part you can compare and negotiate. Operational fees depend on the product stack you use, such as a hosted checkout, recurring billing tools, wallet payments integration, fraud tooling, or multi-currency checkout support.

It also helps to remember how online payment processing works at a high level. A payment system verifies and authorizes a transaction first, then settles funds later through banks, card networks, and service providers. As the source material notes, authorization is fast, but settlement may take days. That timing can affect not just cash flow, but fees tied to payouts, reserves, or risk review. For a deeper operational view, see Settlement Times Explained: How Different Rails Affect Cash Flow and Reconciliation.

In practical terms, merchants usually encounter four common pricing models:

• Flat-rate pricing: one published rate for most transactions, often easiest to forecast but less transparent.
• Interchange plus pricing: interchange passed through, plus a fixed processor markup.
• Tiered pricing: transactions grouped into buckets such as qualified or non-qualified, which can be harder to audit.
• Custom enterprise pricing: negotiated blends that may include gateway, fraud, and acquiring fees under one contract.

For many small and mid-sized businesses, interchange plus pricing is the clearest model for understanding what you are paying for. It does not always guarantee the lowest total bill, but it usually makes cost drivers more visible.

How to estimate

The goal here is simple: turn a pricing quote or merchant statement into an effective rate and a monthly cost estimate you can revisit. You do not need every underlying network rule to do this well. You just need a repeatable worksheet.

Start with this formula:

Total monthly payment cost = variable transaction fees + fixed monthly fees + event-based fees

Break that down further:

1. Variable transaction fees
   This includes percentage-based charges on volume, per-transaction authorization fees, and any category-specific surcharges. For card payments, this is where interchange, assessments, and processor markup usually appear.
2. Fixed monthly fees
   This may include gateway access, merchant account fees, statement fees, PCI DSS compliance program fees, recurring billing platform fees, account updater access, or support subscriptions.
3. Event-based fees
   These are triggered by specific events such as chargebacks, refunds, retrieval requests, failed payouts, cross-border cards, currency conversion, or manual review.

Then calculate your effective rate:

Effective rate = total payment costs / total processed sales volume

This is the cleanest top-line benchmark because it converts a messy statement into one comparable number. However, it only becomes useful when you also note the assumptions behind it. A 3.1% effective rate may be good for a low-ticket subscription business with high fraud controls, and poor for a low-risk B2B merchant with large tickets.

Use this step-by-step approach:

1. Pull one to three recent months of statements.
2. Record total card volume, transaction count, refunds, and chargebacks.
3. Separate card-present, card-not-present, domestic, and international volume if relevant.
4. List every recurring fee outside the processing rate.
5. Identify one-time or event fees and average them monthly if they happen regularly.
6. Divide total costs by total processed volume to get your effective rate.
7. Run a second version excluding unusual one-offs, so you have both a normalized and all-in rate.

If you are evaluating a new payment gateway or merchant account, apply their quote to your own transaction mix instead of using their sample scenarios. Quotes that look cheaper for a hypothetical merchant may become more expensive once you include your own average order value, refund rate, and percentage of premium or rewards cards.

For merchants considering multiple providers, it can help to compare three cost views side by side:

• Advertised rate: what the provider markets publicly.
• Quoted all-in cost: advertised rate plus monthly and event fees.
• Observed effective rate: what you would likely pay using your actual volume mix.

This is also where hidden cost tradeoffs appear. A processor with slightly higher markup may still be cheaper overall if it reduces fraud losses, lowers chargeback volume, or improves authorization performance. Pricing should be read together with risk and operational outcomes. Related reading: Chargeback Prevention Playbook: Operational Controls, Dispute Workflows, and Evidence Collection and Payment Gateway Comparison Framework: How to Choose the Right Provider for Your Business.

Inputs and assumptions

A reliable estimate depends less on perfect precision and more on using the right inputs. These are the variables that usually matter most in credit card processing fees and broader merchant services pricing.

1. Monthly sales volume

Higher volume can improve negotiating leverage, especially on processor markup or fixed platform fees. But volume alone is not enough. A provider will also care about your risk profile, business model, and transaction quality.

2. Average ticket size

Per-transaction fees hit low-ticket merchants harder. A business that processes many small purchases may find that a low percentage rate still produces a high effective cost once authorization fees are included. Large-ticket merchants often care more about percentage-based fees and chargeback exposure.

3. Transaction count

Two merchants with the same monthly volume can pay very different amounts if one processes 500 transactions and the other processes 20,000. Always model volume and count together.

4. Card-present vs card-not-present mix

Online businesses usually pay more than in-person businesses because card-not-present payments carry more fraud risk and often require additional tools such as 3D Secure 2, device checks, or advanced screening. Since this article is focused on merchant payment processing online, most readers should assume a higher-cost environment than a countertop terminal setup.

5. Domestic vs international share

International cards, multi-currency acceptance, and cross-border settlement can add costs beyond standard domestic processing. These may include cross-border assessments, FX conversion spreads, or country-specific acquiring fees. If international sales matter to you, model them separately instead of blending them into one average. See also Real-Time Payments Guide for an adjacent view of rail selection and risk.

6. Card mix

Not all cards cost the same. Consumer debit, basic credit, premium rewards, corporate, and commercial cards can produce different fee outcomes. When providers quote a single headline number, that number may assume a card mix that does not match your customer base.

7. Fraud and chargeback profile

Processors do not only price payments; they price risk. A merchant with elevated disputes, high refund levels, subscription rebills, or digital-goods exposure may face higher markup, rolling reserves, or tighter settlement controls. Chargeback fees can be small compared with the underlying cost of lost goods, labor, and future risk reclassification. Review Building a Transaction Monitoring Program and Payment Security Best Practices if you are trying to lower this part of your cost base.

8. Checkout and platform stack

Your payment API, gateway setup, token vault, subscription engine, and fraud tools can add software fees beyond acquiring. Some providers bundle these. Others charge separately. This matters especially for recurring billing, saved cards, and account updater services. Tokenization can reduce security scope and improve customer experience, but it may also be part of a paid platform layer; see Payment Tokenization vs Encryption: What Payments Teams Need to Know.

9. Compliance costs

PCI DSS compliance is not just a checkbox; it can show up as direct fees, questionnaire support costs, scanning requirements, or indirect operational work. If a provider advertises a low rate but charges extra for PCI programs, fraud tools, or wallet support, your all-in comparison can shift quickly.

10. Settlement and payout terms

Fast funding, weekend payouts, instant settlement options, or reserve requirements may affect the economics even if they do not appear as a simple transaction fee. The source material highlights that authorization and settlement are distinct stages. That is a useful reminder: payment cost is not only about acceptance, but also about when and how funds actually arrive.

As a rule, document your assumptions in a short table before comparing providers:

• Monthly volume
• Monthly transaction count
• Average order value
• Domestic/international mix
• Refund rate
• Chargeback rate
• Subscription vs one-time payments
• Needed features: wallets, ACH, invoicing, multi-currency, tokenization
• Current fixed monthly fees

Without those inputs, most pricing conversations drift toward headline rates that are not decision-grade.

Worked examples

These examples use simple math rather than live market pricing. The point is to show how to estimate, not to publish universal fee benchmarks.

Example 1: Small ecommerce merchant on a flat-rate plan

Assume a merchant processes $40,000 per month across 800 online transactions, with one provider charging a flat percentage plus a fixed fee per transaction, along with a small monthly gateway subscription.

To estimate:

1. Multiply monthly volume by the percentage fee.
2. Multiply transaction count by the per-transaction fee.
3. Add the gateway fee.
4. Add average monthly chargeback or refund-related fees if they are recurring.

If the resulting cost equals $1,320 on $40,000 in volume, the effective rate is 3.3%. That gives you one usable benchmark. If a second provider quotes interchange plus pricing, you would compare its expected all-in cost against the same $40,000 and 800-transaction pattern.

Example 2: Merchant comparing flat-rate vs interchange-plus

Suppose a business with mostly domestic consumer cards receives two offers:

• Provider A: flat-rate pricing with no monthly fee
• Provider B: interchange plus a processor markup and a monthly platform fee

Provider A may look simpler and cheaper at low volume because there is no monthly commitment. Provider B may become cheaper as volume grows, especially if the markup is modest and the merchant has a favorable card mix. To decide, the merchant should estimate total monthly cost at current volume and again at projected volume six months out. That second calculation matters because fixed monthly fees become less significant as volume scales.

Example 3: Subscription business with elevated operational fees

A SaaS company processing recurring billing often focuses only on the core acceptance rate, but its real cost may include account updater tools, failed-payment recovery, fraud screening, and chargeback handling. In that case, a quote that appears more expensive on pure processing can still be economical if it improves retention or reduces involuntary churn. For subscription merchants, measure cost per successful collected dollar, not just payment processor costs per attempted transaction.

Example 4: Cross-border merchant

A merchant selling internationally may see three additional cost layers: international card surcharges, currency conversion costs, and higher fraud management spend. If this merchant compares only domestic headline rates, the estimate will be too low. A better approach is to run separate effective-rate calculations for domestic and international segments. That exposes whether an international payment gateway or local acquiring setup might improve results.

Across all examples, the same lesson holds: use your own inputs, convert all fees into monthly totals, and compute an effective rate. Then review whether the provider’s service level justifies the cost. If two options are close, the one that gives better reconciliation, fewer failed payments, and clearer reporting may be worth more than a tiny rate difference. For teams doing regular cost reviews, Transaction Analytics for Decision Makers is a useful companion, as is Reducing Transaction Fees: Practical Strategies for Merchants and High-Volume Traders.

When to recalculate

You should revisit your payment fee model whenever the underlying inputs change. This is the main reason to keep a reusable worksheet instead of treating processor pricing as a one-time setup task.

Recalculate when any of the following happens:

• Your monthly volume rises or falls materially.
• Your average order value changes.
• Your business adds subscriptions, prepaid plans, or installment options.
• Your international sales mix grows.
• Your refund or chargeback pattern shifts.
• You adopt new fraud tooling, tokenization, or wallet payments integration.
• You change gateways, acquirers, or your merchant account structure.
• Published pricing, markup, or network cost inputs move.
• Your settlement schedule or reserve terms change.

A practical review cadence is quarterly for active online merchants, and immediately after any contract amendment or product expansion. Keep a simple spreadsheet with these tabs:

1. Volume inputs: sales, count, average ticket, region mix.
2. Provider fees: percentage fees, per-transaction fees, monthly fees, event fees.
3. Risk costs: chargeback fees, dispute losses, fraud tooling spend.
4. Output: total monthly cost, effective rate, normalized rate, and notes.

Before renewing or renegotiating with a payment processor for small business or a larger enterprise provider, ask for pricing in a format you can map into that worksheet. If the provider cannot explain what is wholesale cost, what is markup, and what is optional platform spend, comparison will remain difficult.

To make this article actionable, use this five-step review checklist:

1. Pull your last three statements and one recent month of order data.
2. Calculate your all-in effective rate and your normalized effective rate.
3. List every fee that is not part of the advertised processing rate.
4. Identify one operational improvement that could reduce cost indirectly, such as better fraud controls or cleaner retries on recurring billing.
5. Re-run the model before signing any new gateway or merchant account contract.

The best pricing decision is not always the lowest headline rate. It is the arrangement that produces predictable acceptance, manageable risk, clear reconciliation, and a cost structure you can explain line by line. Once you build that habit, payment statements stop being a black box and become another operating metric you can actively manage.