An age-restricted service may need to know whether a customer is over 18. A supported Proof of Age credential can answer that threshold question without requesting a full identity document or date of birth. Plan the evidence, customer journey and recovery process before introducing wallet age verification.
Ask for the fact your service needs
A document image contains details that an age check may not require, including a name, document number and address. Define the threshold your service needs and evaluate whether an accepted age credential can provide that evidence.
In DLBR’s dedicated EUDI Proof of Age mDOC flow, a request can ask for age_over_18. That credential is separate from personal identification data. The service checks the presented evidence and uses the verified threshold result in its own policy.
Sharing fewer attributes does not establish every privacy guarantee. Review the actual presentation profile and data handling with your team. Do not assume all wallets, issuers or age-verification methods disclose the same information.
Fit the check into checkout or service access
An online store can place the age check before a customer continues to a restricted checkout. Explain the required age evidence and let the customer approve the wallet presentation.
The journey can follow these steps:
- Tell the customer which age threshold your service requires.
- Request a supported Proof of Age presentation through a wallet link or QR code.
- Verify the evidence and apply your service’s access policy.
- Show a recovery step if accepted evidence is unavailable or rejected.
DLBR has an open-source WooCommerce plugin for evaluating wallet age checks at checkout. Test how the check interacts with your store’s existing customer journey before enabling it for customers. Explore the WooCommerce age-verification plugin.
Confirm the credential and issuer coverage
Your customers need a compatible wallet and accepted age credential. Confirm the presentation profile and issuer trust for your intended market rather than assuming every EUDI Wallet contains the required evidence.
The European Commission’s age-verification blueprint describes a privacy-preserving solution and its presentation requirements. Those requirements evolve, and they are not a claim that every DLBR deployment supports every blueprint profile. Review the EU Age Verification Blueprint alongside the profile you intend to pilot.
Your reviewers should also confirm the age-assurance rules that apply to the service. Technical verification returns evidence; your business decides when that evidence is sufficient and what happens next.
Measure the customer and operational experience
During a pilot, record whether customers complete the wallet handoff, whether the issuer and credential are accepted, and how recovery works. Include unsuccessful presentations and customers without compatible evidence.
Review which data reaches your application, which verification records it keeps, and which details support teams need. A useful pilot tests the full checkout or service-access journey, including the failure paths.
Plan your wallet age-verification pilot
DLBR EID lets your team evaluate supported Proof of Age presentations and connect the verification result to its existing service. The pilot is underway. Production is planned for Q2 2027.
Explore privacy-preserving EUDI Wallet age verification, then request pilot access to discuss your threshold, target markets and customer journey.