The billing engine
behind recurring revenue.
Sobtra holds the part of your business that has to be right every month: what each customer is on, what they owe, what they paid, and what happens when a payment does not go through.
Everything a subscription needs, on one model.
The same records power the dashboard, the API and the invoice, so a change made in one place is never contradicted by another.
Products and plans
One product can carry several plans: starter, growth, scale, internal. Each plan holds its own features, trial length and ordering.
AvailablePrices and intervals
Per unit, tiered, volume or package pricing on daily, weekly, monthly or yearly intervals, with minimum and maximum amount guardrails.
AvailableSubscription lifecycle
Create, pause, resume, renew, expire, reactivate or cancel. Plan changes take effect immediately or at the end of the paid period.
AvailableTrials
Start and end trials explicitly, then convert to a paid period with the same invoice and billing rules as any other renewal.
AvailableAdd-ons
Recurring extras with mid-period proration, or one-time charges billed exactly once. Quantities respect the limits you set.
AvailableCoupons
Percentage or fixed discounts with duration, redemption caps, minimum spend and plan targeting, applied by a single coupon engine.
AvailableBilling runs as a sequence, not a cron job.
A subscription falls due
The next billing date arrives and the subscription is read in full.
An invoice is composed
Plan, add-ons, metered usage, discounts and tax become line items.
A provider collects
The configured gateway charges the payment method for that environment.
The result is recorded
Paid, failed or pending lands on the subscription, and dunning starts if needed.
Billing that follows how people use the product.
Seats are only one way to charge. Define a meter for the unit your customer actually consumes — requests, storage, tokens or minutes — and send events as they happen.
- Sum, count, max or last-value aggregation per meter
- Idempotent ingestion with an external ID per event
- Per-unit, graduated tier or volume pricing
- Usage linked to the invoice, never billed twice
Metered usage · api_requests
Requests recorded
3 duplicates rejected
Tier reached
₦3.20 per 1,000
Usage on invoice
Post-paid
Bring the providers you already have.
Paystack, Flutterwave and Stripe run through working adapters today. A wider catalog can be configured, with availability stated honestly rather than assumed.
Native adapters
4
Paystack, Flutterwave, Stripe, Bachs
Configured providers
25
Including planned adapters
Currencies
8
NGN, GHS, KES, UGX, TZS, RWF, ZAR, EGP
Environments
2
Test and live, separated
Reporting that uses the billing records.
No parallel warehouse to reconcile. Revenue, churn and recovery are computed from the same subscriptions, invoices and payments you see in the console.
Revenue
MRR normalised across intervals, ARR, ARPU, collected and refunded amounts by period.
Retention
Churn by plan, cohorts for up to twelve periods, trial conversion and paid retention.
Recovery
Success rates by provider and method, retry outcomes and the value dunning brings back.
See it against your own pricing.
Bring a plan structure and a provider account. We will walk through how it maps onto subscriptions, add-ons and usage during onboarding.