Skip to content
For banks and fintechs

Banking MVNO: a growth channel, not an IT project

Banks already make money from mobile. A banking MVNO on Avante pays back in four ways rather than one.

4 to 6 months
to launch on your own BSS
4 value streams
revenue, core growth, cost, risk
6 months
a delivered greenfield banking MVNO

Reviewed by Alexander Donskoy, Sales Director, Avante · Last reviewed 2026-09

Banking MVNOs are already a P&L line

"Banks, supermarkets, and broadband and TV service providers continue to be key players in the MVNO market." — Matthew Reed, Chief Analyst, Omdia, February 2025. Omdia expects the fastest MVNO growth in the Middle East and Africa: 17.6% a year to 2029.

01

R442 million

Capitec Connect's net income for the year to February 2026, up 129% on the prior year; 1.5 million three-month-active subscribers. Launched in 2022.

Source: Capitec annual results; MyBroadband, April 2026.

02

1 million+

FNB Connect active subscribers, with eSIM now 10% of monthly SIM sales.

Source: ITWeb / TechAfrica News, November 2025.

03

333M → 438M

MVNO subscribers worldwide, 2026 to 2030; service revenue from $47bn to over $54bn.

Source: Juniper Research, January and March 2026.

These are independent businesses, not Avante deployments. They establish the mechanism; your business case sizes the opportunity.

Four value streams, each configured rather than developed

01

New revenue

Direct telecom revenue from plans, top-ups and bundles under your brand. Card spend earns data; a utility payment earns an SMS bundle; minutes convert to cashback. For scale, Capitec reached around 6% of its client base in three years.

02

Core business growth

Subsidise mobile, monetise the core: repay on time and earn free data, salary customers get a plan, premium tiers include mobile. FNB reports higher retention and lifetime value where customers hold both products. On an Avante microfinance deployment, a data reward for on-time repayment improved repayment discipline by seven percentage points (measured on that deployment, not a public audit).

03

Cost of communication

SMS, USSD and push on your own routes, so you set price, routing and quality and do not depend on the infrastructure of an operator you compete with. Corporate mobile and M2M for ATMs and POS run on the same platform. On Avante deployments, SMS has come out roughly five times cheaper in an own stack (measured on those deployments, not a public audit).

04

Risk and fraud

Telecom signals the credit bureaus do not hold. A SIM swap becomes a stop signal, a transaction during an active call becomes a fraud flag, and roaming country and SIM lifecycle feed scoring. These are added features, never a sole decision, and they depend on a lawful basis, consent and an agreed data-processing model.

Pick two or three streams for the MVP. Configure, measure and expand without rebuilding the stack.

What it looks like for your customer

Each stage is a reason to return to the one before it, which is what separates a mobile line sold beside the account from a mobile line built into it.

  1. 01

    Join the plan in the bank app

    eSIM or SIM, number kept, KYC reused from the bank's own onboarding where the regulator allows.

  2. 02

    Link the account

    card, salary, subscription or loyalty status becomes a reward rule.

  3. 03

    Bank and earn

    spend, repay, save: eligible events add data, minutes or bill credit, with the benefit and its cap visible in the app.

  4. 04

    Use it, top it up, manage it

    balances, allowances, roaming and family lines in the same app as the account.

Scenario library: 450 ready-made mechanics

Loyalty — bank → mobile

  • card spend → discount, data or minutes
  • account balance or status → telecom reward
  • salary customer → special plan
  • salary customer → family benefits
  • premium customer → mobile bundle
  • bank subscription → mobile included
  • cashback → mobile payment
  • partner activity → data and discounts

Rewards for unused allowances

  • rollover of unused data, minutes and SMS
  • unused allowances → extra reward
  • daily mobile usage → reward
  • loyalty tier → reward multiplier
  • unused allowances → VAS or digital option
  • group and family reward

Engagement — mobile → bank

  • active subscriber → banking communications
  • mobile → bank subscription
  • mobile profile → personalised offer
  • declining activity → win-back
  • new MVNO customer → bank onboarding
  • mobile top-up in the bank app
  • roaming and travel → trip-related offer
  • offer response → segment refinement

