Skip to main content
Your casino has one return to player (RTP), which you choose on the Games page: 99% (the default), 98%, 97% or 96%. That is a house edge of 1%, 2%, 3% or 4%.

​
Which games follow it

​
How payouts change

  • Formula games. Dice, Limbo, Crash, Mines, Pump and HiLo compute their multipliers with 10000 − edge, in basis points, where the 99% games use 9900. Over 50.00, Dice pays 1.98× at 99%, 1.96× at 98%, 1.94× at 97% and 1.92× at 96%.
  • Wheel. Every paying segment pays a little less, by the same rule for every layout, so each of the 15 layouts returns exactly your figure.
  • Plinko, Keno and Diamonds. Each 99% table is scaled to your figure and rounded down to the hundredth, then the entries furthest below their scaled value are raised one hundredth at a time while the table stays at or below your figure. Every derived table returns at most your figure and within 0.12 points of it, and no payout is higher at a lower return.
  • At 99% every payout is the same as before the options existed.
Multipliers are paid in hundredths, rounded down, so some settings return a little less than your headline figure: some Dice targets, Mines and Pump cash outs, and Crash’s small cash outs. The engine also rounds every payout down to the currency’s minor unit.

​
What players see

The return is signed into your catalog and into the manifest that every bet names. Players check it in the Odds tab of the Provably fair dialog, which computes the game’s return and the chance of every payout in the browser from your signed table, at the settings on screen. The checks under it confirm that the table matches the open engine code, that your game server signed it, and that every casino on the same version at your return pays the same table. Each game returns this at each option. The Games page also lists each game’s return under What each game returns at <figure>. Where the player decides how a round plays, the return is a range across the ways to play.

​
Changing it

A change applies to new bets. Bets accepted before it settle and verify at the return they were placed under. A bet that a player’s browser had already signed under your previous table is refused once with authorization_binding, and the player’s next bet is signed under the new one.