Pariplay - Overview and Integration

Summary

• Fusion is an aggregator hub with a single API and a catalog of dozens of studios (internal and external).
• Ignite is an RGS platform for launching/distributing games from third-party studios for a single stack and reporting.
• Promotional tools - freespins, missions/events, tournaments/leaderboards, prize-drops, multi-level jackpots.

The value for the operator is fast time-to-content, geo-certification, unified events/metadata and mature promos without self-written bicycles.

Who fits: operators and aggregators who want single sign-on to a large catalog, built-in campaigns and predictable wallet S2S integration.

Portfolio and user experience

Content

Own/exclusive Pariplay series: video slots (lines/ways, multipliers, hold-and-win/respins, bonus buy), sometimes RNG table games.
Fusion directory: dozens of connected studios in one contract/integration.
Jackpots/drops: fix/local/network levels; mystery/prize-drops by campaign schedule.

UX/UI

HTML5 clients with desktop/mobile/WebView adaptation, quick start of assets.
Clear payment tables, readable feature descriptions, unified Volatility/Hit Rate badges.
Multilingualism/multicurrency, local number/date formats, RG messages.

Platform and Delivery Architecture

Fusion HUB: single API/directory, geo/certification/studio filters, unified taxonomy and events.
Ignite RGS: remote game server (build versioning, stable sessions, round/transaction registry).
Assets/CDN: sprites/fonts/localizations/audio - edge caching controlled by TTL, manual disability.
JS Bridge/SDK: Game Events (SPIN/BONUS/WIN/JACKPOT) for Analytics/CRM/Promo.

Math, RTP and Limits

RTP pools: usually 96/94/92% (and other options) - selected at the build/catalog level for the market and contract.
Volatility: from low to extreme - display badges are recommended.
Limits: min/max bet, auto-backs, timeouts; calculation in minor units for reporting/purse.
Bonus buy/Buy feature: enable/disable by market and game; exposed by flags in metadata.

Promotional tools (campaigns)

Free Rounds/Free Spins: mass distribution by 'game _ id', fix. rate/money, validity period; real/bonus balance winnings; vager - according to the operator's policy.
Tournaments/leaderboards: by winnings, max-multiplier, number of spins; 'TOURNAMENT _ SCORE'events to dimension.
Missions/events: "play N spins," "win ≥ X ×," "activate feature M times"; progress and awards.
Prize-drops/Jackpots: mystery drops, multi-level pools (mini/major/mega), 'seed/cap' parameters, multi-currency restrictions.
Segmentation: geo/VIP/channel/device targeting; campaign schedule.

Integration model (high-level)

1. The player → the front of the operator → SSO/JWT (short TTL).
2. Operator/Aggregator API ↔ Pariplay Fusion/Ignite API: create session, get '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. Promo API : freespins/tournaments/missions/drops.
6. BI/Reports: analytical events, uploads, reconciliation.

Environmental requirements

Safety: TLS 1. 2 +, IP-allowlist S2S, request/response signature, key/secret rotation, strict CSP for iFrame domains.
Reliability: retrai with exponential pause, per player/session queues, key deadlock, sticky routing.
Compatibility: current Chrome/Edge/Safari/Firefox, iOS/Android WebView.

Session creation and start (pseudo-REST)

POST /api/v1/sessions
Authorization: Bearer <operator-key>
{
"player_id": "u_73302",
"currency": "EUR",
"locale": "ru-RU",
"game_id": "fusion_<provider>_<slug>",  // либо ignite_<studio>_<slug>
"return_url": "https://operator.example.com/casino/return",
"limits": { "bet_min_minor": 100, "bet_max_minor": 500000 },
"flags": { "bonus_buy": false },
"tags": { "vip_level": 2, "aff_id": "AFF-552" }
}

{
"session_id": "sess_3b7f...",
"launch_url": "https://fusion.pariplay.example/launch?sess=sess_3b7f...",
"expires_in": 3600
}

Client launch: 'launch _ url' in iFrame/window; heartbeat/reauth - seamless extension; events across the JS bridge.

Client Events and JS Bridge

Client → operator: 'GAME _ INIT', 'SPIN/BET', 'WIN', 'FEATURE _ TRIGGER',

