Authentic Gaming - Overview and Integration

Overview

Authentic Gaming is a Live provider with a strong specialization in roulette and "ground" broadcasts (from real casinos), as well as studio and auto variations. The portfolio is complemented by fast modes, advanced statistics and promo widgets. The tech stack is focused on low latency (WebRTC) with fallback on HLS/DASH, sustainable delivery via CDN, and real-time event bus for bets/results.

Who fits: operators and aggregators focusing on premium roulette tables, geolocal "ground" feeds and predictable server-to-server integration with a wallet.

Portfolio and user experience

Gaming verticals

Roulette: Real Casino Roulette (streams from the floor of real casinos), Studio Roulette (classic/themed), Auto Roulette (no dealer), speed/turbo modes, hot/cold tracks, favorites and quick replays of bets.
Blackjack/Baccarat (with configurations): classic and speed options, Bet Behind/side bets - depend on the table.

UX/UI

Adaptive HTML5 client, chip presets, quick betting combinations, spin/hand history.
Multilingual interfaces, multicurrency, local date/number formats.
Moderated chat, limits/rules prompts, non-invasive RG prompts.

Responsible play

Rate/time limits, age/geo table hiding, localized banners and alerts.

Streaming, protocols and performance

Video: WebRTC for low latency (~ 0. 5–2. 5 s with stable network); HLS/DASH degradation fallback.
Delivery: CDN/edge-PoP, sticky routing to the nearest node, health-checks and fast failover.
ABR: adaptive bitrate, seamless quality switching; on mobile - hardware decoding.
Network: latency up to edge <150-200 ms, HTTP/2 +, TLS 1. 2 +, prioritizing multimedia traffic.

Math, limits and calculations

RTP/House Edge: comply with the rules of a specific table and side rates (disclosed in the rules of the table).
Limits: global by table and personal by player; VIP levels; separate ceilings for side bets.
Currencies: calculation in minor-units; conversion/display - on the operator side; correct rounding by jurisdiction.
Commercial models: RevShare/Flat/Hybrid - contractual conditions that do not affect client mathematics.

Integration architecture (high-level)

1. Operator → frontend player → SSO/JWT

2. Operator/Aggregator API ↔ Authentic API - Create/Validate Session

3. ↔ WebRTC/HLS Client - Video Stream

4. ↔ WebSocket Client - Live Bets/Events

5. Authentic → Webhook/Callback - authorization of write-offs/payments

6. Auth Debit/Credit ↔ Ledger/KYC/AML

7. BI/Anti-Fraud/Monitoring - Audit, Retray, Reconciliation

Environmental requirements

Security: JWT/OAuth2 for sessions; IP-allowlist and (as agreed) mutual-TLS/signature for S2S; short TTLs, key rotation.
Performance: auto-scaling WS-shards, balancer with sticky-sessions, limit on simultaneous subscriptions.
Compatibility: current Chrome/Edge/Safari/Firefox, iOS/Android WebView.

Sessions and Authentication

SSO pattern

The operator generates a short-lived token with 'player _ id', currency, locale, limits/VIP and 'return _ url'. The provider returns' launch _ url '.

Example (pseudo-REST, S2S):


POST /api/v1/sessions
Authorization: Bearer <operator-key>
{
"player_id": "u_10642",
"currency": "EUR",
"locale": "ru-RU",
"limits": { "table_min": 0. 50, "table_max": 10000. 00, "side_bet_max": 200. 00 },
"meta": { "vip_level": 2, "return_url": "https://op. example. com/return" }
}

Answer:


{
"session_id": "sess_f3c1a...",
"launch_url": "https://authentic. example/launch? sess=sess_f3c1a...",
"expires_in": 3600
}

Starting the client

Via 'launch _ url' in iFrame/new window (CSP/' X-Frame-Options' agree). Heartbeat/refresh extends session.

Bets and Events (WebSocket)

Event types

Игровые: `ROUND_OPEN`, `BETS_OPEN`, `BETS_CLOSED`, `ROUND_RESULT`

Transactional: 'BET _ PLACED', 'BET _ ACCEPTED/REJECTED', 'PAYOUT'

Service: 'PING/PONG', 'ERROR', 'RECONNECT _ HITT'

Example result:


{
"type": "ROUND_RESULT",
"table_id": "rc_casino_floor_02",
"round_id": "r_2025_11_02_15_18_45",
"result": { "number": 32, "color": "red" },
"payouts": [
{ "bet_id": "b_7741", "amount_minor": 360000 },
{ "bet_id": "b_7742", "amount_minor": 0 }
],
"server_ts": "2025-11-02T13:18:47Z"
}

Channel reliability

Auto-reconnect, restoring subscriptions and current round status.
Back-pressure/client message throttling.
Deduplication by 'bet _ id '/' round _ id' on the provider and operator sides.

