GOV.UK One Login Sandbox Opens as ID Shuts [2026]

Whitehall closed the front door on its national digital identity programme this year, but on October 19, 2026 it left a side door wide open for software developers. The Government Digital Service (GDS) opened a sandbox environment that lets certified private-sector verification providers plug their code directly into GOV.UK Wallet and test credential-checking journeys against government-issued digital documents. The announcement landed one day before Susannah Storey, permanent secretary at the Department for Digital, Culture, Media and Sport, told the Public Accounts Committee in plain terms: “The national digital identity programme is closed.”

For a story that reads, on its surface, like a policy retreat, the practical effect for engineers is the opposite. The flagship national digital ID scheme is dead. The API surface, the credential infrastructure, and the developer onboarding pipeline built to support it are not only alive, they just got their first outside integrators. That split between the political announcement and the technical reality is exactly what The Register captured when it described the government shutting the front door on digital ID while leaving the back open, and it is consistent with the account Computer Weekly gave of the Public Accounts Committee hearing itself.

Google · Preferred Sources

Don't miss new tech stories on Google

Add TrendinTech once in the Google app and our stories appear in your news suggestions.

Add Now

What actually closed, and what did not

Storey’s testimony at the Public Accounts Committee hearing on October 20, 2026 was the clearest statement yet on the fate of the national digital ID plan first floated in September 2025. The programme, which would have given every UK resident a phone-based national identity credential, is finished. Storey also told the committee that the government has not finalised its future approach to digital ID, meaning there is no replacement scheme on the table, only a set of components that survived the cancellation.

The component that survived is GOV.UK One Login, the single sign-in and identity-verification layer GDS has been building for several years. One Login remains active as part of GDS’s ongoing work, and it has not been scaled back. According to figures shared with the committee, One Login generated 752 million pounds in benefits between April 2022 and August 2026, a figure that covers reduced duplication, fraud prevention and efficiency gains across government services that use it. As of the hearing, 245 services had joined One Login, with HM Revenue and Customs in the process of being onboarded, a significant addition given the scale of HMRC’s user base.

Christine Bellamy, interim director general at the Government Digital Service, framed the surviving infrastructure in forward-looking terms. She described One Login as the foundation for wider digital-ID work within government, language that matters because it tells software vendors and civic-tech developers that the underlying plumbing is not going anywhere even though the national-ID branding is gone. If anything, Bellamy’s comments suggest GDS intends to keep building on One Login rather than start over with a new architecture whenever a future digital-identity strategy does get finalised.

The sandbox: what developers actually get

The part of this story that belongs squarely in a developer’s inbox is the sandbox. The government has opened a testing environment for private-sector organisations that are certified against its trust framework, allowing them to integrate with GDS’s underlying technology. In practice, that means a certified verification provider can stand up test credentials, including a test digital driving licence, and run them through the same verification flow a pub, a bank, or an online retailer would eventually use to check a customer’s age or identity.

This is a meaningfully different posture from most government identity systems, which tend to treat their APIs as internal plumbing rather than a public integration surface. GDS is explicitly inviting outside engineering teams in, provided they clear a certification bar first. That certification requirement, administered through the UK’s digital identity and attributes trust framework, is the gate: a developer cannot simply grab an API key and start building. They have to register, get certified as a Digital Verification Service provider, and only then can they request sandbox access.

Once inside, providers are working with synthetic data in an environment kept separate from live user records, which lowers the stakes for experimentation but also means the sandbox cannot be used to validate production-grade performance or load characteristics. It is a correctness and integration testing ground, not a staging environment for a live launch. That is a sensible precaution for a government identity system, but it also means engineering teams need a second-phase plan for production certification once their sandbox integration passes internal review.

Why Whitehall is doing this now

The timing is not an accident. Killing the national digital ID scheme removed a politically charged deliverable, but it did not remove the underlying problem the scheme was meant to solve: too many UK businesses and public bodies still rely on paper documents, manual checks, or fragmented third-party verification services to confirm who someone is. Rather than mandate a single national credential, the government is now working with the private sector on a national strategy for credentials, using the sandbox as the mechanism to find out, with real engineering teams, which integration patterns actually work before committing to anything at scale.

That approach has an obvious advantage for a government that just watched a flagship programme collapse under its own political weight: it distributes both the cost and the blame. If a credential-verification flow fails in testing, it fails inside a sandbox that a private company volunteered to join, not inside a headline national rollout. If an integration succeeds, GDS can point to it as evidence that the architecture works, without ever having forced anyone to adopt it.

