One integration. Every studio. Every bet accounted for.
iGRoute is a casino game aggregation platform. Operators get one game catalogue and one launch API for every studio they offer, and studios reach every operator through a single connection. In between, the platform routes each bet and win to the operator's wallet exactly once and keeps a complete audit trail. It never holds player funds and never runs games.
How a bet travels through iGRoute.
Every bet, win and rollback follows the same five steps, whichever studio it comes from. Studio connectors only translate formats. The transaction rules are written once and apply to every game.
- The studio sends the betIn its own API format.
- Player and brand identifiedThe platform matches the game session to the operator, the casino brand and the player.
- ValidatedSession, currency and the studio, operator and brand settings are checked. Game and market rules were applied at launch.
- Logged, then sentThe transaction is recorded before the operator's wallet is called.
- Confirmed onceThe wallet's response goes back to the studio. If the studio resends the same transaction, it is recognised and nothing is charged twice.
Integration on your terms.
We integrate to your existing API, so your developers don't have to build to ours. If you'd rather work to one standard, our APIs are published and versioned.
Operators
- We integrate to your walletOur team builds and maintains the connection to your existing wallet API. On your side: one game catalogue and one launch call for every studio you switch on.
- Or use our Wallet APIImplement our published, versioned Wallet API once. Every studio you add after that is a configuration change on our side, not a project on yours.
- Multi-brand readyRun several casino brands through one integration. Each game session remembers its brand, so funds always move in the right brand's wallet.
Game studios
- We integrate to your game serverWe work from your API documentation and test game launch and transactions with you. No changes to your server.
- Or use our Provider APIImplement our published, versioned Provider API and validate it with our self-test tool before go-live. Every operator you add after that is a configuration change.
- One connection, every operatorOperators switch your games on in the platform. There is no per-casino integration to build or maintain.
Transaction integrity, built in.
Studios retry, wallets time out and networks drop requests. iGRoute is designed so none of that costs anyone money.
No double charges
Each transaction ID moves money once, however many times a studio sends it. A duplicate gets the current balance back and changes nothing. Retries are recognised for 90 days.
Timeouts resolved, not guessed
If a wallet doesn't respond in time, the transaction stays on record and the platform checks back with the wallet later. It settles on the wallet's answer.
Complete audit trail
Every transaction is logged before the wallet is called, in an append-only ledger. Nothing is edited or deleted; corrections are added as new, visible entries.
Exact amounts
Amounts are processed as exact decimals and never rounded; anything a currency can't represent is rejected. ISO currencies, Bitcoin and operator-defined coins are supported, and bets are always in the player's account currency.
Open rounds closed automatically
The platform decides when a round ends. If a round's final result never arrives, it is closed for bookkeeping after an idle period, and the team is alerted if a stake was taken without a result.
Reconciles to zero
Every bet, win and refund can be matched one-to-one against your wallet records, per brand. The target difference is zero.
Game availability, managed for you.
Availability is checked before a game launches. Tell us what needs to change and our platform team applies it: no release, no downtime, no work on your side.
- Studio, operator and brand switchesTurn off a whole studio, one studio for a single operator, or a single brand. New game launches stop within about a minute, and switching back on is just as fast.
- Games in progress are honouredSwitching off only stops new play. Wins, refunds and rollbacks already in progress are always paid.
- Release dates and marketsSet a go-live date, an end date and the countries each game may be offered in. Outside those, the game is hidden and can't be launched.
- Nothing goes live by accidentIn production, new studio connections start switched off. Going live is always a deliberate step.
Thousandsof wallet transactions per second, measured on a single deployment.
Capacity scales per operator: each operator has its own stable endpoint and can be moved to dedicated capacity without changing any URLs.
- Operator isolationEach operator has its own limits and circuit breaker. If one operator's wallet slows down or stops, response times for every other operator stay normal.
- A resilient lobbyThe game catalogue responds within two seconds even when a studio is down. That studio is flagged as unavailable and everything else loads as normal.
- Full observabilityLogs, metrics and traces are tagged by operator and brand, and alerts on the transaction flow go to an on-call engineer, not just a dashboard.
- Secure by defaultPer-operator API keys or signed requests. Each key only reaches its own operator's data, keys are never written to logs, and demo sessions can never move money.
Everything your lobby needs, through one connection.
Unified game catalogue
Every studio's games in one call, pre-filtered for each operator, brand and market.
Real money and demo
Launch real-money or demo play through the same call. Demo sessions pass the same checks and never touch a wallet.
Free spins campaigns
Grant free spins to players in advance. The platform delivers them to the studio and tracks exactly how many have been used.
Jackpots
Studio jackpot wins are paid to the wallet as a separate credit, exactly once, and a live jackpot feed keeps lobby tickers up to date.
Round replay
Open the studio's own replay of any finished round for support and player history, limited to the operator's own rounds.
Clear error codes
Every rejection comes with a stable reason code and says whether a retry can succeed.
The platform at a glance.
The short version, for your evaluation checklist.
- Seamless wallet integration: we connect to your wallet, or you implement our Wallet API
- Published, versioned Wallet and Provider APIs
- One game catalogue and one launch API for every studio
- Multiple casino brands per operator
- Exactly-once transactions; retries recognised for 90 days
- Append-only transaction ledger, reconcilable per brand
- Exact decimal amounts: ISO currencies, Bitcoin, operator-defined coins
- Per-operator isolation, limits and circuit breakers
- Thousands of wallet transactions per second per deployment
- Studio, operator, brand, release-date and country controls
- Free spins campaigns, jackpots, demo mode and round replay
- Per-operator API keys or signed requests (RFC 9421)
See what it costs for your volume.
Leave your email and we send you a private link to our pricing calculator.