MVNO in South Africa: hosts, MVNE platforms, RICA and MNP

South Africa is the continent’s most developed MVNO market: Cell C reported 5.7 million MVNO subscribers in May 2026, up 27 per cent year on year, which TechCabal put at 80 to 85 per cent of the national total. Twenty-three MVNOs operate there on wholesale agreements with hosts. The two decisions that set your timeline are the host and the enablement route; the authorisation you need is a question for the host’s wholesale team and local counsel, not for a vendor’s blog.

Cell C reported 5.7 million MVNO subscribers on its network in May 2026, up 27 per cent on the previous year, which TechCabal (August 2026) put at roughly 80 to 85 per cent of all MVNO subscribers in South Africa. One host carries most of the market, a second carries most of the rest, and two more have built enablement platforms to compete for the next wave. For a bank, retailer or ICT provider planning a launch, that concentration is the first fact to plan around: the host decision shapes everything from wholesale pricing to how long registration and porting take to certify.

The market in two tables

TechCentral’s census of June 2025 counted 23 MVNOs in South Africa. Cell C hosted 13 of them and MTN 9, and both had turned hosting into a business line rather than a series of bilateral deals. Vodacom launched an MVNE platform in 2024, Huge NXTGN followed in 2025, and Telkom had announced one. A prospective MVNO has more enablement options here than in almost any other African market.

The second table sorts the notable brands by segment. The segment tells you a lot about the billing logic each one needed.

Two observations. Four South African banks and insurers run MVNOs, and the two that publish numbers are profitable and growing, which is unusual for bank-led MVNOs anywhere. And the retail segment’s most recent relaunch went to an independent enabler rather than a host. The question in South Africa is no longer whether a non-telecom brand can run mobile, but on which platform.

Why the model works in South Africa

Omdia (February 2025) expects MVNO subscriptions in the Middle East and Africa to grow at 17.6 per cent a year between 2023 and 2029, the fastest rate of any region, and names South Africa and Nigeria as the drivers. Matthew Reed, Omdia’s chief analyst, put it plainly: “Banks, supermarkets, and broadband and TV service providers continue to be key players.” South Africa is the market where that sentence describes the actual list of operators.

The bank case is the clearest. Capitec Connect launched in 2022 and reached 1.5 million three-month-active subscribers by early 2026, on a net income line that more than doubled in a year. The bank already holds the customer’s identity, payment instrument and app, so registration, top-up and rewards live in a place the customer opens daily. FNB Connect’s eSIM share, 10 per cent of monthly SIM sales, says the same customer base is comfortable activating a line without visiting a shop. What a bank’s BSS has to do differently is set out on the banking MVNO page.

Retailers came for loyalty. Pick n Pay’s relaunch tied data to Smart Shopper spend at a fixed rate, which is only possible when the catalogue and the charging engine know about the loyalty balance, and the chains’ stores double as distribution and registration points. What a retail MVNO needs from its platform is on the retail MVNO page. Enterprise is the newest segment and the one least served by standard enablement: an ICT provider adding mobile to hold the account needs sponsored usage, limits by employee and group, allocated cost centres and postpaid adjustments, the scenarios covered on the enterprise MVNO page.

Choosing a host and an enablement route

There are three ways to put a South African MVNO on air, and they differ in who owns the customer data, the catalogue and the charging logic. The host decision and the enablement decision are linked but not identical, and it pays to separate them.

The first route is the host’s own MVNE platform. Cell C and MTN each run one, Vodacom launched one in 2024 and Telkom has announced one. You sign a wholesale agreement and take the host’s stack for SIM management, rating, billing and often the customer app. It is the shortest path to market and the right answer for a brand whose proposition is a competitively priced SIM with a few bundles. The cost is that the catalogue, subscriber records and pricing logic sit in the host’s systems, and a host change later is a migration on the scale of the original launch.

The second route is an independent MVNE. Huge NXTGN launched its platform in 2025 and Pick n Pay Mobile relaunched on it the same year. An independent enabler holds the wholesale relationship with a host and runs the BSS for several brands. You get a faster launch than building your own and usually more product flexibility than a host’s shelf, since the enabler competes on that flexibility. You still do not own the platform, and the enabler’s roadmap sets the limit on what your pricing can do.

The third route is your own BSS on a host, which the site calls a Medium MVNO. You sign the wholesale agreement directly with a host, run your own product catalogue, online charging, billing and CRM, and connect through provisioning, charging and mediation interfaces. It takes longer (four to six months after the host agreement and legal framework are in place, on Avante’s planning assumptions) and it puts the platform on your balance sheet or your OPEX line. In exchange the customer data, the loyalty logic and the pricing engine are yours, and a second host is another set of interfaces rather than a migration.

A view, since the South African evidence supports one. If your proposition is a branded SIM, take a host MVNE platform and spend the saved months on distribution. If pricing logic is the product, as it is for a bank paying data for card spend or an ICT provider running sponsored billing, own the BSS. The independent enabler sits between the two and suits a retailer that wants loyalty-linked data without a telecom IT team. Brilliantel chose its own BSS because the B2B and B2G scenarios it sells are not on any enabler’s shelf. The rule generalises: if you can describe your tariff in one sentence, rent the platform; if you cannot, own it.

Whichever route you choose, the host questions are the same. Ask what interface documents exist, whether eSIM provisioning is included from day one, who is the porting party of record and how the RICA registration hand-off works between your front end and the host’s activation. The full pre-signature list is in the launch guide.

