Billing stream
Every charge, renewal, retry and refund lands as an event — per market, per operator, per gateway. What you see streaming is the shape of a real day.
SectionDemoEnvironmentSanitisedDataIllustrative
← Back to homeQuantum Rail · live-ops
The console our ops team lives in.
A sanitised recreation of the Quantum Rail operations console. The panels, events and workflows are the real thing; the numbers are illustrative and no live customer, subscriber or operator data is shown.
rail.quantum.internal / live-opsDEMO · SANITISED
MRR · rolling€0+12.4% WoW
Active subs04 markets
Events / min0all gateways
Checkout CVR0.00%rolling 7d
Uptime · 30d99.98%all markets
Revenue — 60 day€ settled
events.stream--market=all
MarketsMRR · WoW
| Market | Gateways | MRR | Δ | Status |
|---|---|---|---|---|
| PL · Poland | Play · T-Mobile | €51,980 | +6.1% | OK |
| RO · Romania | Orange · Vodafone | €34,210 | +4.2% | OK |
| BiH · Bosnia | Regional | €12,410 | +2.8% | OK |
| FR · France | Orange | €28,830 | +5.4% | OK |
SettlementT+1 · per gateway
- batch 08-12 · PLsettledT+1 · drift 0.00%
- batch 08-12 · ROsettledT+1 · drift 0.00%
- batch 08-12 · BiHsettledT+1 · drift 0.01%
- batch 08-13 · FRpendingexpected T+1
alert · resolvedretry spike · FR · Orange · resolved 14:32 by dunning policy
What you’re looking at
Reconciliation
Operator settlement reconciled against platform events daily. When a batch drifts, finance sees it inside one settlement cycle, not at month-end.
Alerting
Retry spikes, revenue drops and compliance flags page the right team. The FR retry spike in the feed is what an ordinary Tuesday looks like.
The real thing
This view, on your rails.
Operators and partners get role-based access to the live console for their own markets — finance sees settlement, compliance sees consent flows, everyone sees the same numbers.