hizi docs

Appearance

Playtech (POP) ​

Playtech POP integration uses the UCIP (Unified Client Integration Protocol) for communication. The game and the wrapper exchange messages as JSON-stringified strings through postMessage.

Playtech sets requirements for when events must trigger. Playtech also specifies when to use each call. These requirements can change. Find the latest documentation directly on the Playtech site: https://pop-playtech.readme.io/docs/client-api (Contact 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 game must call the corresponding method to delegate navigation to the wrapper. The wrapper enables page delegation when w2gInitializationResponse includes openpage.

  • cashier: delegates the deposit page
  • help: delegates the help page
  • history: delegates the game_history page
  • realityCheck: delegates the responsible_gaming page
  • support: delegates the support page

If the wrapper provides a delegatePages array in w2gInitializationResponse, the Operator Interface delegates only the listed pages. It silently ignores all other pages. If delegatePages is absent or empty, the Operator Interface delegates all pages.

Event Listeners ​

The Operator Interface emits the following events in response to messages from the POP wrapper:

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