A progressive jackpot is not merely a large number above a slot. It is a prize that grows from a defined starting value as eligible stakes contribute to a common pool. The player sees a display, but behind it are rules for funding, eligibility, event ordering, award and reset. The British Gambling Commission's definition describes a progressive as an incremental prize rising through contributions from money staked within a game. Its RTS 9 requires the rules to be available before a player commits and the system to operate fairly and securely.
This explainer follows the money and event record from a wager to a payout. It uses Great Britain's published requirements as the regulatory anchor and GLI-19, version 3.0 as a separate technical reference. GLI is a testing laboratory; its standards are not automatically the law in every market. Each operator must identify the locally adopted requirements, licence conditions and game configuration before making a compliance claim.
The prize is a system, not an animation
The Commission's terms distinguish a progressive prize from a fixed paytable prize. A common implementation starts from a seed amount, allocates a defined part of eligible wagering to the prize and awards it when a defined trigger occurs. The prize then resets according to its rules. That description is an illustrative architecture, not a claim that every jackpot uses the same contribution percentage, trigger or balance sheet arrangement.
The player-facing number should be understood as a claim about a particular award under particular rules. The display alone does not tell the player whether all stakes qualify, whether a minimum stake is needed, whether multiple games feed the same pool or whether the shown figure includes money reserved for a future reset. RTS 9A therefore requires an explanation before the gamble. Its guidance calls for the source of funding, seed, any ceiling, eligibility, prize determination and handling of simultaneous apparent wins to be described.
The distinction from a regular slot return matters. A symbol combination can award a fixed prize according to a paytable without any growing pool. Conversely, a progressive's increment may be visible across games that have very different base-game outcomes. Our paytable mathematics guide explains fixed game awards; our RTP explainer explains why a percentage is an expectation over many plays, not a forecast for a particular session.
| System element | Question the rules should answer | Evidence worth checking |
|---|---|---|
| Seed and reset | What amount starts a new jackpot after a win? | Published rules and configured starting value |
| Contribution | Which eligible stakes increase the pool, and by what method? | Wager events reconciled to pool increments |
| Eligibility | Are certain stake sizes, games or modes excluded? | Game help, player display and configuration |
| Ceiling or diversion | What happens when the prize reaches a maximum? | Rules, overflow account and accounting records |
| Trigger and award | How is a win detected and who receives it? | Immutable event sequence, settlement and replay |
| Display | When does each eligible player see the latest value? | Meter updates, latency monitoring and reset notice |
The table is an editorial audit aid based on the cited standards. It is not a universal accounting template. In particular, the party that technically hosts a jackpot need not be the party that contracts with the player or ultimately bears the payout obligation. Contractual and licensing roles vary; our operator-versus-supplier guide explains why the distinction must be checked for each market.
Funding, seed and the ceiling
A seed sets the initial amount advertised after the pool is launched or reset. Contributions then raise the active award under the game rules. The Commission's RTS 9 guidance says the player-facing rules should describe both funding and seed, and also any maximum value. There is no universal regulator-mandated contribution percentage in RTS 9. Two products displaying the same current prize can have different stake requirements, funding rates and jackpot probabilities.
A ceiling creates a second question: where does the money go after the displayed prize stops rising? RTS 9A says the rules should explain later contributions, for example a redirected overflow or reserve pool. The GLI-19 technical standard, section 4.13 discusses capped payoffs and diversion pools. It says extra contributions are credited to an overflow pool where required by the regulator; that conditional phrase is important. It would be inaccurate to describe a particular diversion design as universal law.
An illustrative reconciliation has four parts: amount before the wager, increment attributed to that wager, amount awarded or carried forward, and value after any reset. The player need not see an internal accounting ledger, but the system must be able to explain why the display and recorded outcome are consistent. If the game is retired before the pool is won, RTS 9B guidance says player contributions must be dealt with fairly, giving examples such as waiting for an award, transferring them to a similar pool or returning them with disclosure. Simply removing the meter without an allocation decision is not an adequate explanation.
Linked jackpots make eligibility harder to see
A linked jackpot can collect contributions through more than one game or interface. A remote gaming server, central pool controller and player account system may be operated by different suppliers. The topology is an implementation choice, not something the screen reveals. Our remote gaming server guide describes the game-hosting role without assuming that the host is always the jackpot operator or legal payer.
For the player, the key questions are narrower: does this stake contribute; can this stake win; what is the actual chance relative to the amount contributed; and is the displayed prize current? RTS 9B says a customer contributing to a pool should be eligible to win while playing that game, and the chance should increase in correlation with the amount contributed. If a player is ineligible, the guidance says this should be clear along with that player's theoretical RTP.
The GLI-19 discussion of linked odds adds a technical reference: for a jackpot linked to multiple themes, probability should be proportional to monetary wager unless disclosed otherwise. That is a test-standard formulation, not a substitute for the applicable jurisdiction's rules. A low-stake game that advertises access to the same headline pool as a higher-stake game needs particularly clear help text; “same jackpot” does not by itself mean “same chance”.
What does the live jackpot display actually guarantee?
Under RTS 9A, eligible players should be able to see current values, updated as often as practicable, especially after a win resets the amount. The standard does not impose a blanket UK rule saying every meter must refresh at exactly the same number of seconds. Network latency, client refresh and a display's animated “odometer” effect can make the visible count differ momentarily from the authoritative value.
GLI-19 specifies, for systems assessed against that standard, updating a displayed payoff at least every thirty seconds from an incrementing game event. This is a GLI technical benchmark, not an RTS 9 deadline or a worldwide legal rule. The same section acknowledges communication delays and latency. An audit should therefore ask which timestamp belongs to the wager, which to pool acceptance, which to the client display, and which amount was used when a win triggered.
Following a win, RTS 9B says the winner must be notified immediately and other participants adequately informed of the reset value. A cached old amount can mislead users even if the central pool has already settled correctly. Display monitoring and an incident path belong in the technical design, especially when the same meter is embedded across several operators' games.
Simultaneous wins, settlement and replay
In a linked network, two players may appear to hit the same pool at almost the same time. Display time is not necessarily trigger time. RTS 9A says jackpot rules must explain what happens when multiple customers trigger the prize simultaneously or appear to because of latency. GLI-19 section 4.13.9 describes ordering and recording triggers and, where an exact order cannot be established, full awards to each winner or a disclosed distribution method. The GLI options illustrate the engineering problem; they should not be asserted as the legal resolution of every real dispute.
A credible event trail links player ID, game and round ID, wager, pool contribution, trigger, authoritative pool amount, award and reset. It also records the software and configuration versions in force. That is an editorial description of useful evidence, not a quotation from RTS 9. For a customer dispute, a video of spinning reels may be incomplete: the decisive questions can concern the pool state and eligibility at the event time. Independent tests are meant to verify the mathematical and technical path before release, while live monitoring checks that production keeps behaving as specified.
The Commission's testing strategy names jackpots that fail to increment or trigger according to the rules as a consumer-loss risk. It describes test-house verification of design and trigger functionality against the stated RTP, and separately identifies configuration changes that affect RTP as a risk for internal controls. Our game-testing guide explains why a test certificate cannot stand in for ongoing monitoring of the live build.
RTP includes more than the headline prize
Theoretical return to player (RTP) includes all payouts expected under the relevant game model. Under RTS 9A, the jackpot RTP should be shown consistently with RTS 3C, either as one combined figure for the game and progressive or as base-game and jackpot components. If a player cannot win the progressive, their corresponding theoretical RTP should be clear. A headline prize of £1 million is not an RTP figure, and a large current pool does not, on its own, establish that a particular wager is favourable.
The denominator matters as well: the stake size, eligible games, contributions and probability model affect the published percentage. Published RTP is calculated over the model's long-run outcome distribution, not over the next hundred spins. A game can have a substantial jackpot component and very volatile short-term returns. Our volatility explainer separates outcome spread from theoretical average return. Readers comparing games should check the rule version and whether a listed RTP includes or excludes the jackpot rather than placing two bare percentages side by side.
The control chain an operator should be able to demonstrate
For a launch or major change, an operator should be able to identify the legal operator, the supplier running the pool, the game or games connected to it, the contribution and trigger model, the display source, the party that settles the prize and the rule version approved for the customer. That is a suggested responsibility map, not a fixed allocation under British law. The iGaming value-chain map helps place the pool among game hosting, account management and payments.
The British RTS 9B also calls for strict access and logging controls around live jackpot configuration. Changes to seed, ceiling, eligibility or odds should not disappear into an undocumented dashboard edit. Reconcile stake contributions to pool movement, awards and resets; test failures, reconnects and almost-simultaneous wins; preserve the client-facing rules and display version. A visually impressive meter should be the last thing to trust, not the first: it is the output of the underlying accounting and game logic.
Frequently asked questions
Does every spin add money to the progressive jackpot?
Not necessarily. The contribution and eligibility rules depend on the game. RTS 9 calls for the funding mechanism and ineligibility to be explained. Check stake thresholds and participating game versions before assuming a particular spin fed the advertised pool.
Does a bigger jackpot mean the slot has better RTP?
Not by itself. The meter is a prize amount, not a return percentage. The published RTP should explain whether the jackpot component is combined with or separated from base-game return, and whether the player's stake is eligible for that component.
Who pays when a jackpot is hit across several casinos?
The on-screen host, pool controller, licensed operator and settlement provider may have different roles. A single universal answer would be misleading. The player-facing rules and relevant licence and contractual arrangements determine who owes the award in that product and market.
What if two players seem to win the same jackpot at once?
RTS 9 says the game rules should explain how simultaneous or apparently simultaneous triggers are determined and awarded, including latency cases. The event ordering and recorded pool state matter more than the order in which browser screens animated.
Can a casino switch off a progressive with player contributions still in it?
The British RTS 9B guidance says player contributions in a decommissioned jackpot must be returned fairly according to the circumstances, with priority to contributors. It gives several possible methods, not a single automatic formula. The game rules and communication to affected players should explain the chosen treatment.