iGaming

Age and identity verification for online gambling

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.

The problem

What teams do today

Regulators want age and identity confirmed before a player deposits, and proof of it at audit. Most operators bolt a document-upload vendor into the funnel, lose a chunk of players before first deposit, and end up custodians of a passport image library nobody wanted.

01
Age and identity settled in one step, not an upload and a wait
02
Borrowed documents and screenshots fail on device binding
03
You store a boolean instead of a birth date
How it works

Three steps with Authbound

  1. Step 01

    Verify at registration

    The player hits the identity step and the flow opens in place, as a QR code or a deep link.

  2. Step 02

    Request what the licence names

    Usually name, nationality and age_over_18. Age comes back as a proof, not a date, wherever your regulator permits it.

  3. Step 03

    Unlock the account

    A verified result lifts deposit and withdrawal limits and leaves you a signed record for the regulator.

Rules in play

National gambling licence conditions, eIDAS 2.0, GDPR data minimisation

Live demo

We built Aurora Bet, a company that does not exist, to show this running inside a finished product. The wallet flow in it is the real SDK.

Open the Aurora Bet demo
Questions

What people ask

Can we check age without seeing a date of birth?
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.
How does this stop a minor using a parent’s ID?
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.
Does it work for players from other EU countries?
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.

Built on Authbound Identity Verification. One API key covers every flow you add later.