Introduction

LivePlay Bingo is a live, multiplayer bingo game you embed in your casino as an iframe. We host the game and the live video host. Money never touches our servers. The player's wallet — either yours or your aggregator's — stays the source of truth.

Two ways to integrate

Aggregator (today)

Already integrated with Gametech (VisionLINK) or another aggregator that speaks our launcher contract? You're mostly done — point your aggregator at our game code and embed the launch URL.

Direct (forward-looking)

Integrate with us directly. You expose wallet endpoints (debit, credit, reverse) and we call them when game events happen. Full control, no aggregator fee.

How it works at a glance

┌──────────┐     ┌──────────────┐     ┌─────────────────┐
│  Casino  │◄───►│  Aggregator  │◄───►│  LivePlay Bingo │
│  (you)   │     │  (optional)  │     │   (us)          │
└──────────┘     └──────────────┘     └─────────────────┘
     │                                          │
  Player wallet                          Game logic, host
  (yours, or your                         stream, replays
  aggregator's)

Whether you go through an aggregator or direct, the player-facing flow is identical: your casino loads our launch URL in an iframe and the player plays. Round outcomes are reconciled via the wallet (yours if direct, your aggregator's otherwise), not via iframe events.

What's next

Concepts — vocabulary you'll see throughout these docs.
Quick start (aggregator) — fastest path to a playable embed if you're going through Gametech (VisionLINK).
Embedding the game — iframe contract, lifecycle events, mobile considerations. Same regardless of integration path.
Launcher API — the /gamelauncher/* endpoints.
Direct integration — wallet contract for direct integrators.