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.
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.
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.
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 demoBuilt on Authbound Identity Verification. One API key covers every flow you add later.