Banks, payments and gaming money, India and beyond ·

Banking India Update

Why Bonus-Buy Cost Rarely Matches the Stated RTP

Bonus-buy RTP rarely matches the advertised figure because the headline describes base-game spins, not the fixed purchase price you actually pay

5 min read

Why Bonus-Buy Cost Rarely Matches the Stated RTP
Why Bonus-Buy Cost Rarely Matches the Stated RTP

The advertised RTP on a bonus-buy slot describes the long-run return of the base game's spin cycle, not the return on the purchase price a player pays to enter free spins or a pick feature at a fixed cost. Across the buy tiers most operators publish, the realised return on the buy commonly sits below the headline figure by a margin that scales with the size of the multiplier attached to the trigger. The gap is structural, not a rounding error, and it widens precisely where the buy price is largest.

The mechanism is straightforward once you separate two quantities that share a marketing vocabulary. A slot's stated RTP, say 96.2%, is computed over the full spin distribution: every paid spin, every scatter trigger, every natural bonus. A bonus buy removes the paid-spin phase and charges a lump sum for the feature alone. The feature has its own payout distribution, and that distribution need not — and usually does not — reproduce the base game's expected value per unit staked. Regulators in several jurisdictions require the buy price to be disclosed as a multiple of the bet (60x, 75x, 100x), but the multiple is a price, not a return.

Where the arithmetic separates

Consider a hypothetical slot with a 96.2% base RTP and a 100x buy. If the feature's expected payout were exactly 96.2x the triggering bet, the buy would be return-neutral against the base game. In practice, published buy features on high-volatility titles cluster their expected payout between roughly 94x and 96x on a 100x price — a realised return of 94–96%, or 20 to 220 basis points below the headline. On a ₹1,000 buy, that is ₹40–₹60 of expected loss per purchase, against ₹38 for a single ₹1,000 spin at the stated RTP. The difference looks small per transaction; compounded over a session of twenty buys it is the difference between a 4% and a 4.6% expected drain.

The variance profile matters more than the mean. Buy features concentrate outcomes: a large share of purchases return less than 20x the bet, a thin tail returns 500x or more. A player evaluating a buy on ten or twenty samples is observing almost entirely the left side of that distribution. This is the same sampling problem that shows up when players assess RTP from short play, and it interacts with how the figure is presented on the page — a subject examined in when players actually read the RTP field, where the label is often consulted after the buy decision rather than before.

The stated figure's denominator

A second source of mismatch is definitional. Some providers quote the buy feature's RTP against the buy price; others quote the game's overall RTP including the buy path blended with base spins. Where a studio publishes a single number for a title that offers both modes, the number is a weighted average whose weights depend on assumed play mix. A player who buys exclusively is not playing the weighted average; they are playing the buy branch, and the branch figure is the one that governs. Operators rarely surface both. The 41% of players who skip the RTP drop below 96%, as documented in the RTP threshold study, are unlikely to interrogate branch-level figures at all.

The wagering overlay

Bonus-buy cost interacts with deposit bonus terms in a way that compounds the gap. Where a buy is funded from bonus balance, the wager contributed by the buy is typically counted at a reduced rate — often 10% or less toward the wagering requirement — because buy features are treated as high-variance, low-turnover play. A ₹1,000 buy might contribute ₹100 to a 35x requirement. The effective cost of clearing the bonus therefore rises sharply for buy-heavy play, and the headline RTP says nothing about it.

This is the same structural problem visible in match-bonus mechanics, where max-bet spins at hour two survive wagering at a rate that depends on stake discipline rather than on the advertised percentage. The lesson transfers: the number in the offer copy describes one parameter of a multi-parameter system.

What the disclosures do and do not cover

Regulators have moved toward requiring buy-price disclosure and, in some markets, a separate RTP for the buy feature. The UK Gambling Commission's remote gambling technical standards require the return to be calculated over the game's full cycle, which for a buy-enabled title means the blended figure unless the operator publishes a branch figure voluntarily. Malta and several Indian-facing operators licensed elsewhere follow similar blended-reporting conventions. India itself does not license online casino products domestically; operators serving Indian players hold licences in Curaçao, Malta or the Isle of Man, and the disclosure standard that applies is the licensor's, not a domestic one. A player in Mumbai reading an RTP figure is reading a number produced under a foreign technical standard, frequently without a branch breakdown.

The practical consequence is that the headline RTP functions as a game-level descriptor, useful for comparing titles, misleading for pricing a specific buy. A 96% title with a 100x buy priced at a 95% branch return is, for a buy-only player, a 95% game. The one-point difference is not trivial at volume: over 500 buys at ₹1,000, it is ₹5,000 in expected loss versus ₹4,000.

An open question on disclosure

The interesting question is not whether buy features underperform their headline RTP — the arithmetic makes that likely wherever the branch and blended figures diverge — but whether branch-level disclosure would change behaviour if it were standard. The evidence on RTP literacy is not encouraging: players who do consult the figure often consult it at the wrong moment, and the mobile presentation of RTP data is itself inconsistent, with labels shifting between portrait and landscape by measurable amounts. If the label moves when the phone rotates, a branch-level disclosure buried three taps deep is unlikely to anchor a purchase decision. The more defensible reform may be to price the buy feature transparently — stating the expected return on the buy price directly on the purchase screen — rather than to rely on players reconstructing it from a game-level percentage. Whether any licensor will mandate that, and whether operators would accept the resulting comparison shopping, remains unsettled. Players should treat the buy price as the stake and the branch return as the relevant RTP, and set session limits on buy count rather than on spin count, because the two are not interchangeable.