The Direct Answer: Compare Total Cost, Not the Listed Fee

The cheapest payment route is not necessarily the option with the lowest percentage fee. Payment routing cost should be measured as the total amount deducted from every successful payment, including the base processing charge, payment-method surcharge, currency-conversion markup, chargeback or dispute expense, payout fee, and any monthly minimum or compliance overhead. For example, a route charging 2.9% plus $0.30 may be cheaper than one charging 2.5% plus $0.60 for a $20 transaction, but it becomes more expensive above a particular order value. On a $1,000 payment, the first route costs $29.30 and the second costs $25.60 before extras, so the percentage alone gives the wrong answer.

Also worth reading: What Are the Key Decision Criteria for Choosing Digital Payment Workflows in 2026? · How should an SMB evaluate payment tools before choosing a provider? · What should be on a payment processor comparison checklist when choosing a checkout system in 2026?

The right comparison also depends on how quickly the customer must receive funds, which currencies and payment methods must be supported, and the merchant’s acceptable failure and dispute rate. A route that is inexpensive but routes customers through an unfamiliar checkout or adds an extra authorization step can reduce conversion enough to outweigh a small processing saving. As of September 27, 2026, there is no universal cheapest provider: the correct baseline is the total cost per accepted order or payout, calculated from current pricing, expected transaction mix, and actual settlement behavior. A useful formula is: expected cost = successful-payment fees + fixed fees + FX costs + expected dispute losses + expected failed-payment costs + internal operating costs.

How Payment Routing Determines the Final Price

A payment router evaluates available processors, methods, and sometimes financial institutions before sending a transaction through a selected path. The path may differ by card issuer, country, currency, device, time of day, or payment method. This is why two customers paying the same merchant can have different costs even when they choose the same checkout. Card-network rules, issuer authorization behavior, local payment preferences, and processor risk controls all affect acceptance and settlement. Lightning Network examples make the routing idea familiar: a payment may traverse channels rather than move directly between two parties, and the selected path has its own fee and reliability trade-offs.

Routing affects more than the processor percentage. A low-fee route may use an indirect acquiring path, resulting in delayed settlement, weaker customer recognition on the bank statement, or a higher dispute rate. A more expensive local method may improve authorization rates in its home market, while a global card route may be more familiar to international buyers. The merchant should therefore measure cost per completed sale, not cost per attempted authorization. A declined payment that never becomes revenue is not saved merely because its processing fee was avoided, although some processors still charge certain fees for failures, currency conversion, disputes, or other events.

Currency conversion must be separated from the payment-processing charge. If a customer pays in euros while the merchant settles in dollars, the provider may add a spread to the foreign-exchange conversion, an international card fee, or both. A quoted 3% checkout price can become materially more expensive after a 1% FX spread and a $1 international-payment surcharge. Conversely, a multicurrency account may reduce repeated conversion costs if the merchant holds the received currency and converts only when needed. The best route is the one whose combined price is transparent and whose payout timing matches the merchant’s cash flow.

Building a Like-for-Like Cost Comparison

Start by collecting current written pricing from every candidate, dated September 27, 2026 or close to that date. Record the percentage charged on the original transaction amount, the fixed transaction fee, treatment of different payment methods, international surcharges, FX markup, payout frequency, payout fee, refund fees, and dispute fees. Do not compare a card offer with a bank transfer offer as though both process the same product: bank transfers may have low percentage costs but require reconciliation, slower arrival, and sometimes return-payment risk. Wallets and local instant-payment methods may be cheaper for domestic customers but can be less useful for cross-border or high-ticket transactions.

Use the merchant’s actual annual volume, not an optimistic forecast. Suppose the business expects 10,000 payments per month with an average value of $120, producing $1.2 million in monthly payment volume. A 20-basis-point difference equals $2,400 per month, or $28,800 annually, before fixed fees and chargeback costs. If a route’s lower price produces even a 0.2 percentage-point drop in completed checkout conversion, the lost revenue may exceed the processing saving. Compare routes at low, typical, and high transaction values because fixed fees make small transactions expensive and percentage fees dominate larger ones.

Cost componentLow-fee percentage routeLow-fixed-fee routeWhat to record
Example processing price2.5% + $0.202.9% + $0.30Current published rate
Cost on $20 payment$0.70$0.88Fixed-fee impact
Cost on $120 payment$3.20$3.78Typical order value
Cost on $1,000 payment$25.20$29.30Percentage-fee impact
Cross-border caseAdd FX spread and card surchargeAdd applicable international feeTotal customer cost
Operational effectMay have lower acceptance or slower payoutMay offer simpler predictable pricingSettlement and conversion rate
This table is illustrative, not a quote from a named provider. The correct break-even point between the two example prices is $10,000: at exactly $10,000, both cost $250, ignoring extras. Below $10,000, the 2.5% plus $0.20 route is cheaper in this example; above $10,000, the lower percentage route wins. Real break-even points change when currency, card, dispute, and payout costs are included.

Practical Steps for Testing Payment Routes

The first practical step is to classify transactions by customer location, currency, payment method, and average order value. Domestic card payments, international card payments, local bank transfers, digital wallets, and manual bank deposits should not be blended into one average. For each segment, identify the routes available, the delivery time, the refund policy, and the likely authorization rate. Test with low but meaningful values rather than relying only on a provider calculator. Ask whether the quoted rate applies to the transaction, the settlement amount, or the converted amount, because small differences in the fee base can matter at scale.

Second, run a controlled test using the same product page, checkout copy, currencies, and order values. Record approval rate, completed-payment rate, time to settlement, customer support contacts, refunds, disputes, and bank-statement recognition. A lower price can be misleading if customers abandon after seeing an unfamiliar method or if the payment succeeds but the merchant receives less than expected. Keep a simple ledger for at least 30 days, covering at least one normal business cycle and ideally a peak period. Monthly reporting often conceals differences between weekdays, weekends, and local holidays.