Do you need an MVNO licence in South Africa?

The honest answer from a BSS vendor is that the licensing category and its conditions are questions for local counsel and the regulator, not for a vendor’s blog. The sources this article draws on do not set out a South African MVNO licence regime, and inventing one would do you no favours. What they do show is that 23 MVNOs operate on wholesale agreements with hosts, and that the hosts, having built enablement platforms, know exactly what authorisation they require from a tenant before they sign. Make that the first question to the host’s wholesale team and the first item on counsel’s list, inside the host and legal stage rather than as a formality afterwards.

Regulatory checklist

Regulation in South Africa does not change the stages of a launch, but it lengthens two of them and adds integrations that are not optional. Four items belong on every plan.

• RICA registration before activation. The Regulation of Interception of Communications and Provision of Communication-related Information Act requires the subscriber’s full name, identity number, address and MSISDN to be captured before a SIM is activated, and an eSIM is treated as a SIM for these purposes (De Rebus, September 2025). For a digital-only proposition this means a self-RICA flow in your app, as Pick n Pay Mobile ships, with the captured record passed to whoever activates the line. Decide in the host agreement who stores the record, who answers a regulator’s request for it, and how a failed registration is handled.
• POPIA as a design principle. The Protection of Personal Information Act governs how you handle the identity and usage data an MVNO necessarily collects. This article does not set out its provisions; that is counsel’s work. What a launch plan should fix is where subscriber data resides, who is responsible for it under the host agreement, what the enabler or host may do with it, and how your consent and retention rules are implemented in the BSS. On a host MVNE platform most of that data sits with the host. On your own BSS it sits with you, which is both the point and the obligation.
• Number portability from day one. South Africa’s number portability regulations came into effect on 7 March 2022 (Bowmans). A launch without port-in turns away every customer who wants to keep a number, and in a market with 23 MVNOs many prospects already have one. MNP certification runs on the porting scheme’s calendar, not yours, and a failed first attempt puts you back in the queue. Start the certification enquiry before the platform contract is signed.
• Lawful interception hand-off. Under RICA the network has interception obligations, and an MVNO on a host network has to establish in writing what the host does, what the MVNO must provide and how requests are routed. On a host MVNE platform this is largely the host’s problem. On your own BSS it becomes a responsibility question between you, the host and your BSS vendor: which system holds the subscriber identity, which produces the records, and who answers the request. Settle it in the technical annex.

None of this is unusual by African standards; Nigeria’s NIN-SIM linkage and Kenya’s 2025 SIM registration regulations impose comparable identity checks. What distinguishes South Africa is that self-registration in an app and instant eSIM are already normal customer expectations, so the registration flow is a product feature as much as a compliance step.

A realistic timeline

Avante plans a Medium MVNO at four to six months from the point the host agreement and legal framework are confirmed, and a Full MVNO at eight to ten. Platform readiness for a standard mono-MVNO is about three months. In South Africa the stages run as follows.

1. Discovery, two to three weeks. Fix the model, the launch segments and the opening offers, and name every integration. In South Africa the list always includes RICA registration, MNP and eSIM provisioning, and for a bank or retailer the loyalty or core-banking interface that makes the proposition work.

2. Host agreement and legal framework, the critical path. Wholesale terms with the host; interface specifications attached as a technical annex; numbering; SIM and eSIM supply; the licensing question resolved with counsel; the RICA and interception responsibilities written down. No vendor can date this stage for you. Four hosts with enablement platforms help, because each has done the paperwork before, but the host’s commercial appetite still sets the pace.

3. BSS platform, four to eight weeks. Deployment in your perimeter, a private cloud or as a managed service; catalogue and charging configuration for the opening offers; a working test environment. Brilliantel secured its hardware platform up front, which kept infrastructure readiness off the critical path.

4. Integrations, six to twelve weeks, partly in parallel with stage 3. Host provisioning, charging and mediation interfaces; the RICA flow and record hand-off; MNP certification; payment gateway; eSIM profile provisioning; your app, CRM and loyalty or banking platform. MNP certification and the host interface are the two long-lead items, and both should start before the platform contract.

5. Launch, two to four weeks. Pilot with a limited group, then friends and family, then commercial start, with hypercare through the first weeks. Test self-RICA and eSIM activation with real customers in the pilot, not only with test identities.

A host MVNE route compresses stages 3 and 4 because the platform already exists and can be materially faster. A Full MVNO adds workstreams for its own core elements and plans at eight to ten months. One calibration point from a comparable project: a leading banking MVNO in the CIS was delivered on Avante in six months to the bank’s security and integration requirements. The stage plan and an interactive timeline builder are on the launch page.

Where Avante fits

Avante is a BSS vendor, not an enabler. It supplies the platform an MVNO runs on the third route above, own BSS on a host: product catalogue, online charging (Avante OCS), convergent billing, CRM, self-care, mediation and provisioning, plus the RICA, MNP, payment and eSIM integrations, delivered on-premises, in a private cloud or as a managed service. In South Africa, Brilliantel, an ICT provider serving enterprise customers, selected Avante for an MVNO centred on B2B and B2G, with sponsored billing (the employer covers an agreed part of an employee’s usage and the rest is billed to the individual), hardware secured up front and an OPEX-based delivery model to reduce upfront capital. Those are commercial models beyond standard MVNE setups, which is why Brilliantel chose its own BSS. The scenario library and the delivery model are on the enterprise MVNO page.

Frequently asked questions