The game launch scheme:
- The Operator provides the lobby page with the link for the integrated game.
- A player registers in an online casino (the GC) and logs in to the lobby page.
- The player clicks on the RubyPlay game link. The player-specific URL for the game launch contains player information (playerSession={sessionToken}). The playerSession token must be generated by the Operator (see the full description of each field of the game launch URL in the RubyPlay Seamless Wallet Integration Guide).
- The game launch URL follows to the RubyPlay backend side (the RGS). The playerSession field, retrieved from the URL, distinguishes the current player from the others.
- All additional player information will be requested from the Operator's GP system. The RGS sends the request to /playerInformation endpoint (see the Player Information section of this document) and receives the info about the player registered in the GC.
- If the response from /playerInformation is successful (HTTP Status Code 200 "OK" and the response body corresponds to the API), then the needed information is now present on the RGS side. The retrieved player will be created/updated in the RubyPlay system.
- After successful verification of the playerSession parameter, all further requests, such as /balance, /credit, /debit, /cancel to the GP related to the current player, will be sent with the mentioned playerSession parameter. It will be presented as the sessionToken field in the request body.