European Digital Identity Wallet interoperability matrix.
Interoperability with the European Digital Identity Wallet ecosystem varies by wallet vendor, credential format (SD-JWT VC vs mDoc), device-topology (same-device vs cross-device), and trust framework (LOTL vs national list). The CodeB verifier accepts both wire formats today — SD-JWT VC + KB-JWT and ISO 18013-5 mDoc (mso_mdoc) — and advertises both in vp_formats_supported. The table below lists the wallets whose interoperability we have tested against our verifier. Empty cells reflect combinations we have not exercised in a formal test run; blank rows are not a statement about wallet quality.
Our verifier is spec-conformant per the OpenID Foundation OID4VP + HAIP conformance harness (alpha) — see the HAIP verifier certification page for the certified test outcomes. Interop against any specific Member-State wallet is a separate exercise.
| Wallet | Country | Version | Test date | SD-JWT VC | mDoc | Same-device | Cross-device | Notes |
|---|---|---|---|---|---|---|---|---|
| EUDI reference wallet | EU (reference implementation) | OID4VP 1.0 FINAL + HAIP 1.0 FINAL profile | 2026-07-28 | yes | yes | yes | yes | Runs against the OpenID Foundation OID4VP + HAIP conformance harness (alpha). Both wire formats accepted end-to-end: SD-JWT VC + KB-JWT with encrypted direct_post.jwt responses (ECDH-ES + A128GCM / A256GCM), AND ISO 18013-5 mDoc device-responses with COSE_Sign1 IssuerAuth + DeviceAuth, SessionTranscript hashing, and MSO digest re-computation. Both formats advertised in /.well-known/openid-configuration under vp_formats_supported. |
| Aloaha Web Wallet | Malta (Aloaha Limited) | 2026-07-28 | 2026-07-28 | yes | yes | yes | yes | Our own browser holder. Not a government-notified EUDI Wallet. Designed for LoA-Substantial-targeted use cases subject to a formal conformity assessment. Both wire formats supported holder-side: dependency-free CBOR + COSE_Sign1 + mDoc primitives ship as js/web-wallet-cbor.min.js, web-wallet-mdoc.min.js, web-wallet-mdoc-devresp.min.js and web-wallet-mdoc-wallet.min.js, matched byte-for-byte on the server by App_Code/CborUtil.cs + CoseSign1Util.cs + MDocIssuer.cs + MDocVerifier.cs. The holder generates a fresh non-extractable P-256 device key per credential (per HAIP §5.5), imports mso_mdoc credentials via OID4VCI with a CWT/JWT proof-of-possession carrying the mDoc device pubkey, persists them in IndexedDB, and produces DeviceResponse presentations signed with COSE_Sign1 over an OID4VP SessionTranscript. See the explainer. |
Additional rows will be published for other Member-State wallets as tests are executed and evidence bundles are prepared. The verifier speaks the standards; the empty cells are a matter of published test scope, not spec support.
See also: HAIP verifier certification · EU Wallet ecosystem cookbook · Glossary · All cookbooks.