I've watched this movie many times. A software business somewhere in the world notices a wave of signups from Lagos, Nairobi, Accra, Johannesburg. Someone pulls the revenue report expecting good news, and the money simply isn't there. Trials that never convert. Renewals that fail once and never recover. A conversion rate that would get someone fired in any other region.
The first instinct is always the same: it's a payments problem, so let's add a payment provider with African coverage. I understand the instinct. It's also the wrong layer, and I say that as someone who spent six years running payments for one of the largest merchants by volume on this continent. You can have the best processing stack in the world and still not collect African subscription revenue, because the problem sits above processing. It sits in who the seller is.
Walk through what actually happens to a foreign SaaS company trying to collect here. Three walls, in order.
The first wall is cards. Your transaction arrives at a South African or Kenyan issuing bank as a cross-border, card-not-present charge from a foreign merchant. Issuers here are conservative about exactly that profile, and for good reason, since it's where their fraud lives. Many of the cards in these markets are debit products with tighter rules for online use. So a meaningful share of genuinely willing customers get declined before anything else even matters. Not because they can't pay. Because of how the transaction presents.
The second wall is rails. In most African markets, cards aren't how the majority of people prefer to pay. Mobile money, instant bank transfers, debit-order mandates: these are the rails that matter, and nearly all of them require the seller to be a local business with local contracts and local settlement. A foreign company can't simply switch them on. The rails you most need are the rails you're structurally locked out of.
The third wall is the seller itself. Card scheme rules tie a merchant account to the merchant's domicile. A foreign company cannot hold a local merchant ID, which means it cannot present transactions as domestic, which loops you straight back into wall one. And separately, most of these countries will consider you liable for VAT on digital services from the first sale, whether you've registered or not.
Notice what these walls have in common. None of them are solved by a payment provider, because a payment provider moves money on your behalf while you remain the seller. Foreign seller, foreign presentment, foreign tax problem. The structure is untouched.
A merchant of record changes the structure. The MoR sells to your customer in-market as the legal seller. It holds the local merchant account, so card transactions present as domestic. It signs the local rail agreements, so mobile money and bank mandates become available. It registers for the tax, issues the invoices, carries the chargebacks and owes the consumer-protection duties. You sell to the MoR, the MoR sells to your customer, and you get settled in the currency you actually run your business in.
I'll be straight about the trade-offs, because there are some. An MoR costs more than raw processing, and it should, given what it's carrying. There are things an MoR legally cannot carry, like activities that need their own licence in each market. And not every company calling itself an MoR actually has the substance behind the label, so ask hard questions: who holds the merchant ID, whose name is on the tax filings, where does the money sit between collection and settlement. If the answers are vague, walk.
But the core point stands. African subscription revenue isn't uncollectable. It's uncollectable by a foreign seller. Change the seller, and a market everyone writes off as too hard starts behaving like a market.