The launch sequence
A player clicks a game in your lobby. Your backend creates a session with the API, receives a launch URL, and the frontend opens that URL in an iframe, webview or new tab. The game then communicates with the wallet through the API for the life of the session.
Session parameters
Launch requests typically carry the game ID, player reference, currency, language, market and return URLs. Keep player references opaque — an internal ID, not an email or username.
Lobby integration
The catalog API provides game metadata — names, thumbnails, categories, market availability — so the lobby is driven by data rather than hardcoded lists. Cache catalog responses and refresh on a schedule.
Mobile and webviews
On mobile, games usually run in a webview. Test orientation changes, session resume after app backgrounding, and return-to-lobby behaviour — these are the most common launch-flow bugs.