Monetisation and ARPU

  • mobile + card
  • mobile + subscription
  • mobile + cashback
  • allowance upsell
  • time-limited bundles
  • regional and country bundles
  • VAS and digital services
  • sponsored mobile service for customers

eSIM and digital distribution

  • eSIM in the bank app
  • travel eSIM
  • allowance balances in the app
  • eSIM and bundle upsell
  • B2B eSIM for employees
  • eSIM in a partner storefront
  • eSIM as a partner reward

B2B and SME

  • business banking → mobile for business
  • corporate mobile for employees
  • employer-sponsored service
  • limits by employee and group
  • allocated accounts and reporting
  • annual and fixed-term contracts
  • postpaid billing and adjustments
  • private APN and enterprise portal

Trust and fraud prevention

  • secure SIM/eSIM for authentication
  • SIM/eSIM lifecycle → risk signal
  • mobile event + transaction → correlation
  • active call session → risk flag
  • roaming and current country → risk signal
  • telecom activity → scoring attribute
  • communication channel control

Partners and ecosystem

  • partner brand and dedicated offer
  • partner sells eSIM and mobile service
  • partner sponsors customer mobile service
  • B2B2C model
  • mobile offers in the marketplace
  • MVNO partner sales programme
  • ecosystem bundles

Operational efficiency

  • dynamic SIM allocation
  • multi-IMSI and roaming optimisation
  • host operator and partner management
  • product catalogue for rapid testing
  • segment-specific plans
  • threshold-based spend controls
  • convergent balances
  • reporting by product and segment

Fraud-prevention scenarios require a valid legal basis, customer consent, availability of the underlying events and an agreed data-processing model.

Turnkey MVNO: Avante delivers the stack; the bank works on offers from week one

01

Complete BSS stack

Plans, offers, customer journeys, communications, rewards and integrations ship as a scenario library proven on live deployments.

02

Open APIs and integrations

One integration surface for the bank app, bank CRM, core banking, data platform, payment gateway and loyalty/CDP, with a phased rollout of the target IT estate.

03

Managed BSS as a service

Year one runs as a managed service with 24×7 support from launch. No in-house BSS team is needed.

04

Growth without re-platforming

Business enablement alongside the technology: financial model, consulting, roadmap and support in host operator negotiations. Medium to Full on one BSS.

The bank owns the proposition. Avante owns the platform, the integrations and the operations.

Reseller builds the host's business; Medium builds the bank's

Model choice is agreed with the host operator and the regulator. The host earns wholesale revenue in every model.Compare models in detail

Reseller / Light: control stays with the host

Reseller is an agency model: the host owns subscribers, plans and revenue. Light lets the brand and contracts be the bank's, but billing, pricing logic and data stay in the host's loop. There is no foundation for testing hypotheses, because you hold no data of your own and the product is limited to the host's shelf.

Medium / Full: the asset is the bank's

Medium: own BSS and own commercial logic, live in four to six months. Full adds network data and autonomy, in eight to ten. Medium to Full runs on one BSS, with no second subscriber migration and no re-platforming.

Five stages, sixteen to twenty-six weeks to launch

  1. 01

    Discovery — 2 to 3 weeks

    Target model, launch segments and opening offers, the data model and integration scoping. Output: MVP scope, responsibility matrix, critical path, preliminary business case.

  2. 02

    Host and legal — the critical path

    Host agreement, numbering, SIM supply, licence or registration, regulatory approvals. Owned by the bank, the host and the regulator; Avante drafts the technical annex and the interface requirements and supports the negotiation.

  3. 03

    BSS platform — 4 to 8 weeks

    Platform deployment in the bank's chosen environment, catalogue and charging configured for the opening offers, a working test environment.

  4. 04

    Integrations — 6 to 12 weeks

    Bank app, host operator interfaces, bank systems and payment gateways, plus KYC and number portability. Runs partly in parallel with stage 3.

  5. 05

    Launch — 2 to 4 weeks

    Pilot, then Friends & Family, then commercial start. Hypercare and managed operations from day one if contracted.