For UK software vendors in the identity-verification space, from fintech onboarding tools to age-verification middleware, this is a rare direct line to the infrastructure government services will eventually be built on. It mirrors a pattern seen elsewhere in UK tech regulation this year, where the Competition and Markets Authority ordered Apple to open its iPhone NFC API to third-party developers by November 17, forcing a previously closed technical surface into something outside engineering teams can build against. Both cases involve a regulator or government department deciding that locking an API behind a single gatekeeper, whether that gatekeeper is a phone manufacturer or a national identity scheme, slows down the market more than it protects it.

One Login’s track record so far

One Login’s numbers are worth sitting with, because they explain why GDS fought to keep it even as the national ID scheme around it was scrapped. A reported 752 million pounds in benefits across a little more than four years is a substantial return for a piece of shared sign-in infrastructure, especially one that government auditors have scrutinised closely. Two hundred and forty-five services onboarded is a wide enough footprint that ripping it out and starting over would have meant re-plumbing a meaningful share of citizen-facing government digital services, from tax to benefits to licensing.

Bringing HMRC onto One Login is the clearest signal of where GDS wants this infrastructure to go next. HMRC’s services touch nearly every working adult in the country, and folding tax identity verification into the same sign-in layer used across other government services is the kind of consolidation that reduces both user friction and the attack surface government has to defend. It also raises the stakes: a security failure in One Login after HMRC onboarding would be a far bigger incident than one affecting a smaller department.

Metric	Figure	Period or date
One Login reported benefits	752 million pounds	April 2022 to August 2026
Services onboarded to One Login	245 services	As of the October 20, 2026 PAC hearing
Department currently onboarding	HM Revenue and Customs	In progress as of October 2026
National digital ID scheme status	Closed	Confirmed October 20, 2026
Wallet sandbox opened to certified providers	Open for applications	October 19, 2026
Legal obligation to hold a digital ID	None	Per government consultation

That security scrutiny has not been absent from the conversation. During a 2025 House of Lords debate on digital ID, Lord Vallance of Balham raised concerns directly, saying: “The greatest concern is the Government’s insistence on building this mandatory system on GOV.UK’s One Login, a platform with security failures that have been repeatedly and publicly criticised, including in my own correspondence and meetings with government.” A government minister responded in the same debate that the underlying issues “date from 2023 and have been resolved,” adding that the National Cyber Security Centre was “working hand in hand to get the OneLogin system to the place where it needs to be.” Those remarks predate the October 2026 cancellation of the national scheme, but they are directly relevant to how much scrutiny the surviving infrastructure, including the new sandbox, is likely to face going forward.

No legal obligation, and what that means for adoption

A government consultation tied to this work states plainly that there will be no legal obligation to have or present a digital ID. That single sentence reframes everything else in this story. Without a legal mandate, adoption of whatever credential infrastructure emerges from the sandbox depends entirely on whether private businesses and citizens find it useful enough to opt in voluntarily.

That is a very different adoption curve from a mandatory national ID, and it puts real pressure on the developer experience. If a pub, a bank, or an online retailer is going to integrate a government-backed credential check instead of their existing manual or third-party process, the integration has to be genuinely easier, cheaper, or more reliable than the alternative. A clumsy API, unclear certification requirements, or a sandbox that does not reflect production behaviour will quietly kill adoption long before any policy debate does. This is the quiet, unglamorous risk in this story: GDS does not just need the sandbox to exist, it needs the sandbox to produce integrations good enough that private companies choose them without being told to. The government’s own consultation document on public services and digital identity is where that no-obligation language appears in writing.

How this compares to other government identity developer programmes

The UK is not the first government to wrestle with how open to make its identity infrastructure to outside developers. The approaches taken by other large digital-identity programmes differ sharply in how much technical access they grant and how the access is governed, which gives useful context for judging how ambitious, or cautious, the GOV.UK Wallet sandbox really is.

Programme	Core access model	Mandatory for citizens	Developer gating
UK GOV.UK One Login / Wallet sandbox	Certified Digital Verification Service providers test against sandbox; national ID scheme itself closed	No legal obligation, per government consultation	Trust framework certification required before sandbox access
EU Digital Identity Wallet	Standards-based architecture with an open-source reference implementation and defined protocols	Member states must offer wallets; citizen adoption voluntary	Open specification model, implementation left to member states and relying parties
Singapore Singpass	Formal developer portal with documentation and a staging environment ahead of production approval	Widely used for public and private services, not strictly mandatory	Developer portal registration with a defined approval process
Apple iPhone NFC (UK CMA order)	Third-party developer access to NFC hardware API, opened under regulatory order	Not applicable, device-level API access	Regulatory deadline of November 17, 2026 forces access rather than voluntary certification

