Most merchants judge a payment provider by the number printed on the pricing page: 2.9%, 3.5%, whatever the headline rate is. That number is real, but it isn't the number that matters. The amount that actually lands in your account after currency conversion, payout charges, refund handling, and settlement deductions is usually smaller than the processing fee alone would suggest, and by the time finance has reconciled a month of transactions, the difference can be substantial.
There's a second, separate cost that doesn't show up in any fee schedule at all: sales that never happen because a customer couldn't complete checkout. A failed payment, an unsupported local method, or a transaction stuck in "pending" isn't a processing cost — it's lost or delayed revenue, and it can be larger than every fee combined.
Sorting out which of these two problems you actually have, and how big it is, is the first real step in fixing either one.
If your customer pays in one currency and you settle in another, conversion happens somewhere in that transaction — and the rate applied, the spread charged on top of it, and any separate conversion fee all determine how much of the original payment survives the trip. A provider can advertise a competitive processing fee while applying an FX spread that costs more than the fee itself.
The only way to know is to check the specifics for each transaction: the exchange rate applied, the spread above the market rate, any explicit conversion charge, and the final amount that shows up in your settlement currency. Comparing this across providers matters more than comparing headline rates, because two providers can quote the same processing fee and still produce very different settled amounts once conversion is factored in.
A transaction can clear, show as successful in your dashboard, and still leave you waiting days before the money is actually available to spend. That gap — between collection and usable settlement — is where a lot of merchants lose track of their own cash position.
Before assuming a payment setup is working well, it's worth confirming the specifics: when funds actually become available, what currency they settle in, where they land, whether reserves or holds apply, how weekends and holidays affect timing, and how disputes or reversals get deducted. A provider that settles quickly on paper but holds a rolling reserve, or that treats Friday transactions as unavailable until the following Tuesday, is not offering the cash flow the settlement schedule implies.
A refund isn't simply the reversal of a sale. The processing fee on the original transaction may or may not come back. Any FX cost incurred during conversion is often not recoverable at all. Payout charges already deducted don't necessarily reverse either, and a dispute or chargeback fee can apply on top of the original loss.
Merchants who don't track this separately tend to underestimate what refunds and disputes actually cost them, because the number that shows up in accounting is the visible refund amount, not the full set of deductions attached to it. Confirming how a provider treats fees, FX, and payout charges on a reversed transaction — and how those deductions actually appear in settlement reports — is worth doing before volume grows.
Even when every individual transaction is priced fairly, a payment setup can still be expensive to operate if it takes significant staff time to reconcile. Matching provider reports against orders, tracking down failed transactions, resolving discrepancies between what was collected and what settled, and handling multi-currency batches all consume finance and operations time that rarely gets counted as a payment cost — even though it is one.
A route that looks cheap at checkout can turn out to be the most expensive one to operate once the reconciliation workload is priced in.
Nigeria, Ghana, Kenya, South Africa, and other African markets each have their own mix of dominant payment methods, currencies, and settlement conventions — mobile money is central in some markets, cards and EFT dominate in others, and merchant eligibility requirements vary by country. A provider supporting your customers in a given country doesn't automatically mean it supports your business there: customer-country payment support and merchant-country eligibility are separate questions, and conflating them is a common source of surprises during onboarding.
Evaluating payment infrastructure market by market — coverage, methods, currency, settlement, and eligibility together — gives a much clearer picture than asking whether a provider "covers Africa" in general terms.
Most of this becomes concrete once you look at actual transaction and settlement data rather than the fee schedule alone. If you want to work through this systematically, the Cross-Border E-commerce Payment Cost & Settlement Worksheet walks through each of these cost areas market by market — processing, FX, payouts, refunds, settlement timing, and reconciliation workload — so you can see where the actual leakage is before deciding what to change.
Payonus builds payment infrastructure for merchants dealing with exactly this kind of cross-border complexity, but the more immediate task, regardless of who your provider ends up being, is measuring what your current setup is actually costing you.