Purse money transactions and collbacks

Streams

Auth-debit (rate): request for write-off/freezing; 'APPROVED/DECLINED 'statement response.
Credit (disbursement): initiated by the provider; the statement confirms and returns the resulting balance.
Reconciliation: periodic reports on rounds/transactions for reconciliation with the ledger.

Delivery Guarantees

Idempotency via 'X-Idempotency-Key' (TTL ≥ 24 h), message numbering per player.
Retrai with exponential pause, ordinal processing, key deduction.

Example of a collbeck (payout):


POST /wallet/payouts
Idempotency-Key: 2a9d-...
{
"player_id": "u_10642",
"round_id": "r_2025_11_02_15_18_45",
"bet_id": "b_7741",
"amount_minor": 360000,
"currency": "EUR"
}

Lobby settings and promotional tools

Table catalogs: grouping by type (Real Casino/Studio/Auto), dealer language, limits, VIP levels.

Promo: Banners, Tournaments, Missions/Quests, Hot Numbers, Top Wins, Analytics Events

Geo-filters: whitelist/blacklist jurisdictions, local RG requirements.
UI parameters: auto-entry to a given table, hiding chat, presets and custom chip values.

Scalability and fault tolerance

Multi-region: choosing the nearest RoR/studio, ASN/geo-routing, sticky sessions.
Protection against event storms: quotas for WS subscriptions and rate changes, queues.
Degradation: fallback on HLS, "lite-UI" for weak devices or turbulent network.

Safety and compliance

Encryption: TLS 1. 2+, HSTS; SRTP for WebRTC media.
Access: JWT with short TTL, IP-allowlist/signature/Mutual-TLS for Collbecks.
PII minimization: masking identifiers, no open PII in the logs.
Anti-fraud: behavioral signals (betting frequency anomalies, multiple sessions, suspicious ASN/VPN), risk flags and throttling.
RG/Regulatory: self-exclusion, timeouts, limits; local consent cookies/banners.

Monitoring, Reporting and SLAs

Metrics

Uptime media/WS, p50/p95 latency,% frame-drops, collback errors (codes/shares).
'Launch → First Bet'conversion, average check, table/language hold, ROI promo.
Operating rooms: retrai/deduplication, reasons for wallet deviations.

SLO/SLA Benchmarks

Media ≥ 99. 9%, API ≥ 99. 95% uptime.
Collbecks p95 <500 ms within the region.
Reconnect WS p95 <3-5 s, automatic subscription recovery.

Dashboards/alerts

Correlation'round _ id/bet _ id/callback _ id ', incident traces, status panel and communication rules.

Testing and acceptance

1. Sandbox: individual keys, dummy round/limit outcomes, coefficient test tables.
2. E2E: successful/rejected bets, WS breaks, double 'PAYOUT' (idempotency check), limit conflict.
3. Load: Prime time/tournament peaks, ABR switching, degradation to HLS.
4. Security: negative JWT cases, signature of collbecks, rate-limits, CORS/CSRF policies.
5. Reconciliation: reconciliation of provider reports with the ledger (amounts, statuses, rounding).

Integration best practices

Make the operator's wallet a source of truth; all S2S calls are idempotent.
Post collabs to queues ('bets', 'payouts', 'recon') with priorities/retras.
Cache limits/table configs on edge (TTL + manual disability).
Use feature-flags to phase in tables/languages/VIP limits.
Plan fail-over: fallback protocols, "technical pause" window, compensation promos.
Log PII hashes and correlation keys instead of direct identifiers.

Checklists

For development

JWT/SSO Generation and Validation
WebRTC + fallback HLS Client
WS client with auto-reconnect and back-pressure
Idempotent S2S endpoints, retrays, deduplication
PII masking, key/secret rotation

To start

L10n (languages, currencies, formats)
Geo-Filters and Jurisdictional Constraints
SLO Monitoring (API/Stream/WS) + Alerts
Nightly Reporting and Reconciliation
Incident Plan and Status Pages

FAQ (brief)

Can iFrame run? Yes, through 'launch _ url' with consistent CSP/' X-Frame-Options'.
Are Real/Auto/Studio Roulette supported? Yes, the set is determined by the connection configuration.
How to handle communication breaks? Auto-reconnect, restore subscriptions/rates, idempotent collbacks.
Any promotional tools? Banners, tournaments, missions/quests, hot numbers, analytics events.
How does reconciliation work? The provider publishes reports; the operator checks the ledger by'round _ id/bet _ id '.

Total

Authentic Gaming is a strong Live provider for roulette tables (including terrestrial broadcasts) with a modern integration model. Following the proposed patterns (SSO, WebRTC + WS, wallet with idempotent collars, SLO monitoring, RG/compliance), the operator receives a stable Live vertical, predictable economy and readiness for peak loads.