The comparison underlines an important point about the UK’s approach: it is gated by certification rather than open by default. Where the EU’s wallet framework leans on published protocols and reference code that any relying party can inspect, and Singapore’s Singpass gives developers a self-service staging environment, GOV.UK Wallet access runs through a certification process administered under the trust framework before a developer ever sees the sandbox. That is a slower on-ramp, but it is also a more controlled one, which may matter more to a government department still recovering from the political fallout of a cancelled national ID scheme.

Historical context: a programme with a troubled past

The national digital ID proposal that just closed was announced in September 2025 as a phone-based national identity credential, with a mandatory element tied to right-to-work checks. That mandatory right-to-work component was already dropped earlier in 2026, well before the broader scheme’s cancellation, a sign that the political resistance to compulsory digital identity had been building for months rather than arriving suddenly in October.

GOV.UK One Login itself has a longer and more technical history than the national ID scheme it eventually got tied to. It predates the September 2025 proposal by years, having been built quietly as shared sign-in infrastructure for government services well before any national-ID branding was attached to it. That history matters for understanding why One Login survived the cancellation intact: it was never purpose-built for the national ID scheme, it was adopted by it. Removing the scheme meant removing a political label, not tearing out the plumbing underneath.

The same pattern shows up in how the UK has handled consumer-facing security upgrades across its own digital estate this year. The site’s own guide on setting up passkeys and FIDO2 security keys covers exactly the kind of passwordless authentication GDS has leaned on for One Login sign-in, highlighting that the government’s identity infrastructure has been tracking, not lagging, broader industry security trends even as the political debate over national ID played out separately.

Market impact: who actually benefits

For UK identity-verification vendors, age-verification middleware providers, and fintech onboarding platforms, the sandbox is a genuine commercial opening. A company that gets its integration certified and working smoothly against GOV.UK Wallet has a credible claim to customers that its verification flow is compatible with whatever government-backed credential strategy eventually emerges. That is valuable positioning in a market where financial institutions, in particular, have spent years building fragmented, higher-friction identity checks because no common government-backed layer existed to build against.

It also changes the competitive calculus for larger software vendors already embedded in UK government contracts. A certified integration with the sandbox is not itself a procurement win, but it is the kind of technical credential that makes a vendor’s bid more credible the next time a public-sector identity-verification contract comes up for tender. Given how much scrutiny GDS contracts face, as reflected in ongoing committee oversight of programmes like this one, vendors with early, proven sandbox integrations have a real head start.

There is a flip side. Smaller developers and startups without the compliance resources to clear trust-framework certification are effectively locked out of this opportunity for now. The certification requirement, while sensible for an identity system handling sensitive government-issued credentials, raises the floor for who can participate, which concentrates the early advantage among established verification vendors rather than opening the field to a broader wave of civic-tech experimentation.

The cybersecurity angle Whitehall cannot ignore

Any time a government opens new integration points into identity infrastructure, security researchers pay close attention, and this sandbox will be no exception. The criticism raised in the House of Lords about One Login’s historical security failures is not ancient history to the people who will be probing this new integration surface. Even with synthetic data and a closed, registered-provider-only sandbox, every new API endpoint, every new certification workflow, and every new credential-issuance path is a fresh target for security research, both the legitimate kind and the adversarial kind.

That risk is not unique to the UK. Government-adjacent identity and records systems have had a rough run in 2026 more broadly: the breach disclosed around the UK Legal Aid Agency, which exposed 250,000 records dating back to 1978, is a reminder of how much legacy sensitive data UK public bodies are still sitting on, and how costly a breach of identity-adjacent infrastructure can be once it happens. GDS will need to treat the sandbox’s certification and monitoring processes as seriously as it treats the production system itself, because a breach originating in a test environment carries nearly as much reputational cost as one in production, even if the underlying data is synthetic.

What this means for developer tooling and government APIs broadly

Step back from the specifics of digital ID, and this story fits a broader pattern reshaping how governments and large platforms expose technical infrastructure to third-party developers. Governments that used to build closed, internal-only systems are increasingly opting for certified-partner sandboxes as a middle ground between a fully open API and a fully closed one. It is the same instinct behind the UK’s move to require NFC access on iPhones, and it echoes how commercial developer platforms have handled contentious integrations, from AI coding agents negotiating access to proprietary codebases to cloud providers gating infrastructure APIs behind verified-account tiers.

Developer tooling vendors have been racing to make these kinds of certified integrations easier to build and audit, a trend visible well beyond government identity work. The same pressure that pushed Microsoft to add host policies and agent rules in VS Code 1.142’s sandbox and agent governance update is the same pressure GDS is responding to here: when you give outside code access to sensitive infrastructure, you need both a technical sandbox and a policy layer around who gets in and what they can touch. The GOV.UK Wallet sandbox is, in effect, Whitehall’s version of that same governance problem, just applied to citizens’ identity documents instead of a developer’s local codebase.

