Concept image · AI-generated

Retail · Age
Age checks at the self-checkout, no waiting for staff
The till gets a yes or no on 18+ from the wallet. No staff approval needed, and the date of birth never leaves the wallet.
Age checks for your tillA few concepts for age verification, mobile driving licences and identity with the EUDI Wallet, all on the same API.
The images are AI-generated concepts. Places, people and screens are fictional.
Concept image · AI-generated

Retail · Age
The till gets a yes or no on 18+ from the wallet. No staff approval needed, and the date of birth never leaves the wallet.
Age checks for your tillConcept image · AI-generated

Venues · Age
Staff see a signed yes from the wallet instead of studying cards in the dark. No names or dates of birth.
Age checks at the doorConcept image · AI-generated

Car rental · Driving licence
The desk gets categories, expiry and photo straight from the wallet. No card copies, nothing typed in by hand.
Licence checks for your deskConcept image · AI-generated

Authorities · Driving licence
The handheld reads the digital licence with photo and categories, signed by the issuer, even when the card is at home.
How licence checks workConcept image · AI-generated

Construction · Identity
Identity and A1 certificate arrive verified from the wallet, ready for the staff register. No paper copies to dig out.
How identity checks workArizon.id is a verification platform from Swedish company Arizon AB for stores, online retailers, banks and public agencies that want to verify customers with the EU Digital Identity Wallet. One API for age verification, identity and address, where the wallet shares only what you ask for. Integrate today and go live from day one when the wallet launches.
Sign in with Microsoft, Google or GitHub. Your first API call takes a few minutes.
Example Store
is requesting data from your EUDI Wallet
Are you 18 or older?
Your name, date of birth and national ID number
Your residential address
The store learns
Yes, over 18
Those three details, nothing else
The address, nothing else
The EUDI Wallet holds credentials from member states, public bodies and companies. Arizon.id accepts them through the same API, and you choose in each request which data you need.
Following the EU age verification blueprint
A yes or no on an age limit, with no other data.
From the member state
Name, date of birth, place of birth and nationality, and optionally address and national ID number.
From the licensing authority
Mobile driving licence under ISO 18013-5, with categories and validity.
From universities and colleges
Degrees, titles and other educational credentials.
From competent authorities
Professional qualifications, licences to practise, permits and licences.
From healthcare
Prescriptions that can be collected at a pharmacy, even in another EU country.
From social security institutions
The European Health Insurance Card and proof of coverage when working in another EU country (A1).
From issuing authorities
Passports, visas and other travel documents for flight and hotel check-in.
From the vehicle register
Vehicle registration certificates.
From authorities and registers
The right to represent a person or a company, and which organisation someone works for.
From business registers
Registration and financial data about legal persons.
From population registers
Civil status, family composition and gender.
The list is based on eIDAS 2.0 Annex VI, the EU attestation rulebooks and the Commission's wallet use cases. Companies and organisations can also issue their own credentials, such as employment and membership, and these can be qualified (QEAA) when a qualified trust service provider stands behind them.
See what each credential containsYou create your organisation, set up your clients as applications, get API keys and run the full verification flow in the sandbox, without waiting on anyone.
With a Microsoft, Google or GitHub account. Create your organisation and invite the colleagues who will manage your clients.
An application is one of your clients, such as a web shop, an app or a checkout system. It gets its own environments, keys and webhooks, and with EUDI Verify its own permissions for which data it may request.
Your sandbox API key works right away. In production you switch to the production key; the code stays the same.
Run it straight from the browser or from your own code.
POST /v1/av/sessions Host: live.id.arizon.se X-Api-Key: av_prod_•••••••• { "age_threshold": 18 }
{
"session_id": "prd_8f3c…",
"wallet_invocation_uri": "openid4vp://…"
}
TypeScript, Python, C#, Go, Java, Kotlin, Swift and ReScript.
Real API calls straight from the API reference.
Signed events per environment, with delivery history, resend and alerts on failure.
Every client has a production environment and its own sandboxes, for example for development, staging and demos. Each has its own key, webhook, limits and retention.
Rotation with a 30-day overlap and email reminders before a key expires.
Invite colleagues as reader, admin or owner. Roles control who can manage clients, keys and webhooks.
The portal issues credentials straight to a wallet, so you can run the whole flow from scan to answer while you build.
Step by step: age verification, environments, key rotation and webhooks.
Arizon.id handles the wallet, the trust lists and the check of every credential. Before you get an answer, the credential has been checked against the EU trust lists, so you know it is genuine and comes from a trusted issuer.
Two solutions on one platform. AV Verify answers an age threshold. EUDI receives everything the wallet can attest, and you choose how isolated it runs: the more isolation, the more you can do, such as issuing your own credentials or keeping keys in your own HSM. Most start with AV Verify in the developer portal.
EUDI · one solution, four ways to run it
| EUDI · one solution, four ways to run it | |||||
|---|---|---|---|---|---|
| AV Verify Age verification | EUDI Verify Shared platform | EUDI Hosted Own instance | EUDI Dedicated Dedicated hardware | EUDI On-Prem In your environment | |
| Verifies | Age, as a yes or no on an age limit | Every credential in the wallet, from identity and driving licence to education, powers of representation and company data | Everything in the wallet, as in EUDI Verify | Everything in the wallet, as in EUDI Verify | Everything in the wallet, as in EUDI Verify |
| Issues credentials | Not included | Not included | Your own credentials to users' wallets, such as membership or employment | Your own credentials, including qualified (QEAA) and public-body (PuB-EAA) attestations | Your own credentials, including QEAA and PuB-EAA, with your own keys |
| Stores verified credentials | Not included | Not included | As an option, so several of your systems can retrieve a verified credential over time | As an option | As an option |
| Operation | Arizon, on a shared platform within the EU | Arizon, on a shared platform within the EU | Arizon, in your own logically separated environment with its own database and HSM partition within the EU | Arizon, on dedicated hardware with its own HSM, in the EU region you choose | You, in your own infrastructure. Can run with no connection to Arizon at all. |
| Best when | You sell tobacco, nicotine, alcohol or anything else with an age limit | You need identity or credentials, for example for customer due diligence and account opening | You want to issue your own credentials or reuse verified data | You are a regulated business, a qualified trust service provider or a public body | Data and keys must never leave your own environment |
| Get started | Get started in the portal (opens in a new window) | Contact us | Contact us | Contact us | Contact us |
The user sees what is being requested and approves the share in their wallet. Your service receives exactly that data and nothing else.
Your service
Creates a session and states what to check, such as an age limit
Arizon.id
Provides a QR code or link for the session
The user
Scans with the wallet, which connects to Arizon.id and fetches the request. The user approves the share.
The result
The wallet sends the answer to Arizon.id, which verifies it and gives your service exactly what was requested
The EU defines three assurance levels for electronic identification: Low, Substantial and High. The EUDI Wallet is required to meet level High, and Arizon.id is built to receive and check credentials from exactly those wallets.
For an age check you get a yes or no. For an identity check you get the fields you requested and no others. What you never receive you don't have to manage under GDPR.
Users see in their wallet exactly what is being requested and approve the share themselves. Without approval, nothing is shared.
Under eIDAS 2.0, every member state must offer an EUDI Wallet by the end of 2026. With Arizon.id your integration is done by the time the wallet reaches your users.
Build your integration in the developer portal. The portal issues credentials to a wallet, so the whole flow works from the first day exactly as it does in production.
Production is activated for each country as the EUDI Wallet launches there. With AV Verify you switch to your production key and the code stays the same. Identity and other credentials also require a relying party registration certificate.
Add identity, address or other credentials when you need them. It is the same integration with more data in the request and, in production, a relying party registration certificate.
Everything the EUDI Wallet can prove via OpenID4VP, including age, identity (PID), address, professional qualifications and other credentials. You integrate once and choose in each request what you need.
Only what you explicitly request and the user approves. For an age check you get only a yes or no, no names, dates of birth or ID numbers.
Sign in to the developer portal (portal.id.arizon.se) with a Microsoft, Google or GitHub account, create an application for your first client and get the API key. Then run your first verification in the sandbox, straight from the browser or from your own code, with guides and code examples in eight programming languages. You can start building the same day, without waiting for us.
With AV Verify you switch to your production key and the code stays the same. To verify identity or other credentials you also need a relying party registration certificate, issued by an authority in the member state where you are established. eIDAS 2.0 requires it of everyone who receives data from the wallet, and it is why the wallet can show the user who is asking. Production is activated country by country as the EUDI Wallet launches. Get in touch and we'll walk through the timeline for your markets.
Arizon.id uses the EUDI Wallet and OpenID4VP under eIDAS 2.0, and the wallet is required to meet assurance level High. Every verification returns a session id, a status and a timestamp you can keep as a record of your age check, and sessions are visible in the developer portal. When you assess the requirements for your business, such as alcohol or tobacco legislation, we're glad to provide technical documentation.
Yes. EUDI On-Prem is the same platform delivered to your own infrastructure, and it can run with no connection to Arizon at all. If you need isolation without running it yourself, EUDI Dedicated runs on dedicated hardware in the EU region you choose.
Integrate Arizon.id today via the developer portal. To talk terms, timelines or your markets, get in touch.