hizi docs

Appearance

Playtech (POP) ​

Playtech POP integration uses the UCIP (Unified Client Integration Protocol) for communication. Messages are exchanged as JSON-stringified strings via postMessage.

Playtech have some requirements regarding when events should trigger and more specific details on when the calls should be used. As they are subject to change by Playtech, the latest documentation can be found here directly on their site: https://pop-playtech.readme.io/docs/client-api (Please speak with the hizi integration team for the password)

Required Methods ​

The following methods are required for integration with Playtech POP:

Page Navigation ​

If the game supports any of the following features, the corresponding method must be called to delegate navigation to the wrapper. Page delegation is enabled when the wrapper includes openpage in w2gInitializationResponse.

  • cashier — delegates deposit page
  • help — delegates help page
  • history — delegates game_history page
  • realityCheck — delegates responsible_gaming page
  • support — delegates support page

If the wrapper provides a delegatePages array in w2gInitializationResponse, only the listed pages will be delegated; all others are silently ignored. If delegatePages is absent or empty, all pages are delegated.

Event Listeners ​

The following events are emitted by the Operator Interface in response to POP wrapper messages:

  • stopAutoplayRequested — when the wrapper sends an interrupt command
  • pauseRequested — when the wrapper sends a pause command (if pause feature is enabled)
  • resumeRequested — when the wrapper sends an unpause command (if pause feature is enabled)