Overview

The primary purpose of this document is to communicate the basic set of methods and flows of the RTG integration with the Seamless Wallet solution so that business and technical implications can be assessed and understood, and so that the design activities can have a clear understanding of the business needs.

Terms Used in this document

  • Seamless wallet - a 3rd party provider of a digital wallet, which exposes APIs to allow RTG to implement and connect in order to allow for a single wallet across multiple products.

  • Operator - Refers to the entity which is responsible for integrating with the RTG APIs and transfer funds via a digital wallet.

  • <RTG API BASE URL> - its the URL for the specific casino on which you're testing and integrationg. \*[Please consult your implementation manager for the corret URL\]*.

  • <Wallet URL> - this is the URL of the main seamless wallet RTG should integrate with.

How to start integration with RTG

  1. Make sure you know who's your implementation manager.

  2. Authorization - The RTG APIs are using API Keys and IP whitelisting to validate and authorize the calling node, you will need to receive the API Key and provide your IP for RTG whitelisting before performing any tests against the RTG Server [Please contact your implementation manager to get your API key and instruction for installing it].

  3. Access - Have the correct URLs for testing (staging) environments [Please contact your implementation manager to get the correct URLs].

  4. Games - Get the list of RTG games based on the business term [Please contact your implementation manager for more details].

  5. Understand - Read this document to understand how to implement the different fundamental RTG APIs, please contact your implementation manager and the technical skype chat with any issues.

  6. Implement and test - implement the different APIs and test its working as expected.

Integration Notes

  • All API response date/time are in UTC+0.

  • Date/time format in all date fields should conform to ISO 8601. Example 2012-04-23T18:25:43.511Z. For more details, please refer to the link here.

  • All API input date/time formats can be time-shifted to the appropriate timezone. Example 2012-04-23+08:00 to denotes UTC+8.