Nucleus Gaming - Overview and Integration

Summary

Nucleus Gaming is an HTML5 slot content provider known for its emphasis on 3D/HD visual, cinematic introductions and "collecting" economies (collect, multipliers, respin/hold-and-win). Clients are light, stable in mobile WebViews. Typical integration: SSO → launch-URL, wallet via BET/WIN/JACKPOT, JS bridge events for analytics, CRM and promo.

Who is suitable: operators/aggregators who need visually distinguished slots with understandable mathematics, fast integration and regular rotation of titles.

Portfolio and user experience

Content and mechanics

Video slots: 5 × 3/6 × N; lines/ways; on part of the games - cascades; xN multipliers, expanding/stacked/walking wilds.
Collect/Hold-and-Win/Respin: collect coins/tokens with fix prizes, repeat backs, mini/major/mega levels.
Bonus modes: freespins with special symbols and drum upgrades, pick-bonus, risk play (if allowed by the market).
Bonus Buy/Feature Buy: Availability varies by title and jurisdiction.
Jackpots: fix/local/network - by connection configuration.

UX/UI

3D/HD graphics and short cutscenes without overloading assets.
Readable pay tables, visual progress counters and round history.
L10n: multilingual/multicurrency, local number/date formats, RG messages.

Technology and performance

Client: HTML5 (Canvas/WebGL), lazy-load assets, sprite/audio compression, critical resource preloading.
Delivery: CDN/edge caching, TTL managed, backup launch/CDN domains (failover).
Network: TLS 1. 2+, HTTP/2+; target latency to nearest PoP <150-200 ms.
Mobile: correct resume after folding, resistance to short-term network breaks.

Math, RTP and Limits

RTP pools: usually several profiles (landmarks ≈96 %/ ≈94 %/ ≈92%); selection at the build/catalog level for the market and contract.
Volatility: from low/medium (classic) to high (collect/hold-and-win/multipliers). We recommend the Volatility/Hit Rate display badges.
Limits: min/max bet, auto-spins, session timeouts; for buy-feature - upper value limits.
Currencies: calculation in minor units (integer) with correct rounding according to local norms.

Integration model (high-level)

1. The player → the front of the operator → SSO/JWT (short TTL).
2. Operator/Aggregator API ↔ Nucleus API: creating session, issuing 'launch _ url'.
3. Client (iFrame/new window) ↔ Game Server: game client + JS bridge (postMessage/SDK).
4. Wallet operator API: BET (auth-debit), WIN/PAYOUT (credit), JACKPOT_PAYOUT, rare adjustments.
5. BI/Reports: analytical events, round/transaction uploads, hourly/daily reconciliation.

Environmental requirements

Security: IP-allowlist S2S, request/response signing, secret/key rotation, strict CSP for iFrame domains.
Reliability: queues per player/session, retrays with exponential pause, key deadlock, sticky routing.
Compatibility: current Chrome/Edge/Safari/Firefox, iOS/Android WebView.

Session creation and start (pseudo-REST)

Request:


POST /api/v1/sessions
Authorization: Bearer <operator-key>
{
"player_id": "u_63104",
"currency": "EUR",
"locale": "ru-RU",
"game_id": "nucleus_<slug>",
"return_url": "https://operator.example.com/casino/return",
"limits": { "bet_min_minor": 100, "bet_max_minor": 500000 },
"flags": { "buy_feature": false, "autoplay": true },
"tags": { "vip_level": 1, "aff_id": "AFF-488" }
}

Answer:


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

Client launch: 'launch _ url' in iFrame/window; heartbeat/reauth supported; events across the JS bridge (ACK/NACK).

JS bridge and game events

Client events → to operator: 'GAME _ INIT', 'SPIN/BET', 'WIN', 'FEATURE _ TRIGGER', 'RESPONSE', 'COLLECT', 'BONUS _ START/END', 'JACKPOT _ HIT', 'ER' ERROR'.
Transport: 'postMessage '/SDK, ACK/NACK acknowledgements, strict' origin 'validation, nonce/signatures.
Application: analytics, CRM triggers, personal banners, campaign connection (free rounds/missions/tournaments/drops).

Wallet API and idempotency

Main flows

BET (auth-debit): rate freeze/write-off → 'APPROVED/DECLINED' (+ balance/reason).
WIN/PAYOUT (credit): Credits the win/jackpot → returns the final balance.
ADJUST/REVOKE: adjustments in exceptional cases (full audit trail).

Delivery guarantees

Header'X-Idempotency-Key '(TTL ≥ 24 hours) and deadlock on the operator side.
Queues per player/session → guaranteed order; DLQ for collisions/replicates.
Correlation 'round _ id '/' bet _ id '/' session _ id'.

