eIDAS 2.0 · live

Sign in with EU Wallet

Open this page on the device that holds your OpenID4VP-compatible wallet (Aloaha Web Wallet, or any EU-Wallet-format holder) and tap the button. The CodeB Verifier mints a fresh OID4VP 1.0 presentation request signed with ES256, bound to the verifier via the wallet‑preferred x509_hash Client Identifier Prefix (HAIP 1.0 x509_san_dns available as fallback) — your wallet validates it and prompts you for consent. [lhf-2026-07-22] We mint Aloaha-native credentials (urn:aloaha:vc:*), not government EUDI PID.

Why the wallet path is stronger than document-upload or video‑ID flows: OpenID4VP wallets are cryptographic and hardware‑bound, and where the credential is a government-issued EUDI PID it is also government‑rooted. By contrast, video‑ID checks are increasingly spoofable in 2026 with generative AI (face‑swap and voice‑clone deepfakes on a webcam feed), and document uploads can’t prove the document belongs to the person submitting it. The wallet sidesteps both problems.

Scan with a wallet on another device, or tap the button below to open your wallet on this device. Both paths target the same OID4VP 1.0 request URI signed with ES256.

Open EU Wallet on this device

Initialising presentation request…

Open Aloaha Web Wallet (new tab)

No wallet installed? The Aloaha Web Wallet opens in a new tab, receives the same presentation request as the QR above, and posts the signed response back. Your session on this page stays intact and updates automatically when the wallet completes.

First time? How to sign in with the Web Wallet · What the wallet is

Live OID4VP 1.0 + HAIP 1.0 Verifier flow. Every page load mints a fresh signed JAR with an ephemeral P‑256 response‑encryption keypair. The wallet response handler lands once interop with the EUDI reference wallets completes; the request side is production today.
Age verification demo · HAIP implementation notes · EU Wallet feature overview · Free training (dial 1844) · Deutsch