Slot Aggregation Integration

Casino integrates a wide range of third-party slot games via the Eva aggregation platform. This integration provides centralized access to multiple providers, handling everything from game launches to wallet callbacks and promotional features.

Slot integration documentation: https://integration-hub.eva-stage-pm8games.com/docs/operator/index.html

1. Integration Overview

The Eva aggregation platform acts as a unified layer between Casino and dozens of slot providers. It enables:

• Centralized game launch API
• Secure session management
• Real-time wallet transaction relay (bet, win, refund)
• Provider-agnostic handling of promotions and game metadata

2. Non-Functional Requirements

• All wallet endpoints must be hosted over HTTPS
• JSON payloads must gracefully ignore unknown fields (forward compatibility)
• Authentication is handled via HTTP Basic Auth + Partner Key headers
• Requests are IP-restricted (whitelisted Eva servers only)
• Wallet API must meet strict performance targets (e.g., sub-450ms for P99 responses)

3. Game Launch Flow

To launch a game, the Casino frontend constructs a URL to Casino BE-endpoint with parameters such as:

• gameId: internal Eva game identifier
• channel: desktop or mobile
• partnerKey: Casino’s assigned partner ID
• sessionToken: the user’s active session token (omitted for demo mode)
• language: user’s preferred language
• lobbyUrl: fallback URL when exiting a game

The resulting URL is opened in an iframe on the frontend.

4. Wallet Integration (Callback API)

Eva relays user game activity through a standardized set of wallet API endpoints implemented on Casino’s backend:

Player Endpoints

• GET /players/accounts/:playerId
• GET /players/sessions/:sessionToken

Transaction Endpoints

• POST /transactions/bet
• POST /transactions/win
• POST /transactions/refund
• POST /transactions/promoWin
• POST /transactions/tournamentWin

Each call contains transaction data such as:

• amount, currency, playerId, gameId, roundId, txId, reason

Responses must include the updated balance state and transaction confirmation.

5. Wallet Transaction Format

Each transaction request includes:

• Identifiers: playerId, gameId, roundId, provider, txId
• Financials: amount,(minor units) currency
• Metadata: reason, freeSpinData, tournamentId, etc.

Wallet response must return:

• balance: broken into main, bonus, and locked
• tx: confirmation details, unique ID, and processed flag

6. Error Handling & Idempotency

• All wallet endpoints must handle duplicate txId submissions safely by returning processed: true if already handled
• Errors must be returned with JSON structure: errorCode, message, and timestamp
• Common errors: insufficient-balance, session-expired, invalid-amount, etc.

7. Game Metadata API

Eva provides a data API for syncing game catalogs, filtering games, and managing visual assets. Casino uses this to:

• Sync the latest provider game lists
• Filter by gameId, provider, productType, or enabled
• Cache game thumbnails, categories, and volatility
• Custom branding can be applied to games by overriding default thumbnails via Eva’s image endpoints.

8. Free Spins System

The platform supports free spin promotions managed through the aggregator:

• Admins define campaigns (bet amounts, validity, per-currency amounts)
• Spins are issued to users via API call
• Spins can be cancelled (per-user or full campaign)
• Eva handles bonus context during gameplay (e.g., free spin payout routing)

9. Admin Capabilities

From the admin panel, Casino can:

• Enable or disable games globally or per provider
• View game usage statistics
• Attach challenges or missions to specific games
• Override thumbnails, sort order, or categories