About

Billing infrastructure, built where the payments actually are.

Sobtra exists because building a subscription billing engine is a six-month project that never really finishes. Every African software business rebuilds the same thing: plans, proration, invoices, retries, provider quirks. We are building that layer once, as infrastructure.

Why it exists

The billing engine is the part nobody wants to own.

It starts as a cron job. Then come proration, trials, tax, dunning, refunds, usage, plan migrations. By the time it is working, it has become a second product that only one or two engineers understand.

Most billing platforms were designed for card-first markets and then localised. That order matters: when card networks are the assumption, bank transfer, USSD and mobile money become edge cases bolted onto a subscription model that never expected them.

Sobtra takes the opposite order. The provider layer models the gateways African businesses actually use, and the subscription model sits above it. A merchant can change provider without rewriting how subscriptions work, because the billing records do not belong to the gateway.

The product is in private beta. That means the scope is honest and the surface is still moving. We would rather onboard a small number of merchants who will tell us where the model breaks than publish a feature list we cannot stand behind.

Principles

Four rules we hold to while building.

These are constraints on the product, not marketing lines. They decide what we ship and what we refuse to fake.

01

Billing state should be legible

A subscription, its invoice and its payment should tell one story. When they disagree, support tickets happen. Sobtra keeps them in one model with one source of truth.

02

Local collection is the default, not an integration

Card-first billing assumes a payment culture that does not exist everywhere. Bank transfer, USSD and mobile money are first-class methods in the provider layer.

03

No invented numbers

We do not publish fabricated customer counts, logos or uptime figures. If something is not measured yet, the page says so.

04

Boring where it counts

Money movement, retries and invoices should be predictable. Novelty belongs in your product, not in whether a renewal will charge correctly.

Where we operate

Markets and coverage.

Sobtra supports merchants in Nigeria, Ghana, Kenya, Uganda, Tanzania, Rwanda, South Africa and Egypt, with currencies and payment methods tracked per country. Provider availability within each market depends on the provider's own coverage and your approved merchant account.

How we work

Beta, described accurately.

  • Applications are reviewed manually; typical response time is four days
  • Access is free for the duration of the private beta
  • Feature scope can change, and changes are communicated to beta merchants
  • Destructive changes to billing records are avoided; migrations are additive
  • Support runs through a direct channel for beta merchants

Building something that needs billing?

Tell us what you sell and we will tell you honestly whether Sobtra fits today.

Contact the team

Read the product before you apply.

The documentation describes the billing model, the API surface and the limits of the current beta.