Third, calculate contribution after payments, not gross sales. If gross margin before payment costs is $8 on a $20 order and one route costs $0.70 while another costs $0.88, the lower-fee route improves contribution by $0.18, assuming conversion and dispute performance are equal. If the cheaper route reduces completed payments by 0.5 percentage points, the loss on 1,000 attempts may be approximately $10 in revenue at a $20 average order, before gross margin, which is larger than the $0.18 per successful order saving. The correct decision is therefore based on contribution per checkout attempt, with customer trust and operational burden considered alongside the ledger.

Comparing Alternatives: Gateways, Wallets, Banks, and Direct Methods

A gateway is usually a software layer connecting merchants to one or more acquiring banks or payment processors. It may provide hosted checkout, stored credentials, fraud screening, and reporting, but it does not eliminate the underlying acquiring cost. A wallet may be a customer-facing payment method, a merchant payout tool, or both. A multicurrency account can be useful for holding several currencies and reducing the number of conversions, but it may charge a conversion spread or a withdrawal fee. A local instant-payment system such as UPI can be inexpensive for participants in India, while the same method may have little relevance to a merchant whose customers are mostly elsewhere.

Bank transfers are attractive for higher-value payments or markets where card acceptance is weak, but they are not automatically cheaper once staff time and reconciliation are counted. A merchant may need to verify the sender, match the reference number, monitor unsettled payments, and handle returned or incomplete transfers. Digital wallets can improve mobile conversion, but wallet fees, wallet-specific incentives, chargeback treatment, and settlement schedules must be included. Payment methods should be compared as delivery mechanisms for the same customer and order economics, not as interchangeable marketing badges.

The strongest alternative is often a two-route arrangement: a low-cost primary method for customers who prefer it and a familiar fallback method for customers who do not. The merchant should set limits by risk and ticket size rather than promising every route everywhere. A useful policy might allow local instant payments for amounts up to $500, cards for higher-value domestic purchases, and a separately reviewed international route for cross-border orders. These are examples, not universal thresholds, and the actual limits should follow the provider’s rules, local regulation, fraud findings, and the merchant’s ability to deliver.

Common Mistakes That Distort the Comparison

The most common error is comparing headline rates while ignoring fixed charges. Another is using a promotional rate without confirming its expiration date, volume condition, currency restriction, or treatment of international cards. A merchant may also assume that “no chargeback fee” means no dispute cost; disputed transactions can still consume staff time, delay funds, and create platform risk. Refunds are similarly misunderstood because some providers retain the original processing fee, while others charge a separate refund fee or do not return the full original amount.

Another mistake is treating authorization as settlement. An approved card payment can still be reversed later, and a bank transfer can appear pending before the money is usable. A provider’s payout schedule matters if the business pays suppliers weekly but receives revenue only monthly. Some businesses compare fees daily while comparing cash-flow timing only once a quarter. Others ignore tax treatment, withholding, local compliance costs, and currency-account maintenance fees. Prices may also change between a merchant’s application and the date of the test, so every comparison should include the quote date and a recheck date.

Finally, do not let a sales representative’s average-case example substitute for a contract or current pricing page. Ask for the complete rate card, service limits, chargeback rules, payout policy, and fee treatment for each relevant currency. A provider that publishes unclear pricing may be cheaper in theory but more expensive after support calls, manual adjustments, or contract exceptions. Transparent pricing is valuable even when a competitor’s headline percentage is lower by several basis points.

When to Act and When to Stay With the Current Route

Act now if a payment provider has recently raised fees, settlement delays have exceeded the merchant’s operating cycle, a high percentage of customers are abandoning checkout, or the business has entered a new country. Recalculate costs whenever the monthly volume, average order value, currency mix, dispute rate, or refund rate changes by a meaningful amount. A practical trigger is to review the routing arrangement every quarter and immediately after any provider change notice, major promotion, new product launch, or peak season.

A 20-basis-point reduction is worth investigating, but it is not automatically a reason to migrate. At $500,000 in annual volume, 20 basis points represents $1,000 before fixed costs and operational effects. That may justify a short test, but migration can also require new integrations, merchant-account approval, customer communication, accounting changes, and reconciliation. If a current route has an authorization rate above 95%, a settlement time of two business days, and a total cost of 2.8%, a competitor at 2.6% may not be meaningfully better if it settles in five days or raises support contacts.

Stay with the current provider when the difference is small, the migration cost is high, and the existing route performs reliably. Staying is not passive acceptance: request current pricing, document service levels, and compare the route again later. For a fast-growing merchant, a small percentage saving can become worthwhile, but only after a controlled test demonstrates that completed sales, settlement timing, and dispute outcomes improve the overall result.

The Decision Rule for a Defensible Choice

Use three totals: cost per attempted payment, cost per completed payment, and contribution after payment costs across the customer’s lifetime value. Add a fourth measure if the business is international: cost after currency conversion and payout. Review each result at the 25th, 50th, and 75th percentile of order value, and include the expected dispute rate rather than assuming every payment is clean. The winning route is not the one with the most attractive advertisement; it is the one that reliably delivers revenue at the lowest total cost under realistic conditions.

For most merchants, the practical decision is to select a transparent primary processor, retain a suitable backup route, and negotiate or test costs by payment method. Record the pricing date, transaction mix, assumptions, and expected savings in a short decision note. If two options remain within a small margin, choose the one with clearer statements, stronger local acceptance, and faster settlement. Payment routing is an operating decision, not only a purchasing decision. A modest fee reduction can help, but preserving conversions and customer confidence is usually the stronger measure of success.