B2B · OPERATOR INTEGRATION

fidra integration docs

fidra is a sandboxed iframe that renders a vertical, playable feed of games inside your casino app. Integration is one iframe plus one message listener.

LAST UPDATED 2026-07-27

What fidra is

The feed runs in its own frame — it never shares a JS context with your app. Your games launch back into your platform (your aggregator URL, your session, your money); fidra's own originals settle either against fidra's demo wallet or against an RPC your page answers (wallet: 'operator'). fidra never holds credentials or funds.

The three integration surfaces

surface	what it is	doc
Mount + events	one script tag, one `Fidra.mount()` call, a schema-versioned event stream out	Quickstart · Events
Wallet RPC	`bet_intent` → `bet_result` cycle for fidra originals settling on your money rail (optional)	Wallet · Sandbox wallet
Measurement	one daily NGR row per pseudonymous user — the incrementality readout fidra is judged on	Measurement

Prerequisites

HTTPS. Provably-fair verification uses crypto.subtle, which does not exist in a non-secure context (including file:// WebViews). Run https://staging.fidra.tech/webview-check.html on your target device before integrating.
A game catalog — your aggregator's game list ({ id, name, provider, category, … }). Without it the feed shows fidra's demo games.
A launch API — something that mints a tokenized session URL for one of your games given an id. fidra calls this via launch_request; you already have this for your own lobby.
A wallet API — only if you set wallet: 'operator'. Not required for your catalog games, which always settle natively on your platform, unchanged.

Environments

environment	URL	use for
Staging	https://staging.fidra.tech	your integration work — redeployed often, carries a permanent STAGING badge
Production	https://fidra-pi.vercel.app	the live demo + pilot embeds

Integrate against staging. Every code sample on this site points at staging. Swap the host for production only at go-live, with fidra's sign-off on the checklist.

What is and isn't configurable

Configurable: theme/accent, games/catalog, operatorId, per-mechanic flags (ghost, clips, tournament, community), wallet mode, player context.
Not configurable, by construction: the responsible-play layer (breather on a loss streak, non-bet card guarantees, audit log). No config key or message can disable it; fidra:v1:pause can only add a breather, never remove one. See Responsible gaming.

source of truth: docs/integration/README.md · docs/EMBED.md fidra is a B2B software supplier — no gambling services operated, no player funds held. g.jgerenaia@tomsons.co