You're selling across African markets.
Customers are placing orders. Payments are coming in. Your sales numbers may even look healthy.
But the amount that ultimately reaches your business may tell a different story.
Processing fees, currency conversion, payouts, refunds, disputes and settlement delays can reduce the value of successful transactions. Failed payments and unavailable local payment methods can create another problem entirely: sales that never become completed transactions.
The result is a payment problem that is bigger than the gateway fee.
Your payment setup can affect how much you sell, how much you retain from each sale, how quickly you receive your money and how much work your team needs to manage it.
This guide shows you how to identify payment-conversion leakage, calculate the true cost of accepting payments, evaluate payment infrastructure across African markets and determine what should change before you expand further.
Payment infrastructure can reduce e-commerce margins in two ways: it can increase the cost of successful transactions and prevent potential transactions from being completed.
You may see the first problem when:
The second problem appears when:
This means merchants need to answer two separate questions:
How much do we retain from a successful payment?
How much order value are we losing because customers cannot successfully pay?
A useful payment review should therefore examine performance by:
Key metrics include:
A lower processing fee is not automatically better if the payment route causes more customers to abandon checkout.
The better commercial question is: How much profitable order value does this payment setup help us complete, and what does it cost us to move and manage that money?
The true cost of a cross-border payment is the difference between what the customer pays and what the business ultimately retains and can use, after processing fees, FX costs, payouts, refunds, disputes, settlement-related deductions and relevant operational costs.
The processing fee is only one part of that equation.
A provider may charge a percentage, a fixed amount or both.
A small difference on one transaction can become significant when applied across thousands of payments.
If customers pay in one currency while your business settles in another, currency conversion can affect the final amount you receive.
Establish:
Moving funds from the payment environment to your preferred account can introduce additional charges depending on the payment and settlement arrangement.
Refunds, chargebacks and reversals can create costs beyond the original transaction.
Confirm:
A payment can be successfully collected but still unavailable to the business.
Review:
Your finance and operations teams may also spend time reconciling:
A payment route can therefore look inexpensive at checkout while creating substantial costs elsewhere.
Failed payments represent potential order value that did not become a completed sale, although some of that value may be recovered through retries or alternative payment methods.
For example, suppose your business receives:
The failed attempts represent:
800 × $75 = $60,000 of attempted order value.
That does not mean the business definitely lost $60,000.
Some customers may:
The more useful question is:
How much of that failed order value could realistically have been recovered?
Track:
This allows you to distinguish between temporary payment friction and the demand you really lost.
Before changing providers, calculate what your current payment setup is actually costing you.
The Cross-Border E-commerce Payment Cost and Settlement Worksheet helps you compare:
Calculate Your True Cross-Border Payment Cost →
Use actual transaction and settlement data wherever possible. This gives you a clearer basis for deciding whether to optimise your current setup, add another payment route or evaluate a different provider.
A customer's payment and your final settlement are different stages of the payment journey.
Understanding each stage helps identify where value is being lost or delayed.
The customer selects an available payment method and attempts to pay.
Depending on the market, this could include:
The first question is whether customers actually have access to the methods they prefer to use.
The payment moves through the relevant payment infrastructure.
Evaluate:
If the customer's payment currency differs from your settlement currency, conversion may affect the final amount.
Review:
The processed funds become available according to the agreed settlement arrangement.
Confirm:
Payment activity must be matched against orders, refunds and accounting records.
This is where businesses can discover that a successful customer payment is not necessarily the same thing as immediately usable merchant funds.
The business may still be waiting for settlement, resolving a discrepancy, converting currency or matching a settlement batch to individual orders.
African markets do not share one identical payment environment. Merchants should evaluate payment methods, currencies, eligibility, settlement and operational requirements separately for every market they serve.
For each priority market, establish:
| Question | What to verify |
|---|---|
| Customer market | Is the country supported for your business model? |
| Payment method | Which methods are customers most likely to use? |
| Currency | What will customers pay in and what will you receive? |
| Merchant eligibility | Can your business onboard from its current entity and structure? |
| Settlement | Where will funds settle, when will they arrive and in what currency? |
| Limits | Are transaction and volume limits suitable? |
| Refunds | Can refunds be processed appropriately? |
| Compliance | What KYC, KYB, AML and licensing requirements apply? |
| Reliability | How are failures and incidents handled? |
| Reporting | Can activity be tracked by country, currency and payment method? |
One distinction is particularly important:
Customer-country support and merchant-country eligibility are not the same thing.
A provider may support customers in a particular country without providing the merchant onboarding, settlement structure or payment methods your business requires.
| Market | Payment considerations | Additional checks |
|---|---|---|
| Nigeria | Cards, bank transfers, USSD and other local account-based methods | Merchant eligibility, currency, settlement and applicable requirements |
| Ghana | Mobile money, cards and bank-based methods | Local-currency settlement and payout arrangements |
| Kenya | Mobile money, including M-Pesa, cards and other local methods | Customer-method fit and settlement route |
| Côte d’Ivoire | Mobile money and bank-based infrastructure | Francophone-market operating and compliance requirements |
| South Africa | Cards, EFT and other local methods | Settlement, refunds, disputes and currency |
| Zambia | Mobile money and bank-based methods | Currency, limits and settlement arrangements |
| Senegal | Mobile money and bank-based infrastructure | Local operating and settlement requirements |
| Cameroon | Mobile money and bank-based methods | Appropriate payment flows and settlement availability |
These are starting points, not guarantees of payment-method availability.
Actual coverage depends on factors including:
Instead of asking if this provider covers Africa, the question you should be asking is: can our customers pay using relevant methods, and can our business receive, settle, reconcile, and manage those funds effectively in each market?
There is no single payment infrastructure model that is automatically best for every merchant.
The appropriate model depends on:
Best suited to: merchants seeking a simpler provider relationship.
Advantage: fewer integrations and commercial relationships.
Trade-off: coverage, payment-method availability, eligibility and settlement need to be strong enough across all priority markets.
Best suited to: merchants prioritising specific countries.
Advantage: strong local payment coverage.
Trade-off: additional integrations, contracts, settlement relationships and support channels.
Best suited to: merchants expanding across multiple African markets.
Advantage: potentially broader coverage through fewer provider relationships.
Trade-off: actual country coverage, payment methods, eligibility and settlement must be verified.
Best suited to: merchants prioritising international card acceptance or global payment infrastructure.
Advantage: established technology and international infrastructure.
Trade-off: local payment methods and market-specific settlement may be more limited.
Best suited to: larger merchants requiring routing flexibility or redundancy.
Advantage: greater control over routing and payment resilience.
Trade-off: greater technical, reporting and operational complexity.
The objective isn't simply to minimise the number of providers but to build the simplest payment setup that provides the coverage, reliability, economics and resilience your business actually needs.
The best payment provider is not necessarily the one with the lowest fee. Compare payment performance, total cost, settlement, operations, technology and expansion capability together.
Compare:
Compare:
Confirm:
Review:
Confirm:
Ask:
The final comparison should answer which provider gives us the strongest combination of completed sales, net settled value, cash availability, operational efficiency and expansion readiness?
A better payment setup should connect the entire payment operation rather than treating checkout as an isolated function.
At minimum, evaluate:
Can customers use relevant payment methods in the markets you serve?
Can required outbound payment flows be supported?
Can collected funds reach the appropriate account, currency, and destination under predictable terms?
Can payment infrastructure connect to your existing e-commerce and finance environment?
Can your teams monitor payment performance, settlement and reconciliation?
Can your business maintain suitable payment coverage if a particular route experiences problems?
The goal is to create a payment operation that supports conversion, collection, settlement, reconciliation and growth.
Once you've identified where payment costs, conversion problems or settlement friction are occurring, you can evaluate whether PayOnUs fits the requirements of your business.
PayOnUs provides capabilities across Collection, Payout, Instant Settlement, Payment API, and Analytics & Reporting, with availability depending on the relevant market, merchant eligibility and configuration.
| Merchant requirement | PayOnUs capability | Potential business outcome |
|---|---|---|
| Local payment collection | Collection | Support relevant customer payment flows across supported markets and methods |
| Outbound payment requirements | Payout | Support required payout flows without necessarily creating a separate payment arrangement |
| Access to settled fund | Instant settlement | Potentially improve cash availability where applicable |
| Existing technical environment | Payment API | Connect payment infrastructure to existing workflows |
| Payment visibility | Analytics and reporting | Improve transaction monitoring and reconciliation visibility |
| Multi-market operations | Regional infrastructure | Potentially reduce the need for separate payment relationships across supported markets |
The value isn't simply that a provider offers several payment products.
The value is what those capabilities can change in the merchant's operation.
Collection can support relevant payment methods that may help customers complete purchases.
Payouts can support outbound payment requirements that might otherwise require separate arrangements.
Settlement capabilities can help merchants plan cash availability more effectively where applicable.
Payment API integration can connect payment activity more closely with existing order and finance workflows.
Analytics and reporting can improve visibility into payment performance, settlement and reconciliation.
Multi-market infrastructure can potentially reduce the complexity of managing separate payment relationships as the business expands.
The actual benefit depends on:
Payment-method availability, settlement timing, Instant Settlement availability and currency options should be confirmed during onboarding and implementation.
You don't necessarily need to replace your entire payment infrastructure at once.
A controlled rollout can help you establish whether a new configuration actually improves commercial and operational performance.
Document:
Document what happens after a customer makes a payment, from processing and conversion through to settlement and reconciliation.
The same exercise should be performed for refunds and relevant outbound payment flows.
Measure:
Possible actions include:
Establish requirements for:
Test:
Compare before and after:
Use those results to determine whether the configuration should expand to additional markets.
Before signing a new provider agreement, make sure you can answer these questions.
If you cannot clearly answer several of these questions, you should not make a payment decision yet.
The highest cost depends on the merchant's payment mix, but it can come from processing fees, FX conversion, failed transactions, payouts, disputes, settlement deductions or operational work. Merchants should calculate total payment cost rather than relying on the headline processing rate.
Payment failures can reduce revenue by preventing customers from completing otherwise viable purchases. The commercial impact depends on failure volume, average order value, retry recovery, and whether customers abandon checkout completely.
Compare payment completion, local payment-method coverage, total cost, FX, settlement, payouts, refunds, reconciliation, integration, support and expansion capability, not processing fees alone.
The appropriate methods depend on the market and customer base. Cards, bank transfers, mobile money and other local account-based methods may be relevant, but merchants should evaluate actual customer behaviour and provider availability in each target market.
No. Customer-country payment support and merchant eligibility are separate questions. A provider may support customers in a country without providing the onboarding, settlement or business structure your merchant operation requires.
Settlement is critical because successfully collected funds are not necessarily immediately usable funds. Merchants should confirm settlement timing, currency, destination, reserves, holds and how disputes or reversals affect settlement.
It depends on the merchant's markets, payment-method coverage, transaction volume and resilience requirements. One provider can simplify operations, while multiple providers may provide stronger local coverage or redundancy. The goal is to find the simplest setup that provides the coverage and reliability the business needs.
If you're unsure whether your current payment setup is actually protecting your margins, start by measuring it.
The Cross-Border E-commerce Payment Cost and Settlement Worksheet helps you identify:
Calculate Your True Cross-Border Payment Cost
If your analysis identifies problems with:
See How PayOnUs Supports African E-commerce Payments
Once you've identified the payment problems affecting your business, the next conversation should focus on your actual operation.
Discuss:
The objective is to determine whether PayOnUs can provide a suitable payment infrastructure configuration for your business.