EGAME
EN

For operators and aggregators · October 2026

Eighteen games,
one click away.

All eighteen are live on our platform, and every one of them opens in your browser right now on demo balance. Nothing to sign up for. See exactly what your lobby would be getting before anyone mentions a contract.

Games live
18
Categories
4slots · instant · table
Languages
2en · zh
Wallet model
1Transfer
RTP range
96.9–99.4percent

The lineup

Four categories.
One integration.

Crash, instant win, table and slots, all on one client and one wallet contract. Every demo below opens the same production build your players would get.

Built in

One client.
Eighteen games.

Paytable and rules inside the game

Every title ships its own rules panel and the full paytable, in the player’s own language. Wheel prints the real probability next to each multiplier, Mines lists all 24 mine settings, and Rocket keeps the crash history from earlier rounds on screen.

Desktop and mobile from one build

The client scales the board to the screen it lands on. There is no separate mobile integration to do, no second set of assets to keep in sync, and no difference in the maths between the two.

Integrate once, add seventeen more

All eighteen share one launch contract, one set of wallet calls and one client. Once the first game is live, adding the rest is a catalog entry rather than another project.

Getting live

One signed launch call.
That’s the whole integration.

You get the endpoint list, the HMAC signing details and a sandbox merchant when you start.

Launch

  • Call POST /v1/game/launch with the member, the gameId and your backUrl, and you get back a finished, encoded URL.
  • Open it in the player’s browser. The token is single-use and lives only for that session.
  • Pass backUrl and the game renders a back-to-lobby button for you.
  • Never cache an assembled launch URL — call launch for every open.

Wallet

  • Transfer — you mint credit with /v1/transfer/in and pull it back with /v1/transfer/out; every game settles against that balance.
  • Balances and transfers are queryable: /v1/member/balance and /v1/transfer/query.
  • Every server-to-server call is HMAC-signed over method, path, merchant, currency, timestamp, nonce and body.
  • Bet history comes back from /v1/order/history — the same rows your reports are built on.

Running it

  • One game backend serves every title. A round is settled server-side, not in the browser.
  • Two languages ship today — en and zh — and lang is a launch parameter.
  • Each game’s RTP on this page is its default certified configuration.
  • Availability follows game.status: switch a game off and it disappears from this list.
All eighteen at a glance
Game Category Mechanic RTP Max win

RTP figures are each game’s default certified configuration. Where a game is certified at more than one tier, the tier is set at integration. Blackjack returns depend on player decisions and are quoted at optimal play.

Getting started

Play them now.
Then let’s talk.

01

Open any demo above. Nothing to install, nothing to sign, and it is the same build your players would get.

02

Ask us for a sandbox merchant code and you can run the whole catalog on demo balance before any contract.

03

When you are ready to build, you get the integration guide, the endpoint reference and a test harness, plus us on the other end of it.