PatePlay, end to end

PatePlay is a game studio. Once connected, PatePlay's servers call OneHazel for every bet and win. OneHazel passes each call on to your casino's wallet, through the contract you already passed. PatePlay needs your wallet and player modules.

This page covers only what is specific to PatePlay. Creating the connection, adding the keys and going live are steps 6, 7 and 10 of the journey. Do them there, with pateplay as the vendor.

What you need before you start

• wallet and player shown as Conformant: steps 1 to 4 of the journey.
• An agreement with PatePlay and a contact there who sets up your site.
• A real player account on your casino that you control, with a small balance, for the first spin.

Step 1. Get your values from PatePlay

PatePlay issues your values when they set up your site: ask your contact there. The connection has six fields. Three hold PatePlay's values, one is optional and two stay empty:

Field on the connection	Value	Where it comes from
API Key	api_key	PatePlay, when they set up your site. It identifies your site on every PatePlay call. If PatePlay asks you to choose the key instead, choose 32 characters and send it to them.
API Secret	api_secret	PatePlay, with the key. It signs every PatePlay call and never travels with one.
Site Code	site_code	PatePlay. Your site's name at PatePlay.
Default Player Country (ISO alpha-2, optional)	default_country	You, if you want it. A two-letter country code, such as mt, that OneHazel sends to PatePlay when a player record has no country.
Your casino wallet (PAM) base URL	provider_base	Nobody. Its label says "only if your casino is not connected through the OneHazel contract": leave it empty.
Your casino callback key	provider_callback_key	Nobody. Same label: leave it empty.

Filling either of the last two sends PatePlay's calls past your contract wallet to a different address.

Keep the values in your password manager, never in a file in your code. You enter them once, in step 7 of the journey. There your agent asks you for each one by its field name, once, and never repeats it. Word for word:

Vendor credentials: ask your human for each value once, by its field name, pass the values straight to connect_set_credentials, and never print, log, echo or commit them; the response returns only field names.

What you should see

Three values from PatePlay: key, secret and site code. Key and secret are usually 32 characters each.

Step 2. Give PatePlay your wallet address

Do this once step 6 of the journey has created the PatePlay connection. Open the connection. The address in your browser ends with /operator/connections/ followed by the connection id, such as conn_1a2b3c4d5e6f. Your agent can also tell you the id.

Send PatePlay this address, with your connection id in place of <connectionId>:

https://api.onehazel.com/pateplay/<connectionId>

PatePlay registers it with your site code. Every bet and win for your site then arrives at this address.

What you should see

PatePlay confirms the address is set for your site.

What PatePlay sees before and after Go live

Until the connection is Active, OneHazel refuses PatePlay's calls for your site with NOT_AUTHORIZED "Unknown site." That is expected while you work through the journey.

When you click Go live in step 10 of the journey, the result for PatePlay is amber: "This connector has no public check; OneHazel verifies it from the first wallet call. If the values are correct, click Go live anyway." That is normal: PatePlay calls OneHazel, so there is nothing to send its keys to before the first game. If the values are correct, click Go live anyway. From then on PatePlay's calls are accepted, and they reach your wallet marked live.

Step 3. Add a PatePlay game to your catalogue (for your platform team)

This step changes your casino's own platform. Hand it to the team that runs your casino's game catalogue. OneHazel does not build PatePlay game links: your casino does, from its own catalogue. This is the exception to the launch module, where OneHazel returns a game_url for a connector that carries a launch template, and PatePlay carries none.

Hand this box to your platform team

Add each PatePlay game as an active game in the catalogue. Its launch link is PatePlay's launcher address with three values added:

• authCode: a fresh single-use launch token for each launch, from your wallet's session start.
• siteCode: the Site Code from step 1.
• game: the PatePlay game code.

Add the player's language too, such as language=en:

<PatePlay launcher address>?authCode={token}&siteCode=<your site code>&game=<game code>&language={lang}

Ask PatePlay for the launcher address and the game codes you may offer.

What you should see

The game listed in your casino's lobby.

Step 4. Spin it

1. Log in to your casino as the real player account from the box at the top.
2. Open the PatePlay game from your lobby.
3. Place one small bet.

Use a real player, not your test player. On app.onehazel.com PatePlay's calls arrive marked live, and the adapter refuses live calls for test players.

What you should see

The game loads. Your PAM records a bet for that player, and a win if the spin paid. The balance shown in the game matches your PAM.

If the game does not open

PatePlay shows its own error. The message tells you which step to recheck:

PatePlay error	Recheck
NOT_AUTHORIZED "Unknown site."	Step 10 of the journey: the connection is not Active. Or step 2 here: PatePlay has the wrong connection id.
NOT_AUTHORIZED "Invalid API key or signature."	Step 7 of the journey: the key or secret on the connection is not the pair PatePlay uses for your site.
NOT_AUTHORIZED "Invalid site code."	Step 7 of the journey: the Site Code does not match the one PatePlay uses.
INVALID_AUTH_TOKEN	Step 3 here: each launch needs a fresh token. A token works once.

For anything else, see Troubleshooting.