What happens if a rival financial outage repeats

One Login’s expanding footprint across government services raises a question that UK consumers have already lived through this year in the financial sector: what happens when shared sign-in infrastructure goes down. The widespread disruption at Revolut and Lloyds Bank, which drew more than 1,500 outage reports across the UK, showed how quickly a shared authentication or banking layer failure can cascade into a visible, headline-grabbing incident. One Login now underpins 245 government services and is in the process of adding HMRC, which means an outage in One Login itself would ripple across a comparable, if not larger, share of citizen-facing digital infrastructure. GDS has not published specific resilience figures for One Login’s uptime, but the scale of its current footprint makes this a legitimate line of scrutiny for the Public Accounts Committee going forward.

Predictions: where this goes from here

Several things are likely to play out over the coming months as the sandbox matures and the government continues working toward a credentials strategy.

Expect the number of certified Digital Verification Service providers testing in the sandbox to grow steadily through early 2027, concentrated among established identity and age-verification vendors rather than new startups, given the certification bar.
HMRC’s onboarding to One Login will likely become the next major oversight story, since folding tax identity into shared sign-in infrastructure touches a larger and more sensitive user base than any department onboarded so far.
Parliamentary scrutiny of One Login’s security posture will intensify rather than fade, particularly if any sandbox-related vulnerability disclosure surfaces, given the concerns already raised in the House of Lords.
The government’s promised national strategy for credentials, developed jointly with the private sector, is unlikely to arrive as a single unified announcement; expect it to emerge piecemeal, through additional sandbox expansions and incremental trust-framework updates rather than a new flagship scheme.
Other UK regulators and departments will likely point to this certified-sandbox model as a template for opening other sensitive government technical infrastructure, following the same logic the CMA used in ordering NFC access on iPhones.

The bottom line for developers and vendors

The headline event here is political: a national digital ID scheme that generated real controversy, including direct criticism in the House of Lords over One Login’s security history, has been shut down. But the technical story underneath it is one of continuity and expansion, not closure. GOV.UK One Login keeps growing, HMRC is joining it, and a certified sandbox now gives outside developers a real, if gated, path into the credential infrastructure the government intends to keep building regardless of what the eventual national credentials strategy looks like.

For software teams working in identity verification, fintech onboarding, or age-verification compliance, the practical takeaway is straightforward: the opportunity to integrate with government-backed digital credentials in the UK did not disappear with the national ID scheme’s cancellation. It simply moved from a mandatory, politically fraught rollout to a voluntary, certification-gated sandbox, and getting in early on that sandbox is likely to matter more to long-term UK public-sector contracts than it currently appears.

Frequently asked questions

Has the UK’s national digital ID scheme been cancelled?
Yes. Susannah Storey, permanent secretary at the Department for Digital, Culture, Media and Sport, told the Public Accounts Committee on October 20, 2026 that the national digital identity programme is closed. The government has not finalised a future approach to digital ID.

Is GOV.UK One Login still active?
Yes. One Login remains active as part of the Government Digital Service’s ongoing work and has not been scaled back. It has generated 752 million pounds in benefits between April 2022 and August 2026, and 245 services have joined it, with HMRC currently being onboarded.

What is the GOV.UK Wallet sandbox, and who can use it?
It is a testing environment the government opened for private-sector organisations that are certified against its digital identity trust framework, allowing them to integrate with GDS’s underlying identity technology. Access is gated behind trust framework certification, not open to any developer who requests it.

Will UK residents be legally required to have a digital ID?
No. A government consultation on the topic states there will be no legal obligation to have or present a digital ID.

Who is leading the government’s digital identity work now that the national scheme has closed?
Christine Bellamy, interim director general at the Government Digital Service, has described One Login as the foundation for wider digital-ID work within government. The government says it is working with the private sector on a national strategy for credentials following the scheme’s closure.

How does this compare to the EU’s approach to digital identity?
The EU Digital Identity Wallet relies on a published technical architecture and an open-source reference implementation that relying parties can build against directly. The UK’s approach instead routes developer access through certification under its trust framework before granting sandbox access, making it a more gated, less openly documented model.

Were there security concerns raised about One Login before this announcement?
Yes. During a House of Lords debate, Lord Vallance of Balham criticised plans to build a mandatory system on One Login, citing its history of publicly criticised security failures. A government minister responded that those issues dated from 2023 and had been resolved, with the National Cyber Security Centre working on the platform’s security posture.

Does the sandbox closure risk affect other government services that already use One Login?
No. The sandbox is a separate, closed testing environment that uses synthetic data and is kept apart from live user records. It does not affect the 245 live services already using One Login for sign-in and identity verification.

UK Opens One Login Sandbox as Digital ID Shuts [2026]