By the Zion Engineering editorial team · reviewed under our editorial standards
Short answer: real-time charging for value-added services (VAS) requires an online charging system that can authorise, rate and deduct balance before the service is delivered, typically within tens of milliseconds. Achieving that reliably depends on the charging interface to the operator, an in-memory rating layer, idempotent transaction handling and a mediation path for reconciliation.
What real-time charging means for VAS
Value-added services include SMS and USSD applications, subscription content, ringback tones, games, lotteries and micro-payments. In an offline model, usage is recorded and billed later. In a real-time model the platform checks the subscriber's balance and reserves or deducts it before delivering content, so prepaid subscribers, who make up most of Ethiopia's mobile base, can be charged instantly.
The core building blocks
- Charging interface: connection to the operator's online charging system, usually via Diameter (Gy/Ro) or an operator-specific API. This is where the authorise-and-deduct happens.
- Rating engine: applies tariffs, bundles, promotions and free periods. It must be fast and configurable without code changes.
- Subscription manager: handles opt-in, renewals, retries for insufficient balance, and opt-out rules required by the regulator and operator.
- Content and service layer: the actual service delivered after successful charging.
- Mediation and reconciliation: collects records from all components so revenue can be reconciled between operator, platform owner and content providers.
Designing for low latency
Sub-100-millisecond responses are achievable, but only if the critical path is short. Practical techniques include:
- Keep subscriber, tariff and session data in memory, with persistence handled asynchronously.
- Use connection pooling and keep-alive sessions to the charging system rather than opening connections per request.
- Make every charge request idempotent with a unique transaction ID, so retries after timeouts never double-charge.
- Separate synchronous charging from asynchronous work such as notifications, reporting and analytics.
- Load-test at realistic peak traffic, including campaign spikes, not just average volumes.
Failure handling matters as much as speed
Timeouts will happen. The platform needs a clear policy for each failure mode: what to do when the charging system does not respond, when a deduction succeeds but content delivery fails, or when a renewal fails for low balance. Refund and reversal flows must be automatic and auditable. Subscribers who are charged without receiving service generate complaints and regulatory risk.
Compliance and subscriber trust
Operators in Ethiopia apply strict rules to subscription services: explicit opt-in, clear pricing messages, easy opt-out and limits on renewal retries. Building these rules into the subscription manager from the start is cheaper than retrofitting them, and it protects both revenue share and the operator relationship.
How Zion Engineering can help
Zion Engineering's VAS and VISP platforms team designs and integrates messaging, USSD, content and subscription billing platforms, supported by our software development and cloud practices. Contact us to discuss integration with your operator or a review of your current stack.