Age Verification for Retailers: One Check, Every Channel

A shopper picks up a bottle of wine at a manned till. The colleague glances at them, decides they look young, and asks for ID. The shopper digs through a wallet, produces a driving licence, and the colleague checks the photo, the date of birth, and the holographic mark before the sale goes through. The queue waits. A few minutes later the same shopper opens your app on the train home, adds the same bottle to a basket for delivery, and faces a completely different request. A face scan, perhaps, or a passport upload.

Same person, same product, same retailer. Two age checks that share almost nothing.

That gap is a direct consequence of how the rules are written, and it shapes what your shoppers experience at every point where they buy from you. For retailers selling alcohol across stores, apps, websites, and delivery, age verification has become a stitched-together patchwork of methods that behave differently depending on where the shopper happens to be standing.

Why the checkout and the basket follow different rules

In a shop, the law governing an alcohol sale is the Licensing Act 2003, supported by the Challenge 25 scheme that most responsible retailers operate. The accepted proof is a recognised form of identification carrying a photograph, a date of birth, and a holographic mark. The Retail Age Standards Group has been clear on a point that matters here: facial age estimation is not currently permitted to authorise the sale of alcohol in store [1]. A colleague can use judgement to decide who to challenge, but the proof that clears the sale has to be a document of a recognised type.

Online, a different regime applies. Under the Online Safety Act, Ofcom assesses whether an age assurance method is capable of being highly effective. In its January 2025 guidance, updated in April 2025, Ofcom set out methods that can meet that bar, including open banking, mobile network operator checks, photo ID matching, and facial age estimation [2]. Facial age estimation is therefore accepted for a digital sale, while at the till it cannot be used to authorise the same purchase.

For the shopper, this is invisible and slightly maddening. They prove their age one way at the self-checkout and another way in the app, and neither feels connected to the other. For the retailer, it means running multiple providers, multiple integrations, and multiple sets of compliance policies to cover the same purchase across channels. Every join between those systems is a place where a check can fail and a sale can drop.

Where age verification at self-checkout actually breaks

Walk the channels and the friction shows up in different forms.

At the manned till, document handling slows the queue and puts the decision on a colleague who has to make the same judgement consistently across thousands of transactions. At self-checkout, an age prompt stops the shopper dead until a member of staff walks over, which is the moment people abandon the basket and leave. In a scan and go app, the age gate sits inside the retailer's own flow, so any friction there reflects directly on the brand. Online, the cost is measured in abandonment, and shoppers who hit a clumsy age check at the basket rarely come back to finish.

Then there is delivery and collection. When alcohol is handed over at the door or released from a locker, the age check has to happen at the point of handover, with an audit trail to prove it did. A driver checking a physical document at a doorstep is slow and inconsistent. A locker has no human to make the judgement at all.

None of these are edge cases. They are the everyday reality of selling age-restricted goods across modern retail, and each one currently demands its own approach.

What is about to change

Two developments are pulling these channels towards a single answer.

The first is regulatory. The Home Office has committed to amending the mandatory licence conditions so that a digital identity certified under the UK's digital verification services framework can serve as proof of age for an alcohol sale in store. It would apply to certified digital credentials only. Facial age estimation would stay outside the change. The change was expected in 2025, slipped, and as of January 2026 has been recommitted to as soon as possible this year [3]. It is not yet law, so the in-store regime described above still stands for now. The direction of travel is clear, though, and retailers building for it today will not be retrofitting later.

The second is the wallet. The GOV.UK Wallet's digital driving licence entered a wider public pilot in February 2026, with full rollout expected in summer 2026, and the Government Digital Service has confirmed that certified verification providers are being enabled to test programmatic checking of those credentials this year [4]. A digital credential held in a wallet is cryptographically signed and confirmed against the issuing authority's own records, rather than estimated from a photograph. That is a different class of proof from a document scan, and it is the same proof whether the shopper is at a till or in a basket.

Put those two together and the picture for retail comes into focus. A digital credential, held in a wallet, accepted at the till once the licence conditions are amended, and already accepted online. One form of proof that works the same way wherever the shopper buys.

What durable age verification for retailers looks like

The risk right now is building for today's methods and rebuilding in two years when wallets reach scale. A design that lasts shares a handful of properties, and none of them are exotic.

Start with a single integration. One connection serves the manned till, self-checkout, scan and go, online, delivery, and collection, rather than a separate build per channel, and the compliance policy lives in one place so it applies consistently everywhere a shopper buys.

