A prepaid engine built to carry the load
A prepaid business lives or dies on its engine. This one is built for real conditions: millions of accounts, busy-hour spikes, component failures, and pricing that changes with the business. It stays fast under load, keeps running through faults, bends to new products without re-engineering, and still enforces the cut-off the moment entitlement runs out.
What a prepaid engine has to get right
Most billing systems are built to handle the easy cases. The Seshnova engine was built to handle everything — including the cases you haven't thought of yet.
Robustness
Failures happen: networks drop, components restart, traffic spikes. The engine keeps rating and enforcing through all of it, and recovers to a consistent state on its own when something breaks.
Power
Authorisation and balance decisions happen inside the call setup window, in milliseconds, and stay fast at busy hour. An engine that slows under load becomes the bottleneck for the whole service.
Scalability
A billing engine that works for 100 customers must work identically for 100 million. Capacity grows by adding infrastructure, not by re-architecting, and provisioning scales with it.
Flexibility
Products change: new brands, new rate decks, new currencies, new session types. The engine takes new pricing and product structures as configuration, not as engineering projects.
Correctness
Charges must be exact and every event accounted for. Real-time enforcement only counts if the numbers underneath it are right, with a complete record behind every balance.
Built to keep running when things break
Networks fail, components restart, and carriers misbehave. The engine is built so that none of it takes the service down: sessions stay controlled, balances stay consistent, and the platform recovers on its own rather than waiting for an operator to notice.
- Keeps rating and enforcing through restarts and failures
- Recovers to a consistent balance state automatically
- Redundancy at every layer of the platform
- Fails safe: no session runs unmetered
Fast at call setup. Fast at busy hour.
The authorisation decision has to happen inside the call setup window, and it has to stay fast when thousands of sessions are running at once. The engine is built for sustained concurrent load, not just a clean demo.
- Sub-100 ms authorisation at call setup
- Per-second rating across thousands of concurrent sessions
- Busy-hour spikes absorbed without queueing
- Recharge and provisioning bursts handled in bulk
From your first customer to your ten-millionth
Seshnova was designed from the start to handle volume. Account provisioning, balance lookups, and session metering all operate at scale without architectural changes as you grow. Capacity is added by adding infrastructure. You do not re-platform when you succeed.
- Millions of accounts in a single deployment
- Bulk provisioning: issue credentials to millions in one operation
- Fast balance lookups regardless of account volume
- No performance cliff as customer numbers grow
Any pricing, any product, by configuration
Rates vary by destination, time of day, customer tier, and promotion. Brands multiply, currencies differ, and new session types arrive. The engine absorbs all of it as configuration, so launching a product is an operator task rather than an engineering project.
- Thousands of destination rates in a single product
- Peak, off-peak, promotional, and tiered pricing
- Multiple brands and currencies on one deployment
- New products launched as configuration, not code
- API-driven: integrates switches, apps, and portals
Exact charges, with the record to prove it
Underneath the architecture sits the discipline that makes it trustworthy: the right amount charged exactly once, even through retries and restarts, with every balance event written to a permanent record the moment it happens.
- Every charge applied exactly once, even through retries
- Partial session charges handled correctly on disconnection
- Append-only history of every balance event
- Balance at any point in time can be reconstructed
Building it yourself vs. Seshnova
Every company that sells prepaid services eventually faces the same choice. Here is what that choice actually looks like.
Built for the hardest problems in prepaid billing
Robust under failure, fast under load, scalable without re-platforming, and flexible enough to price whatever you sell, with exact rating and a complete record underneath. If you run a prepaid service, this is the engine to put under it.