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:

Reality Check ​

Playtech can reject a bet with a reality check. A regulation or the operator can enable this check. When it happens, the bet call fails with error 38 (REALITYCHECK). See Response Codes. The reality check occurs only on a bet. It never occurs on a win, a cancellation, or the close of a game round.

Playtech requires a dialog with two buttons: continue and stop. Do these steps:

  1. Show the text from passThroughData.clientMessage.msg on the failed reply. Playtech sets this text. It can contain HTML links (<a></a>). Render them as links.
  2. Show a continue button and a stop button.
  3. When the player selects continue, call sendRealityCheckResponse with continued: true. Playtech then resets the reality check counter. The player can then place the bet again.
  4. When the player selects stop, call sendRealityCheckResponse with continued: false. Then call quit. The game must close itself.

WARNING

If the game does not call sendRealityCheckResponse, Playtech does not reset the counter. The next bet then fails with the same reality check again.

A simpler fallback is permitted. Show the text with one "OK" button only. When the player selects "OK", call quit. This closes the game, so the player experience is worse.

The backend keeps the identifier of the reality check from Playtech (actionId). It sends this identifier back to Playtech when the game calls sendRealityCheckResponse. The game does not handle actionId.

Do not confuse this flow with the realityCheck method. For POP, that method only opens the responsible_gaming page of the wrapper.

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)