The payment gateway market competes on features — recurring billing, split payments, multi-currency support, developer APIs. But ask any merchant who has experienced a gateway outage during a sales campaign what they actually value most, and the answer is always the same: it just needs to work.
There is a persistent disconnect in how payment gateways market themselves and how merchants actually experience them. Providers lead with feature announcements — new integrations, expanded currency support, improved dashboards. Merchants talk to each other, in founder WhatsApp groups and Twitter threads, about something else entirely: whether the gateway was up during last month’s campaign, whether settlements arrived when expected, whether support responded before the business lost a major client.
This is not anti-innovation sentiment. It is a rational prioritisation that reflects the specific conditions of African digital commerce.
Why reliability is not a baseline assumption in African markets
In mature payment markets — the UK, the US, parts of Europe — merchants can reasonably assume that a payment gateway will be available and functional. Reliability is table stakes. Differentiation happens on features, pricing, and developer experience. When reliability fails, it is newsworthy precisely because it is unusual.
In African markets, that assumption does not hold with the same confidence. Gateway uptime varies meaningfully between providers. Bank API dependencies introduce failure points that are outside any gateway’s control but still fall on the gateway’s reliability record. Mobile network congestion affects transaction success rates in ways that correlate with the exact times — month-end, salary day, major sales events — when transaction volume is highest and reliability matters most.
A merchant who builds their sales infrastructure around a payment gateway’s advanced features and then loses that infrastructure for four hours during a product launch has not made a technology decision. They have made a business risk decision — and miscalibrated it.
The compound cost of an unreliable gateway
Gateway downtime has a cost structure that goes beyond the transactions lost during the outage itself. There is the direct revenue loss from incomplete transactions. There is the customer trust erosion from failed checkout attempts. There is the support overhead of responding to customer inquiries about failed payments. There is the operational disruption of staff redirecting attention from growth activities to problem management. And there is the reputational damage within word-of-mouth networks where a single bad experience spreads faster than any marketing campaign.
For an SME processing 5 million naira in revenue on a Saturday, a three-hour gateway failure at peak shopping time is not a technical incident. It is a material business event — potentially worth 500,000 naira or more in lost transactions — that no feature set compensates for.
OPERATIONAL INSIGHT
In many African founder communities, gateway reliability is discussed primarily through negative experiences — outages, settlement delays, support failures. Merchants rarely publicly praise a gateway for being consistently available. Reliability is expected, not celebrated, which creates a systematic underestimation of its value until the moment it fails. This means reliability rarely wins marketing battles even though it consistently wins retention battles.
How to evaluate reliability before you need it
The challenge with evaluating payment gateway reliability is that the relevant data is rarely published. Uptime SLAs exist but are often written with enough technical exceptions to be commercially meaningless. Historical outage records are hard to find. The most reliable signal available to most merchants is community intelligence — other founders and operators in similar businesses who have lived through high-volume periods on the same infrastructure.
Beyond community signals, the structural indicators worth examining are the gateway’s bank integration architecture — how many direct bank integrations versus aggregated connections it maintains — and its public incident response history. A provider that communicates proactively during outages, publishes post-incident reports, and demonstrates a systematic approach to reliability engineering is materially different from one that goes silent during failures and offers no post-event transparency.
Features create competitive differentiation. Reliability creates business dependency. The merchants building durable digital operations in African markets have learned to prioritise the dependency first.
RELATED READING:
