Workflow diagram
Getting the list of games
To get the list of games, Client (Platform) sends a request for a list of providers (Get list providers) and games (Get list games).
Fungamess sends a list of providers and games in response.
Obtaining of a providers list (Get list providers) is optional.
Obtaining of a games list (Get list games) is necessary for games launch.
Retrieval of the games list is required for their display to the players on the platform.
Launching the game
Client (Front) sends a request to launch the game (Start Game).
Fungamess sends requests for session check (Session check), player data (Player details) and balance retrieval (Get balance).
Parameters userId and token are included in the requests.
After receiving responses to these requests, Fungamess registers a session and assigns a player to it.
A response to each of these requests is required.
Without receiving a response to these requests, Fungamess will not be able to send a link to launch the game.
After that a game launch link is generated and passed to the Client (Front).
After receiving the link, the game is launched for the player.
If Client (Platform) doesn't want to display Fungamess when receiving a link, it makes a request and passes the link through its platform.
As displayed below.
Double check of player's data
From time to time, Fungamess may request to recheck the Player's data.
For example, to recheck balance (Get balance).
In response, Client (Platform) provides the requested data to Fungamess.
Placing a bet
After launching the game on the Client (Front) side, the player places a bet.
The Fungamess receives a request to change the player's balance, processes the request, generates a transaction and sends a move funds request (Move funds) to Client (Platform).
Client (Platform) processes the transaction and passes the updated balance to Fungamess.
Fungamess updates the player's balance after each successful transaction.
Bet result
A player's bet is placed on the Client (Front) side.
If the player wins/loses, then, Fungamess processes the data on its side and generates a request to change the player's balance.
The process goes on as described above.
Fungamess generates a transaction, passes it to Client (Platform), that processes it and sends an updated balance to Fungamess.
Player's balance in the game is changed.