What the 10x Wagering Cap Actually Caps

Where the rule sits

The cap is part of social responsibility code provision 5.1.1 of the Licence Conditions and Codes of Practice, the section headed rewards and bonuses. The adopted wording is a short list of things a licensee must not do, and the relevant line is that a licensee must not "apply wagering requirements, which requires a customer to play through bonus funds, over a maximum of 10 times". The Commission confirmed the final text and the 19 January 2026 implementation date in its response to the autumn 2023 consultation.

Two points about the status of that rule are worth being exact about, because they are routinely blurred. First, 5.1.1 is a code provision, not a statute: it is binding on the licensee as a matter of its operating licence, and a breach is a regulatory matter for the Commission, not a criminal offence. Second, it binds the operator, not the player. Nothing in it caps what a player may stake or lose; it caps what an operator may demand of a bonus before the proceeds become withdrawable.

Ten times what

The adopted wording names the base: bonus funds. The play-through requirement is measured against the bonus amount granted, not against the deposit that unlocked it and not against deposit plus bonus combined. That distinction is the whole of the arithmetic. A £50 bonus carrying the maximum permitted requirement means £500 of qualifying turnover. The same £50 bonus on a £50 deposit, if the requirement had been written against deposit plus bonus, would have meant £1,000 — twice the play for the same offer. Under the current provision the second construction is not available to a GB licensee.

Turnover is not the same thing as spend, and the two are often conflated in offer copy. Ten times a £50 bonus is £500 of stakes placed, which the same balance can supply many times over as it rises and falls. It is a volume-of-play condition, not a demand for £500 of fresh money.

What the provision does not do

• It does not cap the number of games excluded from the requirement, or the contribution rate each eligible game carries. A game that contributes a fraction of each stake stretches the real turnover well beyond the headline multiple, which is why the contribution table matters as much as the multiple.
• It does not restrict the provision to new-customer offers. The adopted text applies to incentives offered to customers and potential customers alike, so reload and loyalty offers sit inside the same ceiling.
• It does not set a minimum. Lower requirements, and offers with none at all, remain entirely permissible.
• It does not freeze a time limit, a maximum conversion, or a maximum stake while a requirement is live. Those remain the operator's own terms, bounded by the separate requirement in licence condition 7.1.1 that terms be fair and transparent within the meaning of the Consumer Rights Act 2015.

Why older pages still print 35x

Multiples of 35, 40 and 65 were ordinary in British offer terms before January 2026, and a great deal of affiliate and review copy has never been revisited since. A page quoting one of those figures is not necessarily describing a rogue operator: it is far more likely to be describing terms that were lawful when the page was written and have since been replaced. The same applies to screenshots and to cached terms pages.

The check is cheap. The operator's current promotional terms are the authority for its own offer, and they must be readily accessible under 5.1.1 and transparent under 7.1.1. A multiple above ten in live GB terms is the anomaly, not the norm, and it is the live terms rather than a third-party summary that settle it.

Reading the figure in practice

Three numbers decide how much play an offer asks for, and the headline multiple is only the first: the multiple itself, the base it is applied to, and the contribution percentages for the games that will actually be played. An offer that states all three plainly is doing what the code requires of it. One that states the multiple and buries the rest is the case the transparency requirement in 7.1.1 exists to address.