RG

RG platform · five slots · live now

Five slots,
one click away.

Five RG slots on one client and one wallet: cluster pays in Swaggy Bunny, a levelled free game in Curupira, eight-of-a-kind anywhere in Kiss of Fortune, 243 ways in Dragon Trio and an eleven-hatch jackpot in Prosperity Goat. Every demo below opens the same production build your players would get — on demo balance, with nothing to sign up for.

Games live
5
Categories
1slots
Languages
2en · zh
Wallet model
1Transfer
RTP range
96.9–97.6percent

The lineup

One category.
One integration.

Five different mechanics, one client and one wallet contract: cluster pays, ten fixed lines with an animal cage, eight-of-a-kind anywhere, 243 ways, and eleven hatches hiding a 5,000× jackpot.

Built in

One client.
Five games.

Paytable and rules inside the game

Each title ships its own rules panel and the full paytable, in the player’s own language. Swaggy Bunny lists its energy-cell effects, Curupira the cage multipliers, Kiss of Fortune the two free-game modes, Dragon Trio the three storms, and Prosperity Goat the eleven hatches and their prizes.

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 more

All five 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.
  • Each game’s RTP on this page is its default certified configuration.
  • Two languages ship today — en and zh — and lang is a launch parameter.
  • Availability follows game.status: switch a game off and it disappears from this list.
All five 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.