Balance

Operation executed by the GPAS which prompts balance information.

Endpoint Details

• Method: GET
• URL: /wallets/balance

Request Parameters

Name	Type	Request	Description
walletSessionId	String	QueryString	Wallet Session
x-parent-system-id	String	Header	Unique GPAS identifier in the operator system
x-signature	String	Header	Signature of the message for communication security, it must be in capital letters

Response Parameters

Name	Type	Request	Description
code	String	Body	Status of request. (BINGO, CASINO, SPORT, REAL, BONUS)
leftBalance	Decimal	Body	Total user balance
subWalletsSummary	List	Body	Identify how the user’s balance is made up

Request Example

GET /wallets/balance?walletSessionId=3fa85f64-5717-4562-b3fc-2c963f66afa6
HEADER
x-parent-system-id: BL13GT
x-signature: SHA1(query string + secret key)

Example Signature

• QueryString: walletSessionId=3fa85f64-5717-4562-b3fc-2c963f66afa6
• SecretKey: Ax34deSfgdB
• SHA1: Encryption Function
• SHA1(walletSessionId=3fa85f64-5717-4562-b3fc-2c963f66afa6Ax34deSfgdB)
• Signature: 52D7382EB6D253CECBD0414AE0CF5B673C9D2D0C

Response Example

{
  "code": "BINGO",
  "leftBalance": 9150,
  "subWalletsSummary": [
    {
      "code": "REAL",
      "leftBalance": 9000,
      "subWalletsSummary": null
    },
    {
      "code": "BONUS",
      "leftBalance": 150,
      "subWalletsSummary": null
    }
  ]
}

Implementation Notes

• This method should return the current balance for the player associated with the wallet session
• The response should include both the total balance and a breakdown by wallet type
• The balance returned should be in the currency associated with the player’s account
• This method is typically called before and after debit/credit operations to verify the balance