The Complete Guide to Usage-Based Billing for African SaaS

Usage-based billing — charging customers based on what they actually consume — has become the default model for developer tools and infrastructure companies globally. Twilio charges per SMS. AWS charges per compute second. Stripe charges per transaction. The pattern is clear.

But for SaaS companies operating in Africa, applying this model comes with unique challenges. Currency instability, prepaid customer psychology, and the technical complexity of accurate metering across unreliable connectivity all need specific solutions.

Why usage-based billing works especially well in Africa

African buyers — whether consumers or businesses — overwhelmingly prefer to pay for what they use rather than commit to fixed subscriptions. The prepaid mobile model has trained an entire generation to think in credit and consumption rather than monthly commitments. Usage-based billing aligns with this expectation.

In a survey of 200+ African SaaS buyers, 68% said they would switch to a competitor offering usage-based pricing over a flat subscription — even if the total cost was similar.

The three components of usage billing

1. Meters

A meter tracks a unit of consumption. API calls, storage gigabytes, active users, sent messages, processed transactions — anything countable can be a meter. Xtopay meters are real-time: you send usage events via API and they're aggregated immediately.

2. Aggregation

Raw usage events need to be summed, averaged, or peak-sampled into billable quantities. Xtopay supports sum (total events), max (peak value in period), and last (final reading — useful for seat-count billing).

3. Billing periods and invoicing

At the end of each billing period, Xtopay calculates the billable quantity, applies your configured pricing tiers, and generates an invoice automatically. You can configure monthly, weekly, or custom periods.

Getting started with Xtopay meters

Creating a meter takes two API calls: one to define the meter (name, aggregation type, event key), and one to start sending usage events from your application. The entire setup takes under 15 minutes.

• POST /meters — define your meter and aggregation strategy
• POST /usage-events — send consumption events in real time or batch
• GET /meters/{id}/usage — query current usage for any customer
• Invoices are auto-generated at period end — no extra configuration needed