Timing is confirmed once the host and the legal model are chosen.

Launch process

What could a paying mobile base contribute?

Enter your assumptions: paying lines by year three, monthly contribution per line after network, rewards, payments and direct service costs, and the share of the base you expect to convert. The tool returns annual contribution and the scale equation. It is not a forecast, and it is not Avante pricing.

Illustration on your inputs — not a forecast, not Avante pricing, not a market benchmark. Contribution, not net profit. No take-up rate or uplift is assumed. Use actual host terms and a downside case.

Accounts, members or loyalty customers you can address with the offer.

Your assumption — the tool assumes nothing. Test a downside case.

After network usage, rewards, payments and direct service costs. Use your actual host terms.

Optional: costs

One-off cost to win a paying line: SIM, onboarding, incentives, marketing.

Your own estimate of platform, team and operating costs per year — not an Avante figure.

On your inputs

The scale equation — 5× lines at the same unit contribution

What data the bank gets, by model

Data groupAvailable dataMediumFull
Subscriber profileMSISDN, IMSI, ICCID/eSIM ID, SIM status, activation date, statusyesyes
Product profileplan, services, add-ons, bundles, limits, remaining allowancesyesyes
Balances and paymentsbalance, charges, debits, failed top-ups, debt, auto-payyesyes
Lifecycle eventsactivation, suspension, plan change, SIM/eSIM reissue, terminationyesyes
Number portabilityporting record, status, donor and recipient operatorsyesyes
Call and SMS metadataevent, A/B number, direction, duration, sender ID, delivery status, costvia hostyes
Data trafficvolume, APN, session metadata, RAT, QoS, costvia hostyes
Roaming eventsvisited country and network, usage, roaming bundle, travel triggervia host / VASyes
Core network eventsregistration, sessions, policy and charging eventslimited / via hostyes
DPI attributes, location (cell-level, not GPS)service categories, traffic class; cell ID, region, geofence, visited countryown component / host feedwith DPI / LBS

"via host" means through the host operator or a VAS integration; "with DPI / LBS" means an own component is required.

Delivered for banks and fintechs

Frequently asked questions

Why would a bank launch an MVNO?

Four reasons banks give: a recurring telecom revenue line under the bank's brand; more engagement and retention in the core product when mobile rewards are tied to banking behaviour; cheaper and fully controlled SMS, USSD and push; and telecom signals (SIM swap, active call, roaming) that improve fraud detection and scoring. Capitec and FNB are the public examples; a further five bank and fintech MVNOs run on Avante under NDA.

How long does a banking MVNO take to launch?

Four to six months for a Medium model once the host agreement and legal framework are in place, and eight to ten for Full. The critical path runs through the host and the regulator rather than the software.

Do we need our own telecom team?

Not to launch. Year one runs as a managed service with 24×7 support. The bank's teams work on offers, channels and the customer, and build telecom capability at their own pace.

Can we reuse the bank's KYC for SIM registration?

Where the regulator allows it. SIM-registration rules differ by market (RICA in South Africa, NIN-SIM in Nigeria, national-ID checks in Kenya); we configure the KYC flow per market and integrate with the bank's onboarding where permitted.

Which model should a bank choose?

Usually Medium: own BSS, own catalogue and data, integrated with the bank app. Full is the planned next step once network data or autonomy justify it. Reseller and light models leave the data and the pricing logic with the host, which removes most of the reasons a bank launches in the first place.

Can telecom data be used in credit decisions?

As an added feature, never a sole decision, and only with a lawful basis, customer consent, the underlying events and an agreed data-processing model. The platform provides the events; the bank's risk and compliance functions decide the use.

One workshop produces a go / no-go decision pack

We align on the target model, launch segments and opening offers, roles of the bank, the host and Avante, and the data model. You leave with an MVP scope, a responsibility matrix, the critical path, a launch roadmap and a preliminary business case.

Let’s discussyour project

Launching an MVNO or evolving your BSS? Let’s start with what you want to achieve.

Our team will review your request and email you to discuss the next steps.

Prefer email?info@avantebss.com