Partner contentRegTech

RegTech is usually told as a finance story: know-your-customer checks, transaction monitoring, the compliance stack that grew out of 2008. The more interesting version of it right now is a build problem, and the clearest live example did not happen in banking. Over the past year a British regulator wrote what amounts to a specification for a piece of user interface, handed it to every licensed operator in a consumer sector, and gave them eleven months to ship it. Compliance has been converging on engineering across finance, health and gambling for a while now. This is the point at which the convergence produced an acceptance test.

The sector is UK online gambling and the rules took effect on 19 January 2026. For a technology audience the headline number matters less than the mechanism behind it. Compliance teams did not build the thing the regulator asked for. Front-end engineers, CMS owners and promotion-engine developers did, against a deadline they had no part in setting and across fields that lived in three different systems. Product and growth teams in consumer finance, retail and telecoms have a reason to read the exercise closely, because nothing in the reasoning behind it is specific to gambling.

The rule that became a build ticket

Revised social responsibility code provision 5.1.1 caps wagering requirements at ten times the bonus, and limits the playthrough to bonus funds rather than letting it run across the customer’s deposit as well. Welcome offers carrying 35 or 40 times playthrough were routine before the change, and some ran to 50, so the cap compresses a mechanic the industry had leaned on for years.

Two further provisions matter as much as the cap:

  • Paragraph 3b bars operators from putting more than one type of gambling product (betting, casino, bingo and lottery) inside a single incentive, which removes the cross-sell offer that moved a sports customer onto a casino product.
  • Terms attached to an incentive have to be clear, transparent, fair and readily accessible to any customer or potential customer to whom the offer is made.

The Commission originally set the deadline at 19 December 2025, moved it back by a month, and published further implementation guidance in December. Members of the sector’s trade body were still asking for clarification well into the autumn. A regulator does not add a month and a guidance note to a rule the industry is finding straightforward.

Why it landed on the product team

The phrase doing the work here is “readily accessible”. A link to a terms page satisfies a lawyer. It does not satisfy a requirement that a prospective customer can reach the conditions determining what an offer is worth before deciding whether to take it. In practice that has meant lifting five fields out of the terms document and into the promotional component itself: the playthrough multiple, the maximum stake permitted while a bonus is live, which games contribute towards it, the expiry window, and the cap on what can be withdrawn.

Anyone who has worked on a promotional surface knows what that involves. Those fields live in different systems. Some sit in the bonus engine, some in the CMS, some are hard-coded per campaign, and historically none of them were rendered anywhere a marketing team could see. Making them appear beside a claim button, accurately, across web and mobile, for every offer in a rotating promotional calendar, is an integration problem that no amount of policy drafting resolves.

It is also the sort of work the compliance-technology sector has spent years arguing for. The co-founder of the anti-money-laundering platform RelyComply told BusinessCloud in March that “the institutions that win will be those that treat compliance as engineered infrastructure, not regulatory paperwork”. Promotional compliance is a cleaner test of that claim than most, because this rule cannot be satisfied with a policy document. Either the numbers render next to the button or they do not.

The disclosure record is now machine readable

Requiring the conditions to be visible at the point of offer has a second-order effect the drafters may not have intended. It makes them collectable. Once the playthrough multiple and the withdrawal cap have to be rendered inside the promotional unit, they can be read, logged and compared across operators by anyone, on a schedule.

BestOnlineCasino, one of the UK comparison sites, lists the wagering attached to each operator’s welcome offer beside its licence number, average payout percentage and minimum deposit. Before January a table like that was partly guesswork, assembled from terms pages of varying honesty.

This is a familiar pattern to anyone who has watched other transparency mandates land. Requiring a firm to publish a number in a fixed place creates a market in aggregating it, and the aggregator tends to apply more competitive pressure than the regulator’s own enforcement does. Energy tariffs and airline fees both went the same way.

What the cap does to acquisition economics

Wagering requirements were never purely a harm-reduction target. They were the control on how much of a bonus was ever likely to convert into a withdrawal, which is what made a large headline offer affordable in the first place. Cap the multiple at ten and the expected cost of an acquired customer rises, unless the headline value comes down to meet it.

That leaves acquisition teams a narrow set of moves: smaller nominal bonuses, tighter eligibility, more weight on retention than on acquisition, or a move away from bonus-led acquisition altogether. The product-mixing ban closes another route, since an operator can no longer use a cheap free bet to seed a casino habit. The second-order effect is on differentiation. When the mechanic is fixed by rule across every licensee, competition moves to the things that are harder to copy, such as withdrawal speed and the quality of the app.

The change also falls unevenly. Flutter Entertainment, Entain and bet365 between them account for most of the UK online market, and all three run in-house platform teams large enough to absorb a specification change of this kind on a normal release cycle. A mid-sized licensee sitting on a white-label stack from a supplier such as EveryMatrix had to wait for the fields to be exposed to it, then hope the supplier’s roadmap matched the regulator’s. Rules written as interface requirements tend to consolidate a market rather than open it up, which is worth watching in a sector already this concentrated.

Which sector inherits this next

The regulator’s position is that a promotional offer with material conditions hidden behind a link is not a fair offer, and that those conditions belong at the point of decision. That argument transfers without modification to buy-now-pay-later, introductory savings rates, mobile tariffs, subscription pricing and retail finance. None of those sectors has been handed a five-field specification yet. The reasoning that would produce one is already written down.

UK gambling got these rules first because it is the sector where the regulator has both the mandate and the appetite, not because the problem is unique to it. Product and growth teams elsewhere would be well served by looking at what shipped in January. The operators that treated it as an engineering problem were finished on time. The ones that treated it as a legal formality are the ones still shipping fixes.