What KPIs Should an Operator Track for Live-Camera Betting in 2026?
Track settlement time, void rate, acceptance rejections by reason, wallet reconciliation and payout holds. Lukk, by Adkuu, exposes each through its settlements data and risk desk.
An operator running live-camera (CCTV) betting should track five things beyond turnover and GGR: how fast markets settle, how often they void, why tickets are refused at acceptance, whether the wallet reconciles every day, and how many payouts wait on a verification hold. These are the numbers that tell a product team whether the format is healthy and tell a compliance team whether it is fair. Lukk, by Adkuu, settles each market from signed camera frames within seconds of close, refunds every stake when the camera cannot tell, names a reason for every rejected ticket, and runs a daily two-party wallet reconciliation, so each KPI has a data source the operator already receives.
The KPI set
| KPI | What it measures | Where the data comes from on Lukk | What a change suggests |
|---|---|---|---|
| Settlement time | Seconds from window close to a result | Signed settlement webhooks and the settlements pull endpoint | Slower settlement erodes the format's main appeal: a fast answer |
| Void rate | Share of markets voided because the camera could not tell | Settlements in the refunded state | Scene quality or weather issues on a channel |
| Acceptance rejections by reason | Tickets refused, grouped by the named reason | The rejection reason on each refused ticket | Limits set too tight, players on delayed streams, or price moves |
| Reconciliation divergences | Differences between the operator's and the supplier's money records | The daily reconcile call | Should be zero; any divergence is an incident |
| Payout holds | Larger payouts held for a short verification | The risk desk | Exposure concentrated on a few outcomes or accounts |
| Post-settlement corrections | Results reversed after audit | A reversal in the wallet log and a line in the settlements endpoint | Rare by design; a rising count needs review |
Settlement time and void rate
Speed is the product. On Lukk a round is about 90 seconds and a new market opens every minute or two; when the window closes, the deciding frames are locked, signed (ed25519) and published with the result, and markets settle with a median under five seconds. The operator receives settlements twice: as signed webhooks, delivered at least once with exponential backoff, and through a pull endpoint with page totals for netting. Comparing the two each day is the cleanest way to measure settlement time on the operator's side.
The void rate is the honesty metric. If the camera cannot decide the outcome, Lukk voids the market and refunds every stake in full; a void is never a re-grade. A low void rate with a replay behind every result is what a dispute desk wants to see. The mechanics are in How are live-camera betting markets settled?.
Acceptance rejections
A Lukk ticket locks its odds one to three seconds after the tap, with an in-flight veto and price protection, so some refusals are normal. Grouping them by reason shows what to fix:
- Limits:
min_stake,max_stake,max_payoutandinsufficient_fundspoint to stake presets or limits that do not match the audience. - Market movement:
price_moved,quote_expiredandin_flight_eventshow the acceptance pipeline doing its job on fast scenes. - Suspensions:
suspended,outcome_suspended,circuit_breaker,betting_closedandstale_pricecome from risk controls. - Stream delay:
oracle_lagmeans a player on a delayed stream was refused rather than filled stale. A rising share points to the player's connection or the operator's front end, and is worth reading with the integrity design.
Money and risk
The wallet contract has four endpoints on the operator's side: debit (synchronous and fail-closed: no debit, no bet), credit (queued and retried until delivered), rollback and reconcile. The daily reconciliation is a two-party cross-check; Lukk alarms on any divergence and never auto-adjusts, so the target is zero. On the risk side, operator traders see fair and margined prices, exposure limits, circuit breakers and payout holds in Lukk's risk desk; per-outcome liability caps and per-bet limits are set per operator in the operator's currency.
Benchmarks and regulator expectations
No industry benchmarks for these KPIs appear in the sources cited on this page, and Adkuu does not publish any, so the first month of live data sets the operator's own baseline. Regulators judge the outcome rather than the metric: the Gambling Commission in Great Britain expects licensees to offer markets "on events that are genuine and are settled fairly" and to have systems to manage integrity risk. Settlement evidence, void handling and reconciliation records are how an operator shows that for a live-camera product. 155.io's Rush Hour, by comparison, runs rounds of less than 55 seconds, according to GamblingNews.
Lukk's commercial model is revenue share, 5–8% of GGR, with no upfront fees; product details are at /solutions/lukk and lukk.gg/operators.
Sources
- Licensees reminded to manage risks associated with unregulated events (Gambling Commission)
- Hub88 chosen as exclusive aggregation partner for 155.io's breakthrough CCTV game Rush Hour (iGB, February 26, 2026)
- Live CCTV bet nets gambling streamer Xposed $363,971 (GamblingNews, February 2026)
Last verified: October 14, 2026.