Games

Partner-facing rules for Reel Stars, Reel Triple and Reel Streak.

On this page

All three games keep a card that builds up over the player's spins, so the player has a reason to come back. The card belongs to the player at that Operator, game, bet level and currency, and is kept across sessions and devices.

GamegameIdJackpotGridsRTP (return to player) range
Reel Starsreel-starsProgressive (full card)3x5, 4x5, 4x670%–96%
Reel Triplereel-tripleProgressive Major + fixed Mini and Minor bonuses3x5, 4x5, 4x680%–96%
Reel Streakreel-streakNone (fixed prizes)3x570%–96%

The Operator chooses the grid and RTP (the Game Variant): 71 variants in all. Reel Stars and Reel Streak offer 70, 75, 80, 85, 88, 90, 92, 93.5, 94, 95 and 96%; Reel Triple offers 80, 85, 88, 90, 92, 93.5, 94, 95 and 96% (no 70 or 75). Grids are written rows × columns.

Planned maintenance

GET /v1/partner/games and GET /v1/partner/games/{gameId}/levels report maintenance for a game that is in a planned maintenance window, or has one starting within the next 24 hours:

json
"maintenance": { "active": false, "from": "2027-03-01T12:00:00Z", "until": "2027-03-01T14:00:00Z" }
  • active is true while the window runs. from and until are UTC times. The field is absent when there is no window in or within 24 hours.
  • Hide the side game while active is true and until until, and from from if you want a clean cut-over. A play sent during a window is refused with 1506 maintenance (refund it; see 05-bets.md). A window can be ended early, so until can move earlier: read it again rather than caching it.
  • A window may cover the whole site, one Operator or one game; the field shows the window that applies to the Operator you asked about. Retries of accepted bets, look-ups, cancels and the widget keep working during a window.

GET /v1/partner/status gives the same information for all your Operators at once: status is operational or maintenance, with serverTime and a maintenance list of windows (from, to, description).

Reel Stars

  • Each spin may land stars on the bingo card; stars stay on the card.
  • A card lasts 50 spins. When only a few cells remain, a 30-minute timer starts.
  • A full card wins the progressive jackpot: the seed plus all the growth in the pool.
  • A card that runs out of spins or time resets with no payout.

Reel Triple

  • Stars stick to the card over 50 spins.
  • One full row locks a Mini bonus (25× the bet); two rows lock a Minor (35× the bet), each before a spin cut-off. Only the highest locked bonus is paid, when the card ends.
  • A full card wins the Major progressive jackpot instead of the bonus.
  • If the card times out with a bonus locked, the bonus is paid with the player's next bet (carriedBonus).
  • If the bet level is withdrawn from the player's Operator, or the game is retired for that Operator, the player can no longer bet at that level, so the bonus cannot be paid. It stays owed for a notice period (default 90 days, counted from the publication that withdrew the level or retired the game) and is paid in the next bet if the level is offered again. After the period it is written off automatically. The rules text tells players that a bonus at a withdrawn level is forfeited after the notice period.

Reel Streak

  • A 3x5 card over 50 spins with a multiplier ladder: 1×, 1.25×, 1.5×, 2×, 2.5×, 5×.
  • Three spins in a row with a star move the multiplier up; three without move it down.
  • A full card pays 200× the bet × the current multiplier.

What the widget shows

  • The card and its progress, the spins left and any timer.
  • For progressive games, the live jackpot value for the player's level in the player's currency.
  • For Reel Streak, the multiplier ladder.
  • A How to play help screen with the rules in the player's language (see language on the session; the widget supports English, Spanish for Spain and for Latin America, Portuguese for Portugal and for Brazil, French, German, Russian and Simplified Chinese), the prize values at the player's bet and the RTP.
  • Each round's result (immediately, or after your reveal where reveal mode 2 is used).

Bet levels

Each game has a ladder of bet levels (1, 2, 3 and so on). The price of a level is calculated:

price = level × the Operator's base bet for the game × the currency's factor

rounded down to the currency's smallest unit. The base bet is the price of level 1 in a reference currency (for example USD 0.10), and the factor is a fixed whole number for each currency that we set (for example USD 1, EUR 1, ARS 1000). With a base bet of USD 0.10, level 2 costs USD 0.20, EUR 0.20 or ARS 200. Prices never follow the live exchange rate, so they stay round and only change when a new configuration is published. /levels returns exactly the levels the Operator offers for the game, with their prices. The offered levels may have gaps (for example 1, 2, 3, 4, 5, 10 and 15), so use the list as returned and don't assume every number is there:

GET /v1/partner/games/{gameId}/levels?operatorId=op-42&currency=EUR

json
{ "gameId": "reel-triple", "currency": "EUR",
  "maintenance": { "active": false, "from": "2027-03-01T12:00:00Z", "until": "2027-03-01T14:00:00Z" },
  "levels": [ { "level": 1, "price": "0.10" }, { "level": 2, "price": "0.20" }, { "level": 5, "price": "0.50" } ] }

A bet at a level that is not in the list is refused with 1200 validationFailed. A bet in a currency the Operator does not offer, or that does not match the session, is refused with 1202 currencyNotSupported, and /levels for such a currency returns 1202 too. A currency for which we hold no exchange rate into the game's jackpot currency yet is not offered either: it is left out of the currencies of GET /v1/partner/games and of GET /v1/partner/currencies. A level in the list sent at a different price is refused with 1201 priceMismatch.

Each level has its own jackpot pools and its own card, so a player switching level starts or resumes the card for that level. A bet names the player's level in level and carries the price you debited in amount; the two must agree (see 05-bets.md).

Price changes. A player has one card per level, and a price change never ends it. If a price changes after a configuration publication, it applies from the next bet; your player's card continues (see 05-bets.md). A bet still sent at the old price is refused with 1201 priceMismatch, which returns the level's current price. Nothing happens to a player who does not bet.