Online payment processing fees are easier to compare when you separate the costs set by card networks from the markup charged by a provider. This guide explains interchange, assessments, processor and gateway fees, and pricing models, then gives you a repeatable worksheet and worked examples for comparing credit card processing online as your volume, channels, and business model change.
Overview
The amount deposited into your business bank account is not usually the same as the amount a customer pays. A payment may generate several costs before settlement, including card-network charges, a processor or acquiring markup, gateway fees, per-transaction charges, and account or service fees.
These costs are commonly grouped into three layers:
- Interchange: A charge associated with the card transaction and its characteristics, such as card type, transaction method, merchant category, and other qualification details. It is generally passed through the payment ecosystem rather than set solely by your payment provider.
- Assessments: Network-level charges applied to eligible transactions. The exact treatment and labels depend on the network, region, and provider statement.
- Provider markup: The portion retained by the processor, acquirer, payment gateway, or merchant-services provider. This may include a percentage, a fixed transaction fee, gateway access, authorization, settlement, risk, or account-management charges.
The practical goal is not to find one universal “lowest rate.” It is to calculate your effective cost for the payment methods and sales channels you actually use. A provider with a simple flat rate may be easier to budget, while interchange-plus pricing may provide more visibility at sufficient volume. Tiered pricing can be difficult to evaluate when transactions are grouped into categories with different rates or qualification rules.
Also distinguish the merchant account from the payment gateway. The merchant account supports the acceptance and settlement of funds, while the gateway transmits payment data between your checkout and the processing environment. Some vendors bundle both functions; others itemize them.
How to estimate
Start with transaction-level data rather than a headline rate. For a simple monthly estimate, use:
Estimated processing cost = variable fees + per-transaction fees + fixed monthly fees + incidental fees
For a percentage-and-fixed pricing plan:
Variable fees = monthly card volume × percentage rate
Per-transaction fees = number of transactions × fixed fee
Then calculate your effective rate:
Effective rate = total payment costs ÷ gross payment volume × 100
For a provider comparison, build one row for each payment method and channel. Record gross volume, transaction count, average order value, refund volume, chargeback activity, currency, and whether the transaction is card-present or card-not-present. Apply each provider’s quoted components to the same inputs. This avoids comparing one provider’s all-in estimate with another provider’s percentage alone.
When a quote uses interchange-plus pricing, model the pass-through portion and the provider markup separately. When a quote uses flat-rate pricing, use the stated blended percentage and fixed fee, but ask whether other costs sit outside that rate. For tiered pricing, request the qualification rules and historical transaction analysis before relying on the advertised categories.
A useful payment processing cost calculator can be a spreadsheet with these columns:
- Payment channel and method
- Monthly volume
- Monthly transaction count
- Average transaction value
- Percentage-based cost
- Per-transaction cost
- Monthly and annual account fees
- Gateway, currency, refund, dispute, and payout fees
- Total cost and effective rate
Use the same forecast for every provider. Run at least three scenarios: current volume, expected growth, and a lower-volume month. Pricing that looks attractive in one scenario may not remain attractive when fixed fees or transaction counts change.
Inputs and assumptions
Before comparing merchant services pricing, define the assumptions that can materially change the result.
Volume and transaction count
Monthly volume and transaction count are separate inputs. Two businesses can process the same dollar volume but pay different totals if one has many small transactions and the other has fewer large orders. Fixed per-transaction fees have a larger effect on low-value orders.
Payment mix
Separate domestic cards, international cards, debit, digital wallets, bank payments, and other methods where your provider prices them differently. A recurring billing payment gateway may also apply separate rules to stored credentials, retries, or subscription transactions. Do not assume that every payment method has the same cost structure.
Sales channel and risk profile
Card-present, ecommerce, phone-order, marketplace, and recurring transactions may be priced differently. Include your actual checkout flow, authentication requirements, fraud tools, and dispute exposure. Security features such as tokenization, hosted fields, or 3D Secure can affect implementation and operational costs even when they are not shown as a simple percentage.
Refunds, disputes, and failed payments
Estimate the cost of refunds and chargebacks using the provider’s written terms. Ask whether the original processing fee is returned on a refund, whether a dispute fee applies, and whether representment tools carry a charge. For subscriptions, include failed-payment recovery work and any account-updater or retry functionality you plan to use.
Contract and operational terms
Review monthly minimums, gateway fees, batch or payout charges, currency-conversion costs, reserve requirements, early-termination terms, hardware, support, and integration expenses. For a payment API integration, also evaluate developer effort, webhooks, reporting, reconciliation, and migration requirements. A transparent quote should make clear which costs are mandatory, usage-based, optional, or subject to change under the contract.
Worked examples
These examples use fictional assumptions to show the method, not to represent market pricing.
Example 1: Flat-rate plan
Assume an online store processes $40,000 in monthly card volume across 800 transactions. The quoted plan uses a 2.9% variable rate and a $0.30 transaction fee, with a $25 monthly account fee.
- Variable fees: $40,000 × 0.029 = $1,160
- Transaction fees: 800 × $0.30 = $240
- Monthly account fee: $25
- Estimated total: $1,425
- Effective rate: $1,425 ÷ $40,000 = 3.5625%
The effective rate is higher than the advertised percentage because the fixed transaction and account fees are included.
Example 2: Interchange-plus plan
Assume the same volume and transaction count. For illustration, suppose the modeled pass-through costs average 1.70%, the provider markup is 0.25%, the provider charges $0.10 per transaction, and the monthly account fee is $35.
- Combined percentage costs: $40,000 × 0.0195 = $780
- Transaction fees: 800 × $0.10 = $80
- Monthly account fee: $35
- Estimated total: $895
- Effective rate: $895 ÷ $40,000 = 2.2375%
The example shows why the model must use comparable assumptions. Actual pass-through costs vary by payment mix and transaction details, so a provider comparison should use your own statement data or a clearly labeled forecast.
Example 3: The effect of average order value
Suppose two businesses each process $10,000 monthly under a plan charging 2.5% plus $0.25 per transaction. Business A has 100 transactions; Business B has 500. Business A pays $250 in percentage fees plus $25 in transaction fees, for $275 before other charges. Business B pays the same $250 in percentage fees but $125 in transaction fees, for $375. The second business has a higher effective rate because each order carries the fixed fee.
When to recalculate
Recalculate your online payment processing fees whenever a major input changes, not only when a contract is due for renewal. Useful triggers include a sustained change in monthly volume, a lower or higher average order value, a new ecommerce or subscription channel, expansion into another country, a material shift toward wallets or alternative methods, or a change in refund and dispute rates.
Review the estimate at least when you receive a new pricing schedule, add a payment method, migrate to a new payment gateway, or change your checkout and fraud settings. Revisit it after implementing account updates, authentication, or payment orchestration if those services add fees or change authorization and recovery outcomes. Related planning may include the comparison of flat-rate and interchange-plus pricing, the guide to choosing a payment processor for a small business, and resources on authorization-rate optimization.
Keep a dated copy of each calculation with the assumptions, provider quote, and source statements used. When a quote arrives, ask for an all-in sample using your transaction mix, a complete fee schedule, contract terms, settlement timing, and the treatment of refunds and disputes. Then compare total cost, effective rate, reporting quality, integration effort, security responsibilities, and support—not price alone. This process turns a one-time payment processor comparison into a practical review you can repeat as the business changes.
