The EU age verification app: what it is and what websites need to integrate

How the EU age verification blueprint and app work, which Member States pilot it, how it relates to the EU Digital Identity Wallet (eIDAS 2.0) and what a website has to build to accept it.

Last reviewed Published

In short

  • The EU age verification solution is an open source blueprint and app that lets a person prove they are over 18 without sharing any other personal data. The Commission made the blueprint public on 14 July 2025 and called it feature ready on 15 April 2026.
  • Seven Member States lead the rollout: Cyprus, Denmark, France, Greece, Ireland, Italy and Spain. National apps are expected to appear during 2026, and the Commission recommends that every Member State offers one by 31 December 2026.
  • It is built on the same specifications as the EU Digital Identity Wallets, which Member States must also offer by the end of 2026, and can run standalone or inside a national wallet.
  • A website integrates by asking the browser for a proof through the Digital Credentials API, checking the signature against the EU trusted list and accepting a signed yes or no. The Commission says the reference verifier is not production ready.

What it is

The EU age verification solution is a Commission project made of a technical blueprint, an open source reference app and a set of specifications. It lets a person prove they are over a threshold, starting with 18, without handing over a name, a birth date or a document. The Commission says it can be adapted to other thresholds such as 13 or 65.

The blueprint was made available on 14 July 2025 together with the Commission's guidelines on protecting minors under the Digital Services Act. On 15 April 2026 the Commission described it as a feature ready solution that Member States and market players can customise, for example by translating it. The customisation may not change the privacy features. The reference code and specifications live at ageverification.dev.

The Commission calls the app a "mini wallet" in some material. It is not a general identity wallet. It holds one thing, a proof of age. Our guide to DSA Article 28 explains why the Commission points platforms to it as a reference standard.

How a person gets and shows a proof

According to the Commission's Q&A, a user certifies their age once, using a biometric passport or ID card, a national eID, a pre installed third party app such as a banking app, or in person. The app then holds the over 18 proof. When a site asks, the person approves in the app and only the confirmation is shared. The Commission states that no name or birth date is saved, that transactions by the same user are not linked, and that the app keeps no trace of the sites visited.

Behind that sits a specific design. The age verification profile defines the proof as an ISO mdoc credential with its own document type, and the newest revision of the project (August 2026, per ageverification.dev) makes a zero knowledge proof the mandatory way to present it, with a plain mdoc presentation as the fallback. With a zero knowledge proof the site can check that the issuer vouched for "over 18" without receiving a reusable identifier.

Anyone can build an app from the blueprint, public bodies and private companies alike. The Commission says users will be able to choose between apps and that it will publish a list of trustworthy ones and a list of trusted proof of age providers. It also plans to work with Apple, Google and other app stores to allow only official versions.

Which Member States pilot it

The Commission names seven frontrunners in its Q&A: Cyprus, Denmark, France, Greece, Ireland, Italy and Spain. According to ageverification.dev they are piloting the solution within their national wallets during 2026, and other Member States are developing their own versions. We found no consolidated public list of which national apps are live for ordinary users, so check each country's government site before you plan around it.

Greece is a useful example of why this matters. It runs national digital age checks of its own, described by Euronews as mirroring the EU approach, and we could not confirm from public documents whether they use the same technical profile as the blueprint. Treat country by country compatibility as an open question until you have tested it.

How it relates to the EU Digital Identity Wallet

The EU Digital Identity Wallet comes from Regulation (EU) 2024/1183, often called eIDAS 2.0, which amends the original eIDAS Regulation. Each Member State must provide at least one wallet within 24 months after the Commission's implementing acts took effect. The Commission's own summary says wallets are to be offered to citizens by the end of 2026. The regulation states that use of the wallet is voluntary and free of charge for natural persons.

The age verification solution is built on the same technical specifications, so it can be offered as a standalone app or inside a national wallet (Q&A). The Commission's guidelines add that every Digital Identity Wallet is designed to be able to receive a token of age, and that Member States can run services that issue them (see the box after paragraph 42 of the guidelines).

Be careful with one point. The eIDAS rules that require some businesses to accept the wallet (Article 5f) concern identification and strong authentication, and cover regulated sectors and very large online platforms. They do not create a general duty to accept the wallet for age checks, and microenterprises and small enterprises are excluded. A site that only wants to know "over 18" is not forced onto the wallet by this rule.

