Skip to content
GPAS Docs

Introduction to GPAS

GPAS - Game Provider Account System

Overview

This document describes requirements and conventions that a third party platform must comply with to be able to integrate with Game Provider Account System (GPAS).

GPAS needs to hold player balance in remote Operator Account System (OAS). Because of this, OAS API must have the following basic requirements:

  • It must work as an independent platform and allow integration with GPAS via standard web service technology.
  • It is responsible for player registration, verification and banking.
  • It must provide the best connection performance and security.
  • It must provide real time information about player balance and must manage possible exceptions.
  • It must be able to audit balance movements.

Purpose of This Documentation

This integration guide provides detailed information about:

  1. Security requirements for establishing connections
  2. Communication protocols and data formats
  3. Sequence diagrams showing the flow of information
  4. Detailed API method specifications
  5. Error handling and edge cases

By following this documentation, third-party platforms can successfully integrate with the GPAS system and provide a seamless gaming experience for players.