Methods to Implement
Methods to Implement
This section provides a detailed explanation of each method that needs to be implemented in the Operator Account System (OAS) to integrate with GPAS. Each method is described with its purpose, endpoint details, and communication examples for reference.
Required Methods
The following methods must be implemented in your API:
- Sessions: Create a wallet session using an authentication token
- Balance: Retrieve the player’s current balance
- Debit: Process a bet by deducting funds from the player’s balance
- Credit: Process a win by adding funds to the player’s balance
- Rollback: Reverse a previous transaction in case of errors
- Close: Close a wallet session
Method Details
Each method documentation includes:
- HTTP Method and URL: The HTTP method (GET, POST, PATCH) and endpoint URL
- Request Parameters: Description of all parameters required in the request
- Response Parameters: Description of all parameters returned in the response
- Request Example: A sample request showing the format
- Response Example: A sample response showing the expected format
Implementation Notes
When implementing these methods, keep in mind the following:
- All parameters are case sensitive
- All parameters are mandatory unless explicitly marked as optional
- The response format must match the examples provided
- Error responses should follow the format described in the Error Response section
Click on each method name above to see detailed specifications for implementation.