Betting and gaming

Age verification for iGaming

Every licensed market makes you check a player's age. Tessio can always check over 18, and it can check a higher bar such as 21 where the credential carries it. You get a signed yes or no and hold no ID data. Players prove their age with the EU age verification app (the EU Digital Identity Wallet follows once our access certificate is issued).

Create an account → See the API

The problem

Betting and gaming operators have to verify age in every market they hold a licence in. One way is a document scan or a database check at signup, which adds a step for the player and brings identity data into your flow.

Tessio asks for one fact instead. The player proves they are over 18 from a wallet credential and you get a signed boolean, so you keep the answer you need and nothing else.

Before and after

Without Tessio

Document upload or database check at signup.
You store identity documents and dates of birth, so a breach exposes real player data.
Separate tooling per market with its own data handling to review.

With Tessio

The player confirms 18+ in the EU age verification app, with no document to upload.
You store a signed over 18 yes or no, so there is no player ID data to leak.
One integration for your EU markets, wherever players have the EU age verification app.
Built on the standards both EU wallet paths use.

How it works

Call the API at signup

POST an age check when a player registers or before their first deposit. You get back a hosted verification link.

The player confirms 18+

They prove they are over 18 in the EU age verification app. No ID scan and no selfie.

You get a signed result

A signed yes or no lands on your webhook. You record the answer for your licence and store no documents or dates of birth.

Start a check

One POST creates a check and returns a link for the user's wallet. The signed result lands on your webhook. Full detail is in the developer docs.

curl -X POST https://api.tessio.eu/v1/age-checks \
  -H "Authorization: Bearer tk_your_key" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: signup-4821" \
  -d '{ "minAge": 18, "reference": "signup-4821" }'

Frequently asked

Does this satisfy licensing age checks?

Tessio proves a player is over 18 and gives you a signed, auditable result you can keep as evidence. Age rules are set by your national gambling regulator and licence conditions, so check that a wallet based over 18 proof meets your specific market. We are happy to talk through what your regulator expects.

Will it hurt conversion?

We have no conversion figures yet. A wallet confirmation needs no document upload, so it asks less of a player who has the app than a document scan does. Tessio does not offer a document or selfie fallback, so players without the app need another method alongside it.

What do you store about players?

No document and no date of birth. You get an over 18 yes or no, and the check record holds technical details such as which issuer signed the credential. The privacy page lists every field.

Put it in front of your users

Signup is open and a test project works as soon as you create one. Sending real traffic needs us to switch your organisation to live mode, so that part stays a conversation. Pricing is published, with no quote needed.

Create an account → Read the docs