Prove a shopper is over 18 without learning their birth date.
Today
With the EUDI Wallet
The wallet changes how the evidence is collected. The step at the end stays yours.
Why the wallet helps
Ask the wallet one question. Is this person over 18. It answers with a signed proof and nothing else. You get a compliance artefact and store a boolean, which is about as little personal data as the obligation allows.
01
You request specific attributes
02
The user gets the request by QR or deep link
03
The wallet shows exactly what is asked
04
The user approves on their device
05
The wallet presents the signed credential
06
Authbound verifies the presentation
07
Your backend receives a structured result
08
Your existing workflow continues
Step 01
Put the check at add-to-cart or checkout. Gating the whole storefront kills your organic traffic for no compliance benefit.
Step 02
We request age_over_18 and nothing more. The shopper sees exactly that on their consent screen.
Step 03
The order carries a signed verification reference. No document, no birth date, nothing that identifies the shopper beyond the order itself.
Technical flow
const verification = await authbound.verifications.create({
policyId: 'pol_…', // the claims this flow requests
customerUserRef: user.id,
});
// Your webhook then receives verification.completed
// with the verified result and its audit record.Wallet presents
Terms to know
Regulatory context
National alcohol and tobacco sales law, GDPR data minimisation, eIDAS 2.0
Age limits for alcohol, tobacco and similar goods are national law, and so is the standard of proof for distance selling. eIDAS 2.0 makes a government-rooted age proof available, and GDPR data minimisation favours a yes or no over a birth date. Delivery-time checks required in some markets stay with you and your carrier.
Selective disclosure age-checking for a premium wine storefront.
What it asks the wallet for
What the business gets back
Halcyon Cellars is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
A signed assertion that age_over_18 is true, plus the issuer identity and a timestamp. No name, no birth date, no image, unless you explicitly ask for them.
The proof is signed by a government-recognised issuer and checked against the EU trust list, which is stronger evidence than a scan somebody eyeballed. Requirements still vary by member state and product, so confirm the standard for your market.
At purchase intent. Verifying only shoppers who were going to buy anyway costs you nothing in traffic and nothing in conversion.
Yes. Offer the wallet as the one-tap option and keep your existing method for shoppers without one.
They fall back to your current check. Nothing about the order flow has to change for them.
If your market requires it, yes. A wallet proof covers the online sale, while hand-over rules are set nationally and usually apply to the courier.
Yes. The age proof is checked against the same EU trust lists wherever the wallet was issued. Which age limit applies is still decided by the law where you sell.
Each order can carry its own proof in seconds, so you do not need to keep identity data between orders to make repeat purchases fast.
Every member state has to offer a wallet by 24 December 2026. Private services that are legally or contractually required to use strong user authentication have to accept it from December 2027 when the user asks. Expect a mix of wallet and non-wallet shoppers for a while.
Yes. EUDIW Age Gate, Authbound’s app on the Shopify App Store, blocks age-restricted checkout until the shopper proves age with their wallet.
iGaming
The same age verification flow, applied in iGaming.
Consumer platforms
The same age verification flow, applied in Consumer platforms.
E-commerce
Another wallet flow for E-commerce.
Built on Authbound Identity Verification. One API key covers every flow you add later.
Tell us what you are trying to build. We will map the user journey, the credentials and the wallet interaction to an implementation.