Signed both ways
Your requests to us and our requests to you are signed with different secrets, so rotating one does not weaken the other. A signature is good for 300 seconds and a request replayed inside that window is refused.
Operators
What you get, and what you have to build.
You get games your players open from your own lobby, reports that reconcile against your own ledger, a fairness record you can hand to a regulator, and a sandbox where none of it costs anything. You build one connection to the wallet you already have.
The money never leaves your side
We run a seamless wallet integration, which is the industry's term for a plain arrangement: the player's balance stays in your system and we ask you to move it.
We hold no player funds, run no cashier and ask for no card details. There is no deposit flow to certify on our side and no float to argue about at the end of the month. What we ask of you is the thing your ledger already does.
The stake leaves
A player spins and we ask your wallet to take the stake. The round is already recorded on our side before the request goes out.
The round settles
The outcome was drawn before the money was touched. Settlement runs in a worker holding a lease, so a process dying halfway through leaves a round you can resume.
The payout comes back
We ask your wallet to credit whatever the round paid. If it paid nothing, nothing is asked for, and the round closes where it stands.
A repeat lands once
If a timeout makes us ask twice, answer the second time exactly as you answered the first. The identifier is the same, so the movement is the same movement, and nothing is counted twice on either side.
From first look to live
Sandbox first
Play money against a real integration. The launch, the client, the reports and the round history all behave exactly as they will in production. Until you connect your wallet we hold the play balance; once you do, sandbox rounds call it exactly as real ones will, marked as play money so that nothing real moves.
Nothing is realConformance
A suite runs against your wallet and works through the cases that only ever bite in production: a repeated request, a reversal for something you never applied, a timeout mid-round. You watch each result as it lands.
Before real moneyLive
We switch your brand over once conformance passes and your production address and signing key are in the portal. That switch needs two people on our side, so allow a day for it.
Two people
What you are actually buying
One round at a time
A player has at most one round in flight. A second spin arriving while the first is still settling is refused rather than queued, and the database enforces that rather than the application, which is a different and stronger promise.
Rounds that are whole
A round either exists with the money moved or does not exist. There is no third state to reconcile on a Monday morning.
Reports that reconcile
Daily totals per title, currency and mode; round detail down to the movement identifiers and the fairness record; and a place to post your own figures and be told which rows differ. Not a dashboard to admire, a tool for closing a month.
Money as whole numbers
Every amount in either direction is a whole number of your currency's smallest unit. Nothing is a floating-point number anywhere in the path, so nothing drifts by a hundredth over a million rounds.
Configuration with receipts
Stake levels, models and ceilings are versioned, and a session records the version it opened on. A change we make while a player is spinning cannot alter the round in front of them, and every change carries who made it, when and why.
Documentation
The integration guide, the wallet protocol, the signing recipe, the error catalogue and the sandbox walkthrough live in the partner portal, behind your account. They are generated from the same specification the service validates against, so they cannot drift from what it actually does.
That is also why none of it is on this page. A public summary of an interface goes stale; the generated one cannot.
How long does an integration take?
Opening a game in your lobby is an afternoon. The wallet connection is the real work, and how long it takes depends on your own ledger rather than on us: if you already have an internal transfer that is safe to repeat, you are most of the way there.
Do you host the game client?
Yes. The player's browser talks to us and never to your wallet. You embed the client and listen for a few messages if you want to drive your own loading state and balance display.
What happens if our wallet is down?
The round is recorded before any money moves, and settlement retries with backoff. Nothing is lost and nothing is applied twice. Rounds still pending are visible to both of us on the same screen.
Can we set our own return to player?
You choose from the models we offer: 94.0, 96.8, 98.0 and 100.0 percent. You can also cap payouts, and we will tell you the exact effective return under that cap before you turn it on rather than after.
Which jurisdictions are you licensed in?
None yet. We are built for a GLI-19 style review of the generator and the return to player and we are preparing the submission. We will not claim a licence we do not hold. If you need one in place before you can sign, tell us which and we will tell you exactly where we are.
Can we run more than one title?
Yes, and it costs you nothing further. Every title in the family sits on the same fixed bank and the same connection, so a second one is a setting on your brand rather than a second integration.
The fastest way to judge this is to look at it. Ask for sandbox credentials and the integration guide.