Shoppers will hold their proof of age in different places: the GOV.UK Wallet, Apple Wallet, Google Wallet, or a retailer's own app. A check that accepts credentials from all of them feels native to the shopper, while anything tied to a single wallet pushes the rest down a path they did not choose at the point of sale.

Wallet standards are still settling, so interoperability matters and lock-in is a real risk. A retailer tied to one provider's closed approach inherits that provider's limits. An open design lets the retailer add channels, add wallets, and change suppliers without tearing up the integration.

Coverage has to reach the whole adult population from day one, and no single credential manages that on its own. Around 98% of UK adults hold a current account and about three-quarters hold a driving licence [5], while roughly 88% hold a passport [6]. Mobile contactability through our own coverage reaches roughly seven in ten. A bank, a mobile, a document, and a digital wallet credential, taken together, reach effectively the entire adult population. The way to deliver that on day one is a fallback cascade: a shopper who already holds a credential is checked instantly; one who does not verifies through whichever route fits, and the result is saved to a wallet so the next check is a single tap.

That last point is what changes the shopper's experience for good. They prove their age once, and from then on the check is a tap of the phone, under five seconds, with no document to dig out and no staff member to call over.

How OneID fits

This is the model OneID is built for. We sit between consumer wallets and retail channels as an access layer, handling credential verification, compliance policy, fallback, and a consistent experience across every channel through a single REST API that works alongside the point-of-sale and ecommerce systems a retailer already runs.

Five of Ofcom's seven highly effective age assurance methods are available through OneID, which more than 12 million people in the UK have now used, with over 5 million OneID wallets in use today. OneID is certified under the UK's digital verification services framework as the first identity service provider, the first orchestration service provider, and the first holder and wallet provider, and is FCA regulated, a B Corp, and ACCS accredited.

On the GOV.UK Wallet specifically, as the first certified holder and wallet provider and an approved Google Wallet provider, OneID is positioned to verify the digital driving licence credential as it reaches production. The platform is built to accept it alongside bank-verified data, mobile network checks, and ID documents through the same integration, so a retailer adds the new credential without a new build.

Named clients include NatWest and Anna Money in financial services, with Adobe among the wider customer base.

Which retailers are ready first

The retailers who move now will not be the ones scrambling when the licence conditions change and wallets reach scale. They will already run one integration and one compliance policy across every channel, with shoppers who prove their age once and never think about it again. As AI agents begin to buy on shoppers' behalf, that same verified credential becomes the trust layer those transactions depend on, so the work done for age verification today carries forward.

The build that lasts is the one that treats every channel as the same check. A retailer can phase it in, starting with the channel where the friction costs most, and add the rest on the same foundation. The shopper notices only that buying a bottle of wine stopped being the slowest part of the visit.

References

  1. Retail Age Standards Group, "Digital Proof of Age for Sales of Alcohol." https://www.rasg.org.uk
  2. Ofcom, "Guidance on highly effective age assurance and other Part 5 duties," 16 January 2025, updated 24 April 2025. https://www.ofcom.org.uk/online-safety/protecting-children/age-assurance-and-childrens-access
  3. Biometric Update, "UK Home Office recommits to digital ID for alcohol age verification," January 2026. https://www.biometricupdate.com. See also House of Commons Library, Standard Note SN05351, "Alcohol: minimum age and proof of age." https://commonslibrary.parliament.uk
  4. DVLA, digital driving licence public pilot announcement, February 2026; Government Digital Service, "Bringing the GOV.UK Wallet to life," 21 January 2026. https://gds.blog.gov.uk
  5. Financial Conduct Authority, "Financial Lives 2024 survey," 2024 (current-account and driving-licence holding rates). https://www.fca.org.uk/financial-lives
  6. His Majesty's Passport Office, UK passport holding figures, GOV.UK. https://www.gov.uk/government/organisations/hm-passport-office

 

Recent posts

Choosing a digital identity partner is now a longer-term product decision.

For product, compliance and engineering teams, the provider you choose has to meet today’s requirement. ...

Age Verification for Online Gambling in the UK: What Operators Need

A player signs up, picks a welcome offer, and reaches for their card. Before any money moves, a screen a...

Where next for UK government digital ID?

As the UK government digests the 90k responses to the consultation on whether or not it should create a ...