If you run a business in Africa that accepts payments from other businesses, one decision quietly shapes everything else in your financial operations: which payment gateway you use, and how well it fits the way B2B transactions actually work on this continent.
Most payment gateway guides are written for e-commerce merchants, i.e., consumer-facing businesses selling products online. The B2B reality is different. Longer payment cycles, larger transaction values, complex approval chains, multi-currency requirements across fragmented African corridors, and a much lower tolerance for failed transactions, because a single failed payment can represent a month’s worth of supply.
This guide is built specifically for that reality – the CFO, finance director, operations lead, or founder running a business that sells to other businesses across Africa. It covers what a payment gateway is, how it works in the African context, what separates B2B gateways from consumer ones, and how to choose and compare your options.
What Is a Payment Gateway?
A payment gateway is the technology layer that sits between your business and the financial system, capturing payment details from your customer, encrypting and transmitting them to the relevant banking or processing network, receiving an approval or decline decision, and reporting the outcome back to both parties.
In a physical store, this function is performed by a card terminal. In an online or B2B environment, the payment gateway performs the same function digitally, and in a B2B context, it also needs to handle bank transfers, virtual accounts, multi-currency transactions, and invoice-linked payments that consumer-facing gateways were never designed for.
Think of a payment gateway as the infrastructure layer that turns a payment instruction into a completed, verified, and recorded transaction.
How a Payment Gateway Works: Step by Step
When a business initiates a payment through a gateway, the following sequence occurs typically in under three seconds:
Step 1 – Payment initiation: The buyer enters payment details (card, bank transfer, or payment link) on the merchant’s checkout interface or invoice portal.
Step 2 – Encryption: The gateway encrypts the payment data using SSL/TLS protocols before it leaves the buyer’s environment, protecting it from interception in transit.
Step 3 – Authorization request: The encrypted data is transmitted to the payment processor, which forwards an authorization request to the buyer’s bank or card issuer.
Step 4 – Bank verification: The issuing bank checks for available funds, validates the transaction against fraud rules, and returns an approval or decline code.
Step 5 – Response: The approval or decline flows back through the processor to the gateway, which notifies the merchant and buyer of the outcome.
Step 6 – Settlement: Approved transactions are batched and settled. Funds move from the buyer’s bank through the acquiring bank, into the merchant’s account, typically within one to three business days.
Step 7 – Reconciliation: In a B2B context, there is almost always a seventh step: matching the incoming payment to the correct invoice, department, or project. This is where most B2B businesses lose significant time if their gateway does not handle it automatically. Payment systems like Duplo handle all of these operations end-to-end.
The Four Types of Payment Gateway
1. Hosted Payment Gateway
The customer is redirected to a third-party payment page to complete their transaction. The gateway provider handles all security and PCI-DSS compliance. The drawback is loss of control over the checkout experience and the friction of leaving the merchant’s environment which creates drop-off even in B2B contexts.
2. API-Integrated Payment Gateway
The gateway is embedded directly into the merchant’s platform via API. The customer never leaves the merchant’s environment. The business has full control over the checkout experience. Compliance responsibilities are shared between the gateway and the merchant. This is the preferred approach for businesses operating their own platform or ERP.
3. Self-Hosted / Server-to-Server Gateway
The merchant collects payment data on their own server and transmits it to the gateway. Maximum control, but highest PCI-DSS compliance burden. Suitable only for businesses with significant in-house technical and security resources.
4. Payment Links and Virtual Accounts
A hybrid approach increasingly used in African B2B contexts. The gateway generates a unique payment link or virtual account number tied to a specific invoice. The buyer pays into that account or via the link, and the payment is automatically matched to the invoice upon receipt. No checkout page required. No integration necessary on the buyer’s side.
This is particularly powerful for B2B collections across Africa, where most buyers pay via bank transfer rather than card.
What Makes B2B Payment Gateways Different from Consumer Ones
Most payment gateway articles focus on consumer e-commerce. B2B is a fundamentally different problem:
| Factor | B2C Gateway | B2B Gateway |
|---|---|---|
| Average transaction size | Low to medium | High |
| Primary payment method | Card | Bank transfer, payment links, card |
| Payment cycle | Immediate | 30–90 days |
| Invoice matching | Not required | Critical |
| Multi-currency support | Optional | Often essential |
| Approval workflows | Not applicable | Required |
| Compliance complexity | Moderate | High |
| Reconciliation | Handled by platform | Manual unless gateway automates it |
For B2B businesses, a payment gateway that doesn’t support automatic invoice reconciliation, virtual accounts, and multi-currency collections is both inconvenient and creates operational overhead that grows with your revenue.
The African Payment Gateway Landscape in 2026
Africa’s B2B payments environment has specific characteristics that shape what a gateway must be capable of.
Multiple Payment Rails Across Markets
Across African markets, businesses pay using a mix of bank transfers, mobile money, cards, USSD, and payment links. A gateway that only supports cards is immediately limited in most markets.
- Nigeria: Bank transfers dominate B2B payments. Card payments are secondary.
- Kenya & East Africa: Mobile money (M-Pesa) is significant even for business transactions.
- South Africa: EFT and real-time bank payments via PayShap are primary.
- Ghana, Côte d’Ivoire: Mobile money is integral across both consumer and business payments.
Currency Complexity
A Nigerian exporter receiving payment from a Kenyan buyer is managing NGN-KES conversion. A South African business paying a supplier in Ghana is dealing with ZAR-GHS. These are not straightforward currency pairs, and the spread on conversions through traditional banking corridors is significant. A gateway that offers transparent FX rates rather than inflated bank margins is a material commercial advantage.
Regulatory Fragmentation
Each African market has its own payment regulatory framework:
- Nigeria: CBN licensing; NRS e-invoicing compliance now mandatory (see our NRS E-Invoicing guide)
- South Africa: SARB regulation; Financial Intelligence Centre Act (FICA) KYC requirements
- Kenya: Central Bank of Kenya payment service provider licensing
- Ghana: Bank of Ghana payment systems and services licensing
A gateway operating across multiple African markets must be compliant in each jurisdiction – and this is a significant differentiator between providers.
Payment Success Rates Vary by Corridor
This is the metric most guides overlook, but every finance team eventually learns to care about. A gateway’s success rate – the percentage of initiated transactions that complete – varies significantly across different African payment corridors. A gateway with a 94% success rate in Nigeria but a 78% rate on cross-border transactions is creating invisible revenue leakage at scale.
Payment Gateways in Nigeria: What Businesses Need to Know
Nigeria is the largest B2B payments market in sub-Saharan Africa, and its requirements are specific:
- Bank transfer is the default. The majority of Nigerian B2B payments happen via NIBSS Instant Payment (NIP), not card. Your gateway must support bank transfer collections natively.
- Virtual accounts are standard. Assigning a unique virtual account number to each client or invoice is the cleanest way to automate reconciliation in the Nigerian market.
- NRS e-invoicing compliance is mandatory. From 2025 (large taxpayers) through 2027 (all businesses), invoices must be validated through the NRS Merchant Buyer Solution platform. A gateway that doesn’t integrate with NRS compliance is creating a separate compliance burden for your finance team.
- CBN licensing matters. Ensure any gateway you use holds valid CBN licensing for the payment services it provides.
Payment Gateways in South Africa: What Businesses Need to Know
South Africa has a mature payment infrastructure relative to the rest of the continent, but B2B-specific requirements still apply:
- EFT dominates B2B. Electronic funds transfer (EFT) is the standard for business-to-business payments. PayShap (real-time payments) is growing rapidly.
- FICA KYC compliance is required for payment service providers, meaning your gateway partner needs robust identity verification processes.
- Cross-border complexity is high. Rand-denominated businesses paying suppliers in other African markets face significant FX and correspondent banking friction. A gateway with established African corridors reduces this materially.
Key Features to Look for in a B2B Payment Gateway for Africa
When evaluating gateways for a B2B African business, prioritise these capabilities:
Virtual accounts: Dedicate unique account numbers to specific clients, invoices, or departments so every inbound payment is automatically attributed without manual matching.
Multi-currency support: Cover the currencies relevant to your trading corridors, with transparent exchange rates rather than inflated bank spreads.
Automatic reconciliation: Payments should match to invoices in real time, with data flowing directly into your accounting or ERP system.
Approval workflows: Support customisable approval hierarchies for outbound payments – transactions above certain thresholds should require sign-off before execution.
API-first architecture: The gateway should integrate with your existing ERP, accounting software, or platform without requiring a system replacement.
Compliance coverage: Licensed and compliant in every market where you operate. In Nigeria, this includes CBN licensing and NRS e-invoicing compatibility.
Transparent pricing: B2B transactions are high-value. Percentage-based fees become disproportionately expensive at scale. Look for flat fees or volume-based pricing.
Corridor success rate data: Ask any provider to show you their transaction success rates by market and payment method. Inability to answer this question is itself an answer.
Comparing B2B Payment Gateways in Africa: Top Options
| Provider | B2B Focus | Key Markets | Virtual Accounts | Auto-Reconciliation | Multi-Currency | NRS Compliant |
|---|---|---|---|---|---|---|
| Duplo | ✅ Built for B2B | Nigeria + expansion | ✅ | ✅ | ✅ | ✅ SI + APP licensed |
| Paystack | ❌ Primarily B2C/checkout | Nigeria, SA, Ghana, Kenya | Partial | ❌ | Limited | ❌ |
| Flutterwave | ❌ Primarily B2C | Pan-Africa | Partial | ❌ | ✅ | ❌ |
| Peach Payments | Partial | South Africa, Kenya | Limited | Limited | Limited | N/A |
| DPO Group | Partial | Pan-Africa | Limited | ❌ | ✅ | ❌ |
| Anchor | ✅ Infrastructure/BaaS | Nigeria | ✅ | Partial | Limited | ❌ |
The key distinction: Paystack and Flutterwave are excellent consumer payment gateways that many B2B businesses use by default – but they were not built for B2B workflows. Invoice matching, approval workflows, and automated reconciliation are either absent or require significant custom development on top. For businesses where these functions are central to finance operations, that gap compounds over time.
Duplo’s specific positioning: Duplo holds both the Systems Integrator (SI) and Access Point Provider (APP) licences from the NRS – one of only a small number of Nigerian fintechs to hold both. This means NRS e-invoicing compliance is native to the platform, not a bolt-on.
What Most Payment Gateway Guides Miss
The cost of failed B2B transactions is not symmetric with B2C. A failed consumer transaction means a lost sale. A failed B2B transaction means a delayed shipment, a strained supplier relationship, a cash flow disruption, and potentially a contract dispute. The stakes are categorically higher.
Invoice-linked payments are the African B2B standard, not the exception. The assumption that buyers will enter card details at a checkout is a Western B2C framework. Most African B2B buyers pay via bank transfer against a specific invoice. The gateway needs to handle this natively.
Cross-border B2B payments in Africa are a separate problem. Sending money from Lagos to Johannesburg is not a minor variation of sending money from London to Frankfurt. The regulatory requirements, currency corridors, correspondent banking relationships, and settlement timelines are fundamentally different. A gateway built for intra-market payments will not serve a business with pan-African trading relationships.
Reconciliation is not a nice-to-have – it is the core of B2B finance operations. Consumer gateways don’t need to match payments to invoices because there are no invoices. B2B businesses do. A gateway that doesn’t automate this function adds hours of manual work to every finance team’s week, at every scale.
How to Choose the Right Payment Gateway for Your African B2B Business
Use this framework when making your decision:
- Map your payment corridors – which countries are you collecting from and paying into? Not all gateways support all corridors.
- Audit your payment methods – what do your buyers actually use to pay you? Bank transfer, mobile money, card? Your gateway must support the method your buyers prefer, not just the method you prefer.
- Assess your reconciliation burden – how many transactions does your team manually match per month? This number tells you how much reconciliation automation is worth to you.
- Check compliance coverage – is the provider CBN-licensed in Nigeria? Do they support NRS e-invoicing? Are they SARB-compliant for South Africa operations?
- Ask for corridor success rate data – before signing any contract, ask for transaction success rates by market. This is a direct measure of how much invisible revenue leakage you will experience.
- Evaluate total cost of ownership – factor in transaction fees, FX spreads, integration costs, and the hidden cost of manual reconciliation if the gateway doesn’t automate it.
Frequently Asked Questions: Payment Gateways in Africa
What is the best payment gateway in Nigeria for B2B businesses?
For B2B-specific requirements – invoice matching, virtual accounts, bulk disbursements, and NRS e-invoicing compliance – Duplo is purpose-built for this use case. Paystack and Flutterwave are strong for consumer payments but require significant additional development for B2B workflows.
Can I use a global payment gateway like Stripe in Africa?
Stripe has limited support in African markets. As of 2026, Stripe is available in South Africa and a small number of other African countries, but does not support the local payment rails (NIBSS in Nigeria, M-Pesa in Kenya, PayShap in South Africa) that B2B businesses depend on. Local and regional gateways built for African payment infrastructure are typically better suited.
What is a virtual account and why does it matter for B2B payments in Africa?
A virtual account is a unique account number assigned to a specific client, invoice, or transaction. When a buyer pays into that account, the payment is automatically matched to the right record – no manual reconciliation required. For African B2B businesses where bank transfer is the dominant payment method, virtual accounts are the primary tool for automating collections.
How does NRS e-invoicing affect my payment gateway in Nigeria?
From 2025 onwards, all Nigerian businesses must issue invoices that have been validated through the NRS Merchant Buyer Solution platform. If your payment gateway does not integrate with this system, you will be managing e-invoicing compliance separately – creating duplicate workflows and compliance risk. Read our full NRS e-invoicing guide here.
What is the difference between a payment gateway and a payment processor?
A payment gateway is the interface that captures and secures payment data. A payment processor handles the transaction routing between banks. In practice, many providers (including most African fintechs) bundle both functions – the distinction matters more in enterprise or custom-build contexts.
How long does payment settlement take in African markets?
Settlement timelines vary by market and payment method. In Nigeria, NIBSS instant payments settle in seconds, but funds may take one to two business days to appear in your business account, depending on your gateway. Cross-border settlements typically take two to five business days, depending on the currency corridor and correspondent banking relationships involved.
Duplo’s Approach to B2B Payment Gateways in Africa
Duplo was built specifically for African businesses operating in the B2B context. The platform combines a payment gateway with virtual accounts, multi-currency international payments, automated reconciliation, and NRS compliance in a single integrated system.
Where most gateways hand a business the infrastructure and leave the operations problem unsolved, Duplo closes the gap between payment initiation, payment receipt, and financial record. Automatically, in real time, and across multiple African markets.
This is not an e-commerce gateway adapted for business use. It is a B2B payment infrastructure built from the ground up for businesses operating in Africa.
👉 Ready to see how Duplo handles B2B payments end to end? Book a demo here to speak with a member of our team.
Last updated: May 2026. Payment gateway features, pricing, and compliance requirements change frequently. Verify details directly with providers before making procurement decisions.
