Single Customer View: The Cross-Operator Lens on Every British Punter

The Punter Who Was Three People to Three Operators

A friend of mine ran three betting accounts for years – one at a major chain, one at a smaller specialist, one at the Exchange – and treated them as three separate financial relationships. Each operator saw a customer with a specific deposit history, a specific betting pattern, a specific risk profile. None of the three operators saw what the other two saw, and none of them could tell that the punter’s aggregate annual deposit across the three accounts was several times the deposit at any single operator. That state of operational invisibility is what the Single Customer View – SCV – is designed to end. The Gambling Commission has been piloting SCV through 2023 and 2024 as the regulatory answer to the cross-operator data fragmentation that allowed exactly this kind of aggregate-invisible behaviour.

SCV is one of those pieces of regulatory infrastructure that is technical enough to be dull, consequential enough to matter, and controversial enough to deserve more attention than it gets in the standard punting-press coverage. This article walks the SCV pilot history, what data is shared between operators and the regulator, what the punter experience looks like in practice, and the industry-side concerns that have shaped the rollout. The objective is to make SCV legible to the regular UK punter so that the framework is understood rather than feared, and to set out what the rollout means for the way British betting accounts are managed in the post-2025 environment.

The Pilot, the Timeline and the Affordability Context

SCV emerged from the broader gambling reform debate of the early 2020s as a proposed technical mechanism to address the cross-operator invisibility problem. The 2023 White Paper on gambling identified the cross-operator data gap as a structural weakness in the harm-prevention framework and committed the Gambling Commission to piloting a cross-operator data-sharing capability. The Commission’s pilot began in 2023 with a small group of major operators and a defined population of customers, and expanded through 2024 to a wider population. The pilot ran in parallel with the rollout of the affordability checks framework that came into formal effect in late 2024, and the two frameworks are operationally connected.

The affordability checks framework is the operational context for SCV. Affordability checks apply at defined deposit thresholds – the headline threshold is £150 per rolling 30-day period – and trigger a financial risk assessment that the operator must complete before accepting further deposits from the customer. The 2025 reporting figures put the share of UK punters who have passed through the affordability checks framework at 23.7% of the active account population, meaning that nearly one in four UK punters has experienced the formal affordability process in some form. SCV is the cross-operator visibility layer that allows the Commission and the operators to see aggregate deposit and betting patterns across accounts rather than seeing only the activity within a single operator’s books.

The pilot has been deliberately gradual. The Commission’s stated intent has been to test the technical infrastructure, refine the data-sharing protocols, and validate the harm-prevention outcomes before committing to a full mandatory rollout. The pilot’s progress has been reported through the Commission’s regular gambling sector reports, and the trajectory through 2024 and 2025 has been towards a wider operator population and a more comprehensive data set. The Commission has not yet announced a formal mandatory go-live date for SCV, and the pilot continues to expand through 2026.

What Data Is Shared Between Operators

The data shared through SCV is a defined, structured set rather than a comprehensive copy of every operator’s customer records. The pilot framework identifies a customer using a combination of personal identifiers – typically name, date of birth, and a hashed national insurance number or equivalent – and uses the matching to construct a cross-operator picture of the customer’s activity. The shared data fields include aggregate deposit volume across operators within defined time windows, aggregate betting volume, indicators of self-exclusion or self-imposed limits at any operator, and indicators of operator-side risk flags triggered by the customer’s activity. The fields are deliberately narrow to manage the privacy and data-protection considerations and to focus on the harm-prevention use cases that the framework is designed to address.

What SCV does not share is more revealing than what it does share. The framework does not share individual bet selections, win/loss outcomes on specific bets, or any data that would compromise the customer’s commercial relationship with their operator of choice. It does not share marketing data, promotional response data, or any information that would allow one operator to compete with another on customer-specific terms. The framework’s design is structured to limit the data exposure to the harm-prevention use cases – aggregate volume, exposure indicators, and risk flags – and to keep the wider commercial data set within the boundaries of each operator’s own customer relationship.

