One ISP Billing Setup, Five Markets: Collecting Payments Across East Africa

An ISP that expands from Nairobi to Kampala or Kigali usually discovers that its billing spreadsheet doesn’t travel well. The plans are priced in a different currency, the customers pay on different mobile money networks, and the reports that made sense for one market give a confusing picture when they are added together. The core job, knowing who owes what and whether their service should be on, stays the same. The details around it change.

This guide looks at what changes when an ISP bills subscribers in Kenya, Uganda, Tanzania, Rwanda and the Democratic Republic of Congo, and what can stay the same. It’s written for operators running networks in more than one of these markets, and for owners planning their first expansion. If you are choosing a billing system first, read our practical guide to ISP billing software.

Why multi-country ISP billing is harder than it looks

Running one network in one country gives you a single set of rules. Multi-country operations add four sources of complexity:

  • Currency: Each market has its own currency, and in the DRC both CDF and USD are in use.
  • Payment rails: Customers in different markets pay through different mobile money networks, with different prompts, fees, and confirmation behaviour.
  • Local rules: Telecom licensing, tax treatment, and consumer protection differ between regulators.
  • Reporting: Management usually wants one view of the business, but each market’s figures need to be recorded in local terms first.

None of these is a reason to avoid expansion. They are reasons to design the billing setup with each market in mind from the beginning, rather than copying a Kenyan setup and fixing problems as they appear.

The markets at a glance

The table below summarises the currency and the first questions to answer for each market. Check the mobile money networks and rails with the current coverage page before you rely on them, since availability can change.

MarketCurrencyWhat to confirm before launch
KenyaKESPaybill and prompt options for each plan, and local invoice format
UgandaUGXWhich mobile money networks your subscribers use, and local tax treatment
TanzaniaTZSWhich mobile money networks your subscribers use, and local tax treatment
RwandaRWFWhich mobile money networks your subscribers use, and local tax treatment
DRCCDF and USDWhich currency each plan is priced in, and how customers choose between them

The DRC row deserves the most attention. Where a market uses two currencies in daily life, the billing system needs a clear rule for which currency a plan is priced in and whether a customer can pay in either. A rule that is unclear to the customer will generate disputes.

Keep plans priced in local currency

The simplest and most reliable approach is to price each plan in the currency the customer pays in. A 20 Mbps plan in Kampala should be priced in UGX, and the same plan in Nairobi in KES. Converting prices on the fly makes invoices harder to check and makes it difficult for a customer to see why the amount changed.

Store the currency on every invoice. A subscriber’s balance should always carry its currency, and the system should never add amounts in different currencies without a deliberate conversion step. Adding KES and UGX together produces a number that means nothing.

If you set prices across markets to match a regional strategy, treat the local price as the master and the comparison as a report. Changing an exchange rate should not silently change what a customer owes.

Use local payment rails in each market

Mobile money is common across the region, but the networks differ. M-Pesa is the dominant rail in Kenya. MTN Mobile Money and Airtel Money are the main networks in Uganda and Rwanda, while Tanzania and the DRC each have several, including M-Pesa. Which network a customer uses depends on the market and on their own SIM.

For a multi-country ISP, the practical steps are:

  1. Find out which networks your subscribers use in each market, through your own customer base or a short survey at sign-up.
  2. Offer the networks your customers actually use, rather than every network available. Too many options slow down the choice.
  3. Test each rail with a real account before opening that market. The prompt, the confirmation, and the messages a customer receives can differ.
  4. Check the coverage page for the markets you operate in. IntaSend’s coverage page lists the payment rails available per market, and that is the reference to confirm before promising a network to a customer.

Avoid promising a payment method in a market until it’s confirmed as live for your use case. A customer who can’t pay on the network they use will simply stop trying.

Keep reconciliation local, then consolidate

Each market should be reconciled on its own, against its own mobile money statements and bank accounts. A Ugandan subscriber’s payment should be checked against the Ugandan record, in UGX, before it’s added to any regional total.

Once each market is reconciled, the consolidated report can combine them. The consolidated view should show figures in each local currency first, with any conversion to a base currency as a separate line. That keeps the local team’s numbers recognisable and lets head office see the regional picture without losing detail.

A simple monthly routine works well:

  • Reconcile each market’s collections against its own records.
  • Record the outstanding balance per market, in local currency.
  • Convert to a base currency only for the consolidated summary, using a rate you record and use consistently.
  • Investigate any gap between the billing system and the payment record before the month closes.

Local rules still apply

Telecom licensing, consumer protection, and tax treatment differ across the region. Each market has its own telecom regulator, and some have specific rules on how service can be suspended, how charges are shown, and how refunds are handled. Check the regulator in each market directly for the current rules before launch.

The most relevant regulators are:

Check each regulator’s current requirements, rather than relying on this list or on a summary from another market. Rules change, and a setting that is compliant in one country may need adjusting in the next.

Tax is another area where the billing system needs to be flexible. Some markets require a tax line on invoices; others apply it differently. Configure tax per market, not as one rate for the whole business, and ask a local adviser to confirm the treatment before you publish invoices.

Central or local billing teams

