postMessage from the parent frame. If you are building a Fullscreen extension, contact Nayax to confirm the delivery method.
Receiving the token via postMessage
For Screen, Button with Popup, and Tab extensions, listen for amessage event on the window. Nayax posts an object containing the token, the Cortex base URL, and (for Button with Popup and Tab) the selection context.
selection object is only present for Button with Popup and Tab extensions. Screen extensions receive token and cortexUrl only. Nayax can also pass context via the URL hash (for example, /YourApp/index.html#machineId=12345).
Token payload
The token is signed with RS256. Here is an example payload:Token claims
Validating the token
Validate the JWT signature using the RSA public key for your environment.- QA / Development
- Production
Use the QA key during sandbox development. Switch to the production key when you deploy to production.
Scopes
Scopes control which Nayax resources your app can access. Nayax injects them into the JWT token when your app is registered. There are two scope types:
Scopes are configured by Nayax when your app is registered. Contact your Nayax representative to request the scopes your app requires.
Next steps
Extension Types
See which display type is right for your app and how each one works.
Get Started
Walk through the full developer journey from sandbox to production.