Settle player age and identity in one wallet step, before the first deposit.
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 for the attributes your licence names, and ask for age as a signed boolean rather than a birth date where the rules allow it. You get proof the player is an adult without learning when they were born. Screenshots do not work, because the credential is tied to the holder’s device.
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
The player hits the identity step and the flow opens in place, as a QR code or a deep link.
Step 02
Usually name, nationality and age_over_18. Age comes back as a proof, not a date, wherever your regulator permits it.
Step 03
A verified result lifts deposit and withdrawal limits and leaves you a signed record for the regulator.
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 gambling licence conditions, eIDAS 2.0, GDPR data minimisation
Age and identity requirements come from your national gambling licence, not from eIDAS. eIDAS 2.0 gives you a high-assurance way to meet them, and GDPR data minimisation favours asking for age_over_18 rather than a birth date. Affordability, source of funds, AML and self-exclusion checks remain your responsibility.
Casino onboarding with age and identity verification in one wallet scan.
What it asks the wallet for
What the business gets back
Aurora Bet is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
Yes. Selective disclosure lets the wallet answer age_over_18 as a signed boolean. Whether that alone is enough depends on your licence, since some regimes still want full identification before payouts.
The credential is bound to the holder’s device and needs their device unlock to present. That is a lot harder to get around than photographing somebody else’s passport, which is the standard failure mode of upload-based checks.
Yes. Every member state wallet presents over the same protocol and validates against the same trust list, so a cross-border player is not a separate code path.
Yes. Run the wallet as the fast lane and keep your current vendor for players without a wallet. You decide which players see which option.
The attributes your licence requires, such as name and nationality, plus age_over_18 as a signed true or false. The webhook also carries the verification ID and your player reference for the audit trail.
No. The wallet proves identity and age. Responsible gambling, affordability, AML and source-of-funds checks stay in your existing process.
It gives you verified identity attributes to match against your player base and the national self-exclusion register. The matching itself stays in your systems.
They use your current verification flow. Wallets roll out from the end of 2026 and uptake will grow gradually, so treat the wallet as an additional lane during the transition.
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. Adoption will vary by country, so plan to run both paths for a while.
You get a failed result with a reason, such as a revoked credential or an untrusted issuer, and route the player to your fallback instead of leaving the account in limbo.
E-commerce
The same age verification flow, applied in E-commerce.
Consumer platforms
The same age verification flow, applied in Consumer platforms.
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.