Private beta · Applications reviewed weekly

Build your product.
Leave billing to Sobtra.

Sobtra keeps every subscription, invoice and payment outcome in one place, so your team can stop maintaining a billing engine and get back to the product people pay for.

Nigeria first, then Ghana, Kenya, Uganda, Tanzania and Rwanda.

A bright workspace with a laptop set up for building software
Built for teams who sell software on repeatLagos · Accra · Nairobi

Subscription billing infrastructure.
Not payment processing.

Your provider still moves the money. Sobtra decides what should be charged, when it should happen, and what to do when a payment fails, then keeps one billing record across every provider you connect.

Invoice to charge, in orderTest and live separatedOne API for every provider
The platform

Eight parts of billing, handled in one place.

You do not need every one of these on day one. Start with a plan and a subscription, then turn on usage, coupons and dunning as your pricing gets more interesting.

Products and pricing

Products, plans and versioned prices with daily, weekly, monthly and yearly intervals.

Available

Subscriptions

Create, pause, resume, renew, expire, reactivate, or change a plan immediately or at period end.

Available

Add-ons and coupons

Recurring and one-time add-ons with proration, plus percentage or fixed discounts with limits.

Available

Customers

One customer record per person or company, with their subscriptions, invoices and payment methods.

Available

Invoices and payments

Draft, finalize, void and uncollectible states, line-item detail, refunds and failed-payment retries.

Available

Usage billing

Meters with sum, count, max or last aggregation, idempotent event ingestion and per-unit or tiered prices.

Available

Analytics

MRR, ARR, churn, retention cohorts, trial conversion, payment recovery and CSV exports.

Available

Payment gateways

Provider credentials per environment, with a catalog that states which rails are native and which are planned.

Provider dependent

The billing console your team actually opens.

Subscriptions, invoices and payment attempts share one source of truth, so support, finance and engineering read the same numbers. Switch views to see how the console is organised.

Good morning, Ada

Here is how Northline is billing this month.

SearchCreate invoice

MRR

₦8.42M

+6.4% vs Oct

Active subscriptions

214

12 trialing

Collected this month

₦7.96M

94.6% of invoiced

Past due

4

₦740,000 outstanding

Recurring revenue

Jan – Dec 2026
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec

Subscription health

Live
Active214
Trialing12
Past due4
Cancelled9

Net revenue retention 103.2% over the last 90 days.

Latest invoices

5 of 412
INV-10428Kestrel Analytics₦480,000Paid
INV-10427Harborworks Ltd₦185,000Past due
INV-10426Sable Interactive₦96,000Open
INV-10425Lumen Freight₦5,280,000Paid

Payment activity

Today

payment.succeeded

Paystack · ₦480,000

2 min

invoice.finalized

INV-10429

18 min

payment.failed

Harborworks · insufficient funds

1 hr

subscription.created

Aster Health

3 hrs
Sample workspace. Every figure shown is illustrative, and live and test data are always separate.Overview · Catalog · Subscriptions · Invoices · Analytics

Billing is a system. Not just a charge.

A recurring business has to decide what is due, collect it, and keep a record that survives the next invoice, the next refund and the next support ticket.

01

Billing logic

Schedules, renewals, plan changes and subscription states live in one model instead of four scripts.

02

Payment outcomes

Every attempt is recorded as pending, successful or failed, with the provider reference attached to the invoice.

03

Lifecycle records

Invoices, credit balances, discounts and customer billing history stay readable months after the charge.

Most teams get here after building it twice: once for the first plan, and again when pricing, trials and failed payments arrive.

One billing cycle, four clear steps.

The same sequence runs for a first charge and for the fortieth renewal, whether the customer pays by card or bank transfer.

01

A subscription falls due

Sobtra reads the live record: plan, price, quantity, add-ons, coupon and any metered usage for the period.

02

An invoice is issued

One invoice with plan, add-on, usage, discount and tax lines, in the customer's currency, ready for finance and support.

03

A provider collects

The payment attempt runs through the gateway configured for that merchant and environment: card, transfer, USSD or mobile money.

04

The outcome is recorded

Paid, failed or pending is written to the subscription. A failed attempt follows your dunning schedule before anything changes.

Know what recurring revenue is doing.

Numbers you can take into a board meeting, built from the same records that produce invoices. No separate reporting warehouse.

Monthly recurring revenue is normalised across every billing interval, so one customer on an annual plan does not distort the month. Churn, recovery and lifetime value follow the same basis.

  • MRR, ARR, ARPU and lifetime value with the basis stated
  • Churn by plan, with the MRR it took with it
  • Retention cohorts for up to twelve periods
  • Recovery rate on failed payments and retried attempts
  • CSV export for revenue, subscriptions, payments and invoices

Net revenue

Last 90 days
SepOctNov

MRR

₦8.42M

One normalised figure

Monthly churn

1.8%

By plan as well

Recovery

72%

Of failed payments

Lifetime value

