Solutions
Billing shaped around the product you sell.
A flat monthly plan, a per-seat contract, a metered API and a retainer all need different behaviour from a billing system. These pages describe how each model maps onto the same resources, and where the beta's limits are.
SaaS businesses
Recurring revenue products need plans, trials, upgrades, invoices and retries. Sobtra runs that lifecycle so your team can stay on the product.
ReadAPI and infrastructure businesses
Usage-based products need metering and idempotent ingestion. Sobtra meters events, aggregates them and turns them into invoice lines.
ReadFintech businesses
Financial products need auditable billing state, payment references and reconciliation data that survives support escalations.
ReadDigital service businesses
Agencies, media products and professional services bill recurring retainers with occasional one-off charges.
ReadEnterprise software
Larger accounts need role-based access, audit-friendly records and invoicing that finance teams recognise.
ReadAI products
Token or credit based products need metered billing that does not punish customers for retried requests.
ReadDeveloper tools
Developer products sell seats and usage, and expect an API that behaves predictably under retries.
ReadSame engine, different shapes
What stays the same across all of them.
Products, plans and prices
Every model starts with the same three objects. A price carries the currency, interval and amount, so changing pricing does not mean rebuilding subscriptions.
Invoices are the unit of record
Whatever you sell, the invoice is what a finance team reads. Line items keep their own amounts for plans, add-ons and usage.
Provider independence
The gateway is a configuration on the merchant, not a property of the subscription, so moving providers does not move billing history.
Not sure which model fits your product?
Describe how you charge today. We will tell you which parts Sobtra covers now and which would need work.