Standard Wallet API: Player Authentication

In order for the ThrillPots system to take wagers (debit the player's wallet) and payout winnings (credit the player's wallet), it needs to be able to authenticate the player with the operator wallet.

This is done by calling the Standard Wallet's auth endpoint, passing in the provided player token and game code to the operator wallet and receiving the required player details (including the token that should be used for transaction calls)

This is done by ThrillGate calling the endpoint defined in endpoints.auth of the Standard Wallet's configuration. An example call's payload would look as follows:

{
    "operator_id": "your_operator_id",
    "brand_id": "your_brand_id",
    "player_token": "token_00001",
    "game_code": "AwesomeJackpotGameCode",
    "currency": "EUR"
}

If successful, the operator wallet must respond with a valid session token and player details that can be used for future transaction calls for this player.

Response example:

{
    "id": "player_00001",
    "token": "session_token_00001",
    "currency": "EUR",
    "balance": 100001927.79,
    "operator_id": "thrilltech",
    "brand_id": "brand1",
    "nickname": null,
    "gender": "?",
    "country": "MT",
    "jurisdiction": null,
    "segments": null
}