₦3.9M

With basis stated

Billing your engineers can work with.

A REST API that mirrors how subscriptions actually behave, with merchant keys scoped to one environment and documented request shapes for every operation.

Merchant API keys for test and liveWebhooks with signature verification and duplicate handlingIdempotent usage ingestion, up to 500 events per requestPlain HTTP today; SDKs only once they are usable
Read the documentation
curl -X POST $SOBTRA_API_URL/api/v1/checkout_sessions \
  -H "Authorization: Bearer $SOBTRA_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "priceId": "prc_9fK2mQ",
    "quantity": 1,
    "successUrl": "https://app.example.com/welcome"
  }'
Test environmentPOST /api/v1/checkout_sessions

Your providers. One billing record.

Keep your own merchant accounts, settlement and rates. Sobtra coordinates the subscription and keeps the result of every charge, refund and retry in the same timeline.

Paystack logoFlutterwave logoStripe logoFincra logoMonnify logoNomba logoPayPal logoOPay logoHubtel logoHub2 logoWave logoOrange Money logoMTN MoMo logoAirtel Money logoM-PESA logoAdyen logoPayU logoFedaPay logoUnitechpay logoPesapal logoDPO logoPaymob logoCheckout.com logoBachs logo

Working adapters today: Paystack, Flutterwave, Stripe, Bachs.

PaystackNative
FlutterwaveNative
StripeNative
FincraPlanned
MonnifyPlanned
NombaPlanned
PayPalPlanned
OPayPlanned
HubtelPlanned
Hub2Planned
WavePlanned
Orange MoneyPlanned
MTN MoMoPlanned
Airtel MoneyPlanned
M-PESAPlanned
AdyenPlanned
PayUPlanned
FedaPayPlanned
UnitechpayPlanned
PesapalPlanned
DPOPlanned
PaymobPlanned
Checkout.comPlanned
EversendPlanned
BachsNative
01Connect your provider
02Configure products and prices
03Manage the lifecycle

Pricing that starts at zero while we are in beta.

Beta access is free. The commercial plans below apply when billing starts, and we will tell you before anything is charged.

Detecting your region

Starter

For a first paid product finding its first customers.

—platform fee / month
3%of eligible monthly billing volume
Apply for beta

Growth

For a subscription business with predictable volume.

—platform fee / month
2%of eligible monthly billing volume
Apply for beta

ProPopular

For established billing operations and higher volume.

—platform fee / month
0.9%of eligible monthly billing volume
Apply for beta

Enterprise

For negotiated commercial terms and migration support.

Custom
Below 0.9%negotiated on volume
Talk to us

Billed monthly in NGN. Local transfer or card through your provider.

Prices follow your location. Enterprise terms are negotiated individually. See the full pricing page

Your product deserves more engineering time.

01

Tell us about your business and what you sell.

02

Describe how you bill today, and where it hurts.

03

We review the application and your provider setup.

04

Approved teams receive onboarding and workspace access.

Beta access is free while the programme runs. Applications are usually answered within four days. Onboarding starts with Nigerian businesses, then the other supported markets.

Questions worth asking before you commit.

What exactly does Sobtra do?
Sobtra keeps the billing state of a subscription business: products and prices, subscriptions, invoices, payment attempts, add-ons, coupons, usage and dunning. Your application tells Sobtra what was sold; Sobtra decides what to charge, when, and what happens next.
Is Sobtra a payment provider?
No. You keep your own merchant accounts with Paystack, Flutterwave or Stripe. Those providers move the money and settle to you. Sobtra coordinates the billing around them and records what the provider reported back.
Which providers work today?
Paystack, Flutterwave and Stripe have working server adapters, and Bachs is used for Sobtra's own platform billing. Other providers in the catalog can be configured, but live charges are rejected until their adapter ships, so we label them as planned rather than available.
Which countries can I bill in?
Nigeria, Ghana, Kenya, Uganda, Tanzania, Rwanda, South Africa and Egypt are supported, with NGN, GHS, KES, UGX, TZS, RWF, ZAR and EGP pricing. Beta onboarding starts with Nigerian businesses.
Can I bill for usage instead of seats?
Yes. Create a usage meter, send events with an idempotency key, and attach a metered, tiered or volume price. Usage is aggregated for the period and linked to the renewal invoice, so the same event is never billed twice.
Are test and live environments separate?
Every merchant record carries an environment. Test subscriptions, customers, invoices and payments stay out of live reporting, and each API key is scoped to one environment.
Is there an SDK?
Not yet. The API is plain HTTP and every endpoint is documented with request and response shapes. Language SDKs will be published when they are usable, not before.
How does the private beta work?
You apply with your business details and how you bill today. Applications are reviewed by hand and usually answered within four days. Approved businesses get onboarding information and a workspace, and beta access is free while the programme runs.

Build the product. We'll work on the billing.

Bring your provider account and your pricing. We will help with the rest, starting with your first live subscription.