`BONUS_START/END`, `JACKPOT_HIT`, `ERROR`.
Transport: 'postMessage '/JS-SDK, ACK/NACK, strict' origin 'check, handler idempotency.
Purpose: analytics, CRM triggers, campaign connection (freespins/tournaments/missions/drops).

Wallet API and idempotency

Streams

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

Guarantees

'X-Idempotency-Key '(TTL ≥ 24 h), deadlock on the operator side.
Queues per player/session to keep order.
Correlation 'round _ id '/' bet _ id '/' session _ id'; DLQ for collisions/replicates.

POST /wallet/payouts
Idempotency-Key: 8fd1-...
{
"player_id": "u_73302",
"round_id": "r_2025_11_02_17_59_33",
"amount_minor": 214000,
"currency": "EUR",
"reason": "round_win"
}

Reporting, uploading and reconciliation

Export: hourly/daily CSV/JSON/S3 for rounds/transactions/bonuses/jackpots/campaigns.
Reconciliation: reconciliation of amounts in minor units by'round _ id/bet _ id/session _ id'and statuses (success/declined/retry).
Anomalies: auto-alerts for duplicates, omissions, "dumb" collbacks, desynchronization of final balances.

Geo-configuration and compliance

Geo certification/catalog: inclusion/exclusion of titles, selection of RTP profiles, disabling bonus buy/risk games, local RG notifications.
Display rules: age/regional restrictions, cookies, self-exclusion/timeouts/limits.
Data/PII: minimization and pseudonymization; shelf life of logs under the requirements of regulators.

Monitoring, SLO/SLA and operation

Key metrics

Technical: uptime API/Launch/CDN, p95 wallet collabs, JS bridge errors by code, asset download speed.
Product: 'Launch → First Spin', 'Spin → Bonus', ARP (B) U, retention, ROI campaigns (freespins/tournaments/missions/drops).
Financial: share of retrays/deduplications, anomalies in amounts, discrepancies in nightly reconciliations.

SLO/SLA Benchmarks

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

Dashboards/alerts

Correlation'round _ id/bet _ id/callback _ id ', incident tracing, status panel and communication procedures.

Safety

Transport: TLS 1. 2+, HSTS; Strict CSP for iFrame domain.
Access: JWT/OAuth2 (client), IP-allowlist/signature/mutual-TLS (S2S) if necessary, rotation of secrets.
Data: prohibition of open PII in the logs; tokenization/hash 'player _ id'; encryption at rest/backup on the operator side.
Anti-fraud: spin/bet rate anomalies, multiple sessions, suspicious ASN/VPN; quotas/throttling/block lists.

Scalability and fault tolerance

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

Graceful degradation: simplification of assets/effects, limitation of the frequency of events, "technical pause."

Failover: backup domains for Launch/CDN; re-issuing 'launch _ url' when token expires.

Check sheets

For development

• Generation/validation of SSO tokens (short TTL, clock-skew).
• Wallet API: idempotent debit/credit, signature, queues, DLQ.
• JS bridge/SDK: events, ACK/NACK, secure 'origin'.
• Promo API: freespins, tournaments/missions, prize-drops.
• Export: CSV/JSON/S3 formats, field completeness and security.

To start

• Geo-directory, RTP profiles, disabling prohibited features.
• SLO monitoring (API/CDN/Wallet/JS bridge) + alerts.
• Nightly reconciliation and duplicate/skip alerts.
• RG/cookie banners, local requirements.
• Incident plan and status pages.

FAQ (Brief)

Can iFrame run? Yes, through 'launch _ url' with negotiated CSP/' X-Frame-Options'.
How to connect external studios? Through Fusion: single contract/integration, geo/certification filters.
Freespins and tournaments available? Yes, through the promo platform/Promo API and analytics events.
Got a bonus buy? By game/market; is configured.
How do I select an RTP variant? At the build/catalog level for a specific jurisdiction and contract.

Result

Pariplay gives the operator single sign-on to a major catalog through Fusion, the ability to publish studio games through Ignite, and a strong set of promotional mechanics. By following the described patterns (SSO/launch-URL, idempotent Wallet API, Promo API, strict geo-configuration, monitoring and reconciliation), you get a predictable content economy, regulatory compliance and peak resilience.