Age and eligibility checks
Build an eligibility flow around an age proof such as age_over_18, with the request limited to the attributes declared for that use.
EUDI Wallet verification for relying parties
One API for privacy-preserving identity and age verification with EUDI Wallets. Purpose limitation is enforced before the QR code is shown.
DLBR EID is in private pilot with selected businesses. Test an age verification or identity onboarding journey with direct integration support. You define the purpose and required attributes; the gateway blocks requests outside that scope before creating a session or QR code.
Pilot use cases
Identity onboarding
Request the identity attributes needed for a specific onboarding step, such as given_name and family_name.
Strong Customer Authentication (SCA / TS 12)
A separately scoped pilot for banks, payment institutions and e-money issuers, based on the wallet, issuer and authentication factors required.
Claims are deleted within 30 seconds.
How it works
- 01
Set an intended use and the attributes needed for that customer journey.
- 02
The gateway checks the request before creating a session. An out-of-scope claim is refused before a QR code is issued.
- 03
In-scope requests continue to the wallet, and the verification result returns to your existing application flow.
A clear request boundary
{
"error": "ERR_CLAIM_OUTSIDE_INTENDED_USE",
"message": "The requested claim is not declared for the selected intended use"
}For an is_over_18 use, a request for birth_date returns 403 with ERR_CLAIM_OUTSIDE_INTENDED_USE before a session exists. See how declared-use checks work
Strong customer authentication
The Gateway implements EUDI TS 12 flows, including checks on wallet-signed transaction binding and configured authentication-factor policy. For a bank or payments pilot, we agree the transaction journey, wallets, issuers and factors to test together. Gateway verification is one part of the institution’s wider SCA assessment. Read the SCA guide for banks
Wallet coverage and pilot scope
We agree the wallets, credentials and target markets for each pilot. Synthetic tests and observed real-wallet results are recorded separately; support for a format alone does not establish compatibility with every wallet. National relying-party registration and access requirements also apply. The Gateway’s declared-use check does not establish national registration or certificate status. Compare wallet availability and access requirements
Plan your target market
Compare national wallet initiatives, availability and official access requirements before planning a pilot. Explore wallets by country
Data handling
Verification sessions, including selected claims, are stored and processed in Cloudflare’s EU jurisdiction; claims are deleted within 30 seconds of the result. Audit records contain no claim values and are kept in an EU-jurisdiction database. For details about the rest of the platform, see the privacy notice .
Plan your private pilot
Test one customer journey with direct integration support and agreed success criteria.