Integration and API
Your wallet, your players, our games in an iframe.
The integration follows the model crypto casinos already use with game providers: the game runs in an iframe, money stays in the operator’s wallet, and our server talks to yours through signed, idempotent requests.
In development. The operator API is in development. This page describes the design we are building to; field-level documentation will be published before the first game is offered to operators.
Game launch
You request a launch URL for a player session and open it in an iframe in your lobby. The session carries the player identifier you choose, the currency and the language. Games are built for mobile first and scale to desktop.
Seamless wallet
The balance never leaves your system. When a player bets, our server asks your wallet to debit the stake; when a round pays, it asks your wallet to credit the win; a failed round is rolled back. We do not hold player funds and do not keep a parallel balance.
The API in outline
- Your platform calls us to open a game session and get its launch URL, and to read round history and reports.
- Our server calls your wallet when money moves: to read the balance, debit a stake, credit a win and roll back a failed debit.
- Messages are JSON over HTTPS. Amounts are whole numbers in the currency’s smallest unit, so no rounding errors creep in.
- Every call is safe to repeat: the same transaction id always gets the same answer.
Signed, idempotent requests
- Every request between our server and yours is signed with a shared secret and carries a timestamp, so it cannot be forged or replayed later.
- Every money movement carries a unique transaction id. Repeating a request with the same id returns the original answer and never moves money twice, so retries after a timeout are safe.
- An outcome that is unknown, such as a timeout after a debit, is resolved by retrying with the same id, not by guessing.
Demo mode
Every game runs in demo mode with a virtual balance and no wallet calls: for lobby previews, for affiliates and for players who want to try before they bet.
Operator back office
- Round history with lookup by round id, and a replay of any round from its seeds.
- GGR reports by game, currency and period, with export.
- The maths passport of every game and version you have enabled.
Commercial model
Revenue share on the GGR our games generate at your casino. You keep the bankroll, the wallet and the player relationship. Terms are agreed directly; write to us.
Questions and answers
What is a seamless wallet?
The player’s balance stays in the casino’s own wallet. The game provider never holds a balance: it asks the casino to debit a stake and credit a win, round by round. The alternative, a transfer wallet, moves money into the provider’s system before play; we do not use it.
How is a game launched?
Your platform asks our server for a launch URL for a player session and opens it in an iframe in your lobby, on a phone or a desktop. The session carries the player id you choose, the currency and the language.
What happens if a request times out?
Every money request carries a unique transaction id. It is repeated with the same id until there is an answer, and your wallet returns the original result for a repeated id, so money never moves twice. A debit that cannot be confirmed is rolled back with the same id instead of being guessed.
How are requests protected?
Each request is signed with a secret shared with your platform and carries a timestamp. A request with a wrong signature or an old timestamp is refused, so it cannot be forged or replayed later.
Is there a demo mode?
Yes. Every game runs with a virtual balance and no wallet calls: for lobby previews, for affiliates and for players who want to try before they bet.
When will the API be available?
It is in development. Field-level documentation will be published before the first game is offered to operators. Early partners can plan the integration with us now.