Wallet Integration

Introduction

When integrating ThrillPots to your wallet, you will need to implement what is known as the "Standard Wallet API". This API has been defined by ThrillTech and is what our ThrillGate services uses to communicate with your backend to process:

• Player Authentication
• Transactions
• Transaction cancellations
• Batch transactions# Wallet Integration

ThrillPots Wallet Configuration

IMPORTANT

Please note that when you change the wallet configuration for the ThrillPots service, you MUST restart the ThrillPots service for the changes to take effect. In this section, we will discuss how ThrillPots performs player authentication and jackpot contribution transactions.

When running in a non-development environment (such as staging or production), ThrillPots uses the ThrillGate Service as an integration layer to an operator's wallet API.

NOTE:

ThrillPots also supports an internal, in-memory wallet for development or isolated testing purposes. This wallet is enabled by default in the AIO development container

Types of Wallet Integrations

There are two types of wallet integrations that can be developed:

• Provider-to-Operator integration
• Operator-to-Provider integration (Standard Wallet Integration)

This section is been written for operators that have chosen to do an Operator-to-Provider integration. For a Provider-to-Operator integration, ThrillTech are responsible for implementing the integration to your wallet API and that topic is out of scope for this book.

• Batch transaction cancellations

All communications from ThrillGate are conducted over secure SSL REST calls to your system.

As part of all calls to your system, ThrillGate sends an HMAC in the X-Server-Authorization header which is calculated from the body of the request only. You can use this HMAC value to verify that the request is coming from the expected ThrillGate server.

NOTE: During integration you will receive the secret key that you can use to verify the HMAC value with.