The data flows are mediated through an independent third-party processor rather than passed bilaterally between operators. The processor receives the operator-side data on a defined schedule, constructs the cross-operator aggregate view, and provides the operators and the Commission with the aggregate signals rather than the raw underlying data. The mediated structure is the principal data-protection safeguard within the framework, and it is the architectural feature that the Commission has emphasised in its communications about the pilot.

How SCV Affects the Punter Experience

The punter who does not engage in high-volume cross-operator betting will mostly not notice SCV. The framework operates in the background and the operator-facing signals are typically only triggered when the cross-operator aggregate breaches a defined threshold – the £150 monthly deposit threshold that triggers the formal affordability check is the most consequential one, but other thresholds apply to higher-volume customers and to specific patterns of behaviour that the framework flags as elevated risk. The median UK punter, with one or two betting accounts and a modest monthly volume, will pass through SCV without any visible operator-side intervention.

The punter who does engage in higher-volume cross-operator betting will experience SCV in more direct ways. The most common scenario is that a customer who has been operating below the £150 threshold at each of two or three operators individually will be flagged at the SCV level if the aggregate cross-operator deposit volume exceeds the threshold, and one or more of the operators will trigger an affordability check. The customer who has been operating at the £150 threshold at one operator and at a similar volume at another will experience the affordability check at both operators sequentially, with the second operator able to see the first operator’s check status through the SCV framework. The aggregate visibility is the principal operational difference from the pre-SCV environment.

The second-order effects on the punter are more subtle. Customers who have self-excluded at one operator will have that self-exclusion visible to other operators through the SCV framework, which extends the practical reach of a single-operator self-exclusion. Customers who have been restricted by one operator for risk-related reasons will not (by design) have the restriction visible to other operators, because the framework excludes commercial restrictions from the shared data set – but customers who have triggered harm-related flags at one operator will have those flags visible at others. The boundary between commercial restrictions and harm-related flags is the area where the framework’s design has been most carefully worked through, and the boundary is the principal source of the industry-side debate about how SCV should be implemented in the long run.

Industry Concerns and the Open Questions

The industry-side concerns about SCV cluster around four themes. First, the data protection question – the SCV framework involves a meaningful flow of personal data between operators and through a third-party processor, and the operators have flagged the importance of the framework’s data-protection design being robust against breach risk and against future expansion of the shared data set. The Commission has worked through these questions with the Information Commissioner’s Office and the data-protection design has been published as part of the pilot framework, but the underlying concern about future data-set expansion remains a structural one for the industry.

Second, the customer-relationship question. The operators have argued that SCV interferes with the operator-customer relationship in ways that are not yet fully understood, particularly for customers who maintain multiple accounts deliberately to manage their own betting behaviour. A customer who spreads activity across three operators to keep each individual account below the affordability threshold is now visible at the aggregate level, and the operator-side response to that aggregate visibility is shaping the customer experience in ways that the customer did not necessarily choose.

Third, the leakage question. The combination of SCV and the affordability checks framework has been identified by the industry as a contributor to the offshore migration of UK punters – the 4.9% of Racing Post survey respondents who acknowledged using unlicensed operators is up from 3.6% two years earlier, and the affordability framework is the principal cited reason. SCV reinforces the affordability framework’s reach, which in turn reinforces the offshore migration pressure.

Fourth, the operational question. SCV imposes a meaningful operational burden on operators in terms of data feeds, response protocols, and customer communication. The major operators have absorbed the burden but the smaller operators have flagged the proportionality of the framework. The Commission’s response has been to phase the rollout to manage the implementation cost, and the ultimate scope of mandatory SCV remains a question that the regulator and the industry are still working through. The wider regulatory architecture – including the financial risk assessment framework that sits alongside SCV – is set out in how the frictionless financial risk assessment works in practice.