Prove each profile is a real, unique adult without collecting an ID document.
Today
With the EUDI Wallet
The wallet changes how the evidence is collected. The step at the end stays yours.
Why the wallet helps
Selective disclosure separates the trust signal from the identity. The wallet proves the account holder is over 18, is a unique human, and lives in a given country, without giving up a name, a birth date or a document. You get better safety guarantees than an ID selfie and hold far less data.
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
Run the check once when the profile is made and mark the account verified.
Step 02
Typically age_over_18, a uniqueness proof, and residence country. No name, no birth date, no document.
Step 03
A verified badge and verified-only filters turn the check into something users want rather than an obstacle.
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
Online safety and age assurance rules including the UK Online Safety Act and DSA obligations, GDPR data minimisation
Age assurance duties come from online safety rules such as the Digital Services Act and national laws. The wallet gives a government-rooted age proof, and selective disclosure supports GDPR data minimisation. How strict the check must be varies by market, and content moderation remains yours.
Verified-human dating. Real names, real ages, real people — proven by your country, never uploaded as a document.
What it asks the wallet for
What the business gets back
Surepath is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
The wallet derives a pseudonymous identifier that is stable for your platform and cannot be linked to the same person elsewhere. You can tell two accounts are the same person on your service. You cannot tell who they are, and nobody can correlate them across platforms.
It gives you a signed, government-rooted proof of adulthood, which beats self-declaration and facial age estimation. Regulatory acceptance is still settling, so confirm against your target markets.
A boolean, a pseudonymous identifier and a timestamp. That is the whole record. There is no document and no identity to leak.
Yes. Offer the wallet as the privacy-first option and keep your current vendor for users without one.
age_over_18 as a signed true or false, a pseudonymous identifier that is stable for your platform, and a verification ID. No name, no birth date, no document.
They use your existing verification. You can still badge wallet-verified profiles so users see the difference.
Yes. Every EU wallet is verified the same way, so you do not need country-specific vendors.
The pseudonymous identifier stays the same for the same person on your platform, so you can block re-registration without knowing who they are.
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 early adopters first, so keep the fallback.
The verify step in profile creation, the badge, and your moderation rules. Authbound handles the wallet protocol and the proof checks.
iGaming
The same age verification flow, applied in iGaming.
E-commerce
The same age verification flow, applied in E-commerce.
Banking & fintech
The same verify integration, applied to KYC.
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.