The RubyPlay Seamless Wallet API is an API that has to be implemented by the Operator.
A typical RubyPlay game (which is played on the third-party GC) reports all game-related operation results to the specific GP.
To develop seamless-wallet funding principles the Operator has to implement the following API requests:
- playerInformation
- balance
- debit
- credit
- cancel
The Credit and Cancel requests have to be idempotent. It means the Operator has to ensure that the request with the same transaction ID is not processed twice while the response has to be the same for all duplicate requests (see the more detailed information in the Common Scenarios section of this document).
The Operator has to provide RubyPlay with the service URL for the implemented service as soon as possible, for example, https://integrator-gaming-platform.io/rest/v1/api.
API uses REST protocol with JSON serialization.
HTTP method POST is used for all requests.
HTTP header "Content-Type: application/json" must be included in all requests and responses.
| Round type | freeRound | purchasedFeature | promotionId |
|---|---|---|---|
| Regular round | false | false | null |
| Free round | true | false | not null |
| Buy feature | false | true | null |
| Awarded feature | true | true | not null |