Operators commonly choose between one central team running billing for every market, and a local team in each market. Both can work.

  • A central team keeps rules consistent, makes it easier to see the whole business, and suits a smaller network. The risk is that local questions, such as a missing payment or a complaint in a local language, wait too long for an answer.
  • A local team answers local questions quickly and understands local customers, but it can drift from the group’s rules over time. It suits a larger network with several markets of meaningful size.

Many operators start central and move to local teams as each market grows. Whichever you choose, write down the rules that must stay the same everywhere, such as how a late payment is handled and how reconnection works, and let local teams adjust only the details that really differ. Our guide to reducing late payments for ISPs is a good starting point for those shared rules.

A practical checklist for a new market

  • Confirm the currency for each plan and how invoices show it.
  • Find out which mobile money networks your subscribers use, and confirm each one is live for your use case.
  • Test a full payment and reconnection on a real account in that market.
  • Confirm local telecom, consumer protection, and tax requirements with the regulator or an adviser.
  • Set up a separate reconciliation routine for the market, in local currency.
  • Agree who answers customer questions and how quickly.
  • Plan the consolidated report, with local figures shown first.

Where IntaSend fits

IntaSend provides mobile money collections for ISPs and connected devices across Kenya, Uganda, Tanzania, Rwanda and the DRC, through one integration with the Payments API. Your billing rules, plans, currencies, tax settings, and customer service stay with your business. The payment layer is the part that lets a subscriber pay on the network they use and have the payment reach your system.

To see which payment rails are available in each market, check the IntaSend coverage page. If you’re planning a multi-country network and want to talk through the setup, speak to the IntaSend team. You can also reach us on WhatsApp at +254 711 082 947, by email at [email protected], or by phone at +254 114 114 644.

What Our Clients Say About Us

Don’t just take our word for it—hear what our satisfied customers have to say! IntaSend has helped businesses and individuals across Kenya and beyond streamline their payments.

  • The experience has been seamless, efficient, and hassle-free. One thing that makes Intasend stand out is the platform's ability to collect payments from anywhere in the world.

    Felistas Njihia - IntaSend customer
    Felistas NjihiaFelin Solutions
    ★★★★★
  • Our experience with IntaSend has been remarkable. The integration process was quite smooth with proper API documentation. Intasend won us over on the ease of B2B transactions which is our mainstay and remains our preferred payment solutions

    Kelvin Muriuki, C.E.O - IntaSend customer
    Kelvin Muriuki, C.E.Otaka.earth
    ★★★★★
  • Their platform is incredibly user-friendly, allowing our customers to easily pay for their weekly meals. The fast and secure payment process also provides peace of mind for both our customers and us.

    John Faderr - IntaSend customer
    John FaderrFoodtable by Roros Co.
    ★★★★★
  • @intaSendHQ I am currently blown away by your product. The documentation is so developer friendly as opposed to one pan-African payment gateway, market leader. Good job!

    @Matinde on Twitter - IntaSend customer
    @Matinde on Twitter
    ★★★★★
  • Their customer service is top-notch. The team at IntaSend Payments is friendly and super responsive, always there to lend a hand whenever you need it.

    Wearify on Shopify - IntaSend customer
    Wearify on ShopifyWearify Kenya
    ★★★★★
  • I would like to commend your service and especially point out your outstanding quick turn-around in processing payment and your after-office hour’s support. We are glad that you can be reached 24/7 for queries and round-the-clock support.

    Peter Nyotta - IntaSend customer
    Peter NyottaTwende Worldwide Tours and Travel Ltd
    ★★★★★
  • This payment processor has allowed me to continue serving my local as well as international customers. They also offer reasonable fees and their payouts are timely. Even without a website, IntaSend payment links works just fine.

    Shadrack Masinde - IntaSend customer
    Shadrack MasindeGofan Safaris Limited
    ★★★★★
  • I have been using Intasend for a while now both on my website as a payment gateway and my business as a payment solution and all I can say is, IntaSend is the best solution to sort out all business payment related difficulties.

    Daniel Nyongesa - IntaSend customer
    Daniel NyongesaA+ Academic Consultants
    ★★★★★
  • IntaSend is one of the best online money transfers with mobile and card payment options and helps in collecting emails for marketing.

    Moses Thoithi - IntaSend customer
    Moses ThoithiWizAdventures Safaris
    ★★★★★

Frequently Asked Questions

Which markets does this ISP billing guide cover?

Kenya (KES), Uganda (UGX), Tanzania (TZS), Rwanda (RWF) and the Democratic Republic of Congo, where both CDF and USD are in use.

Should an ISP price plans in local currency in each market?

Yes. Price each plan in the currency the customer pays in and store the currency on every invoice. Never add balances in different currencies without a deliberate conversion step.

Which mobile money networks can ISPs collect on in East Africa?

It depends on the market. M-Pesa leads in Kenya, MTN Mobile Money and Airtel Money are used in Uganda and Rwanda, and Tanzania and the DRC have several networks. Check the IntaSend coverage page for the current list.

How should a multi-country ISP reconcile payments?

Reconcile each market on its own, in local currency, against its own statements. Then consolidate, showing local figures first and any conversion to a base currency as a separate line.

Does IntaSend handle telecom licensing or tax for each market?

No. IntaSend provides mobile money collections. Licensing, consumer protection and tax treatment should be confirmed with each market's regulator or a local adviser.