The domain
Everything starts with the address you choose for your sportsbook. That domain joins your site’s list of authorised domains, and that is where, and only where, the book will agree to open.
Integration, wallet & security
Light integration, a wallet that fits, accounts no one can rewrite
This page is for the people who make things work: the technical lead, the payments team, whoever answers for the numbers. It explains how the sportsbook connects to your site, how it talks to your wallet and which safeguards protect every movement of money.
- One domain, one line of code
- Our wallet or yours
- Signed calls
- Immutable ledger
One domain, one line of code
From domain to live book, without a development project
The integration is deliberately minimal. The sportsbook runs on our infrastructure and reaches your page through an iFrame, so on your side there is nothing to install, host or maintain. From the start of work to a book ready for players takes 72 working hours.
The public key and one line of code
You receive a public key that identifies your site and a single-line snippet. Once it sits in your page, the snippet loads the book inside an iFrame, with your brand and your settings.
No infrastructure to run
Servers to buy, apps to publish, updates to schedule: none of that is your concern any more. Every improvement we release reaches your site automatically, without you lifting a finger.
The real technical effort
If you use our wallet, you do not need a developer to go live. The only technical work concerns operators with an existing player wallet to connect: roughly half a day, done by your developer together with our team in a single session.
Two wallet models, the same experience for the player
The right wallet depends on where you are today. A brand-new project often prefers not to handle money at all; an established platform wants the money to stay exactly where it is. The sportsbook supports both scenarios, and the player sees the same interface either way.
Our wallet
The book handles the entire financial side: it opens player accounts, records deposits and withdrawals and keeps the balance up to date. It is the fastest route for anyone starting from scratch, because it removes the only technical step of the integration and leaves your team free to focus on marketing and acquisition.
- Player accounts
- Deposits and withdrawals
- Balance management
Your wallet
The balance lives in your system and stays there. The book holds no money: when a player confirms a bet or collects a win, it asks your system to debit or credit the amount. The player has a single balance for casino and sport, with no transfers between accounts.
- Debits and credits on your system
- The book holds no cash
- One balance for casino and sport
How money moves with the seamless wallet
- 1
The player confirms the betslip in the book.
- 2
The book asks your system to debit the stake, with a signed call.
- 3
Your wallet updates the player’s single balance.
- 4
Once the event is over, the book asks your system to credit any winnings.
Every call signed, every credential protected
When the book talks to your wallet, the key question is simple: how does your system know the request really comes from us? The answer lies in three credentials and a few strict rules about how they are kept.
Three credentials, one purpose
With the seamless model you receive a username, a password and a signing key. Together they let your system recognise the book and reject any request that does not come from it.
Signed calls
Every debit or credit request we send to your system carries a signature generated with the key. Your system checks it before touching the balance, so no one can pass themselves off as the book.
Hashed password, shown once
The password is stored only as an irreversible hash and appears on screen a single time, at the moment it is generated. After that, nobody can read it.
Lost it? Generate a new one
A lost password is not recovered, and that is a deliberate choice. You simply generate a new one and enter it in your system in place of the old one.
A transaction ledger no one can rewrite
Trust in a betting system is measured in numbers. That is why every movement of money goes into a ledger where the database accepts new rows but refuses any attempt to edit or delete existing ones. It is not a process rule that depends on good intentions: it is a technical constraint, and it applies to us too.
- No row can be edited or deleted
- Corrections are made with compensating rows
- The original row and the correction both stay visible
- Not even Gamblix can change a row
The result is a complete history: at any moment you can reconstruct how a balance came to be, movement by movement, including the mistakes and how they were corrected.
| Row | Movement | Amount |
|---|---|---|
| #1 | Win credited on ticket | +50.00 |
| #2 | Compensation of row 1 | −50.00 |
| #3 | Corrected win credited | +45.00 |
Safeguards that work quietly
Beyond the ledger, three design choices reduce errors and abuse before they can happen. They need no special configuration: they are part of how the system is built.
Configuration kept apart from money
Settings and financial movements live on separate layers. Whoever changes a limit, a theme or a currency is working on configuration, and none of those actions can touch a balance or a recorded movement.
Every site locked to its domains
The browser refuses to open the book on a domain that is not authorised for that site. The list updates automatically and rests on a baseline safety threshold, so your book cannot be loaded on someone else’s pages.
One-way permissions
Within the network, each agent can narrow the permissions of those below them, but can never widen them. Control flows in one direction only, and no level can override the one above.
Integration and security FAQ
Does the sportsbook run inside my site or on a separate one?
Inside your site. The book loads through an iFrame on the page you choose, on your domain and under your brand, so players are never sent anywhere else.
How does my system verify that debit requests come from you?
Every call the book sends to your wallet is signed with the key we give you along with a username and password. Your system checks the signature before moving the balance and discards anything that fails.
What happens if I lose the seamless wallet password?
It cannot be recovered, because we store it only as an irreversible hash and show it once. You generate a new one and enter it in your system in place of the old one.
Can a movement recorded by mistake be corrected?
Yes, without deleting anything. The original row stays where it is and a compensating row is added: both remain visible, so the history also tells the story of the correction.
What stops someone from using my book on another site?
Every site is locked to its own authorised domains. On a domain that is not on the list, the browser refuses to open the book, and the list updates automatically.
Keep exploring the sportsbook
Back office
Agent network, domains, currencies, accounting, reports and risk: everything you need to run the business.
Read morePlayer experience
Sports offer, betslip, languages and layouts: the sportsbook through the eyes of the people who play.
Read moreLive streaming
Put the match next to the betslip
Read moreLet’s talk integration with your technical team
Tell us which platform you run today and whether you already have a player wallet: we will point you to the right model and the steps to go live in 72 working hours.