Timing is uncertain. The deadline is the end of 2026, but some reporting from April 2026 (Biometric Update, a secondary source) says the Commission doubts all Member States will make it. Plan for a staggered rollout in 2027.

The Commission recommendation

On 29 April 2026 the Commission adopted Recommendation (EU) 2026/1035. It asks Member States to make sure all citizens have access to robust, privacy preserving age verification by 31 December 2026, to use the EU blueprint and to draw up implementation plans. The Commission also says it will set up an EU age verification scheme with a list of compliant solutions. A recommendation is not binding, so the date is a target and not a legal deadline.

What a website needs to integrate

The Commission's developer guide for verifiers describes the website side. In plain terms:

  1. Decide the threshold, when the check triggers and how often it repeats. Do this with your compliance team, using the Commission guidelines.
  2. Ask the browser for the proof with the W3C Digital Credentials API. The guide calls this the primary route. Chrome 141 and later ship the API on Android, on desktop through a QR code to a phone wallet, and on iOS 26 or later. Browsers that lack the API need the OpenID4VP fallback.
  3. Support all combinations and choose at runtime, in the order the guide gives: Digital Credentials API with a zero knowledge proof, then Digital Credentials API with a plain mdoc, then OpenID4VP with a plain mdoc.
  4. Validate every proof against the EU age verification trusted list before granting access. The Commission publishes the production list and a separate test list.
  5. Check the nonce and the binding to your request so a proof cannot be replayed, and treat each proof as single use.
  6. Grant access on the yes or no, and do not store anything else about the check.
  7. Plan a fallback for visitors with no compatible wallet or browser, and offer a second method as the guidelines advise.

Two points from the profile matter for planning. First, for the age verification app the profile says reader authentication and client authentication are not required, and relying party registration is out of scope, so there is no registration step for the app path today (profile). Second, the profile is versioned and can change.

The EUDI Wallet path is different. Businesses that want to rely on EUDI Wallets register in the Member State where they are established, under Implementing Regulation (EU) 2025/848, which applies from 24 December 2026. National registers and access certificate providers will appear at different speeds.

The developer guide also warns that neither reference implementation is production ready and that the hosted reference verifier is for development only. You must build and host your own verifier or use a provider. Plan for engineering time to verify the cryptography, including zero knowledge proofs, and to keep up with spec changes.

What is still undecided

  • How many national apps will be live to the public by 31 December 2026, and whether they all use the blueprint profile.
  • How the EU age verification scheme and its lists of trusted solutions will work in practice.
  • Whether and how the proposed EU KIDS Act, which is still a proposal, will change age check duties for platforms.
  • Which methods regulators accept for national obligations such as alcohol sales or social media age limits.

Where Ageseal fits

Ageseal is building the verifier side described above: a script and an API that request the proof, check it against the trusted list and return a signed yes or no to your server. It is in development, has no customers yet and does not claim any certification.

Sources

  1. European Commission: EU age verification app and blueprint
  2. European Commission: questions and answers on the EU age verification solution
  3. EU age verification project: blueprint and specifications (ageverification.dev)
  4. Age verification profile (annex A of the technical specification)
  5. Developer guide for verifiers
  6. EU age verification trusted list
  7. Commission Recommendation (EU) 2026/1035
  8. Regulation (EU) 2024/1183 (eIDAS 2.0) on EUR-Lex
  9. European Commission: EU Digital Identity Regulation
  10. Implementing Regulation (EU) 2025/848 on registration of wallet relying parties
  11. Commission guidelines C(2025) 6826 under Article 28(4) DSA (PDF)
  12. Euronews, 18 March 2026: Greece launches digital age verification for tobacco and alcohol
  13. Chrome: Digital Credentials API shipped in Chrome 141
  14. Biometric Update, April 2026: doubts that all Member States will launch wallets this year (secondary)

This guide is general information, not legal advice. Check your own duties with a lawyer or your regulator.

Ageseal is building the wallet check described here

A script tag asks the visitor’s wallet whether they are over 18 and your server gets a signed yes or no. Ageseal is in development and has no customers yet. Join the waitlist to hear when test mode opens.

Join the waitlist