Rating connected to the offer
Define tariff scope, units, validity and balance rules. Keep supplier cost and customer selling rules distinguishable so reconciliation can explain the commercial outcome.
PAYG & flexible charging
A little data. Or a lot. Your rules.
Offer bundles, reusable balances and sponsored data. Rate usage against your product rules and keep balances and service states in sync.
FLEXIBLE CHARGING / EXAMPLE LEDGER
AVAILABLE BALANCE20.00
demo creditsOpening balance20.00
No usage event yet—
See how an event changes the balance.
Interactive example · sample credits.
Every event has a placeUsage comes in.
Usage comes in.
The rules do the rest.
Rate an event against the product, update the appropriate balance or allowance, and keep the record available for reconciliation. The charging model stays connected to the offer.
Usage recordProduct rules
Rate & account
BalanceUsage historyThe opportunityA simple offer.
A simple offer.
A complete operation.
PAYG gives customers flexibility, but the rules still need to be precise. How usage is rated, when a balance changes and what happens at the end of a benefit all shape the customer experience and the operating workload.
Designed around the use case
What you can put to work.
Balances with a customer journey
Design purchase, top-up, exhaustion and renewal states alongside the service. Explain what the customer can do next and how delayed records or adjustments are handled.
Usage with an operational record
Bring subscriptions, usage records and charging events into one reviewable process. Define record timing, cut-off behaviour and reconciliation for each source.
From idea to operation
A clear way in.
Start with the customer need. Agree the setup. Test the complete service journey.
Choose the charging model
Usage-based balance, fixed allowance or a combination with clear priority.
Define service states
Agree top-up, expiry, exhaustion and customer notification behaviour.
Reconcile the records
Validate rating and balances against representative usage and exception scenarios.
Complete underneathSimple to introduce.
Simple to introduce.
Serious about the systems.
Commercial, service and network capabilities work together. Explore the modules behind this use case and the responsibilities they cover.
Practical questionsBefore you
Before you
launch.
Can PAYG and bundles coexist?
Yes. The rating design should specify which allowance or balance is used first, where each applies and what happens when it expires.
Are balances updated instantly in every case?
Record timing depends on the network and charging integration. The implementation should define the expected latency and how customer-visible balances are reconciled.
Do you publish standard rates here?
Pricing depends on markets, usage, product rules and the commercial setup. A proposal follows an agreed requirements review.
Your next stepTell us where
Tell us where
you want to start.
Bring your audience, your idea or your current setup. We’ll help define the product and the operation behind it.
Talk to Comsand