Example of payment:


POST /wallet/payouts
Idempotency-Key: 3a92-...
{
"player_id": "u_63104",
"round_id": "r_2025_11_02_21_38_40",
"amount_minor": 159000,
"currency": "EUR",
"reason": "round_win"
}

Promo: freespins, missions, tournaments, jackpots

Free Rounds / Free Spins

Issuance via Provider/Promo API or synchronization with bonus engine.
Parameters: fix. bet/denom, number of spins, expiration date, 'game _ id'.
Accounting: winnings in real/bonus-balance; vager - according to operator/market rules.

Missions/Events

"Play N spins," "win ≥ X ×," "activate feature M times," "collect K characters." 'MISSION _ PROGRESS'events.

Tournaments/Leaderboards

Metrics: sum of winnings, max-multiplier, number of spins/triggers. 'TOURNAMENT _ SCORE'events.

Jackpots/Prize-drops

Multi-tier (mini/major/mega), mystery/prize-drops by campaign schedule; 'seed/cap', multi-currency restrictions.
Payments - a separate collection 'JACKPOT _ PAYOUT' with idempotency.

Geo-configuration and compliance

Geo directory: including/excluding titles, choosing an RTP profile, disabling Buy Feature/risk games, age/regional restrictions.
Responsible game: self - exclusion/time auty/limity of deposits/rates/time, RG banners and cookie-consent.
Data/PII: minimization and tokenization of 'player _ id', log retention and export at the request of regulators.
Certification: Use of certified builds/versions for target jurisdictions.

Monitoring, reporting and SLAs

Key metrics

Those: uptime API/Launch/CDN, p95 wallet collabs, asset download speed, JS bridge error rate.
Product: 'Launch → First Spin', 'Spin → Bonus', ARP (B) U, hold, ROI campaigns.
Finance: share of retrays/deduplications, anomalies in amounts, nightly discrepancies.

Export/Reconciliation

Hourly/daily offloads (CSV/JSON/S3) by rounds/transactions/bonuses/jackpots/tournaments.
Reconciliation in minor units by'round _ id/bet _ id/session _ id '; auto-alerts to duplicates/omissions/" dumb" collbacks.

SLO/SLA Benchmarks

API uptime ≥ 99. 95%, CDN assets ≥ 99. 9%; p95 collbecs <500 ms (intraregional).
MTTR - according to the incident plan; separate SLOs for prime time/mass campaigns.

Safety

Transport: TLS 1. 2+, HSTS; strict CSP for iFrame domains.
Access: JWT/OAuth2 (client), IP-allowlist/signature/mTLS (S2S) if necessary, rotation of secrets.
Data: PII prohibition in logs; tokenization/identifier hash; encryption at rest/backup at the operator.
Anti-fraud: spin/bet frequency anomalies, multiple parallel sessions, suspicious ASN/VPN; quotas/throttling/block lists.

Scalability and fault tolerance

Edge cache: manifests/assets/localizations - managed by TTL, manual disability for releases and events.
Rate-limits: per player/session/API endpoint; protection against "storms" of events.

Graceful degradation: simplifying assets/effects, reducing the frequency of events, banner "technical work."

Failover: backup launch/CDN domains; re-issue token without losing context.

Check sheets

For development

SSO tokens: short TTL, clock-skew protection.
Wallet API: idempotent debit/credit, signature, queues, DLQ.
JS bridge/SDK: events, ACK/NACK, secure 'origin'.
Promo API: free rounds/missions/tournaments/drops; vager accounting.
Export: CSV/JSON/S3; completeness of fields (minor units, round/bet/session).

To start

Geo-directory, RTP profiles, disabling prohibited features.
SLO monitoring (API/CDN/Wallet/JS) + alerts.
Nightly reconciliation + duplicate/skip alerts.
RG/cookie banners, local requirements.
Incident Plan/Status Page.

FAQ (Brief)

Running in iFrame? Yes, through 'launch _ url' with consistent CSP/' X-Frame-Options'.
Is Bonus Buy available? By title and market; is configured.
Are there network jackpots? By configuration; payments - individual 'JACKPOT _ PAYOUT'.
How to connect freespins/tournaments? Through Promo/Provider API + analytics events.
How do I choose RTP? At the build/catalog level under the target jurisdiction and contract.

Result

Nucleus Gaming offers visually distinctive 3D/HD slots and standard integration. By following the described patterns (SSO/launch-URL, idempotent Wallet API, JS bridge, promotional campaigns, strict geo-configuration, monitoring and reconciliation), the operator gets a predictable content economy, regulatory compliance and stable peak performance.