Personalausweis, Fuehrerschein, Fahrzeugschein and Versicherungskarte in the European Digital Identity Wallet.
The four documents most Germans carry every day map to four different EUDI Wallet attestations at very different maturity levels. This page is the honest status — what is ratified in the EUDI ARF today, what is still in Large Scale Pilots, and what CodeB actually issues and can verify.
All four are wired into the CodeB self-hosted wallet catalogue. The two ratified types (PID, mDL) use their normative identifiers; the two draft types (mVRC, EHIC) use working identifiers with a -draft URN suffix so the label can be renamed when the ARF ratifies them, without silently breaking downstream consumers.
Status matrix.
| German document | EUDI attestation | ARF status | Format | Identifier (SD-JWT VC / mdoc doctype) |
|---|---|---|---|---|
| Personalausweis | PID | Ratified · ARF Annex 3.01 | SD-JWT VC + mdoc | eu.europa.ec.eudi.pid.1 |
| Fuehrerschein | mDL | Ratified · ISO/IEC 18013-5, ARF Annex 3.02 | mdoc (normative), SD-JWT VC (interop only) | org.iso.18013.5.1.mDL |
| Fahrzeugschein | mVRC | Draft · ISO/IEC DIS 7367-1, APTITUDE LSP | mdoc (planned) | working urn:eu.europa.ec.eudi:mvrc:1-draft |
| Versicherungskarte | EHIC | Draft · DC4EU LSP, CEN WS/eEHIC | SD-JWT VC (planned) | working urn:eu.europa.ec.eudi:ehic:1-draft |
Detail per credential.
Personalausweis → PID Ratified
eu.europa.ec.eudi.pid.1eu.europa.ec.eudi.pid.1Fuehrerschein → mDL Ratified
org.iso.18013.5.1.mDLeu.europa.ec.eudi.mdl.1Fahrzeugschein → mVRC Draft
urn:eu.europa.ec.eudi:mvrc:1-draft-draft so that when ISO/IEC 7367-1 ratifies and the ARF publishes an mVRC rulebook, the URN can be renamed via a single retired-VCT shim in MapRetiredVctToArfSuccessor without breaking prior issuances. Use only for pilots and interop testing until then.Versicherungskarte → EHIC Draft
urn:eu.europa.ec.eudi:ehic:1-draft-draft discipline as mVRC. Two source-of-truth channels on the user record are accepted: top-level personal_administrative_number (typical German KVNR), or nested insurance.{document_number, issuing_institution_id, ...} for tenants federating from HL7-FHIR bridges.Operating this on your own tenant.
All four credentials are already in the issuer catalogue on any tenant running the current vci.ashx build. To mint one for a member:
- Ensure the user record on your OIDC IdP has the source fields for that credential (see the attribute lists per card above). Missing fields are logged by tag:
[VCI-PID-INCOMPLETE],[VCI-MDL-MINT],[VCI-MVRC-MINT],[VCI-EHIC-MINT]. - From the admin-side offer builder (POST
/vci.ashx?action=create-offer), pass the correspondingvctstring. The issuer returns anopenid-credential-offer://deep link. - The holder scans the deep link in the CodeB Web Wallet or any conformant EUDI wallet. The credential lands in the wallet as SD-JWT VC (or mdoc for mDL/mVRC when we ship that path).
- A relying party requests it via the OpenID4VP verifier at
/oidc.ashx?action=vp-start. Trusted-issuer AKIs are per-tenant, inApp_Data/<tenant>/trust/dcql-trusted-akis.txt.
Verified attributes flow into the standard OIDC id_token via MergeVcClaims (the vc claim block plus the standard-claim lift for profile / email scopes). Per-OIDC-client filtering via App_Data/<tenant>/oidc-clients/<client_id>/wallet-claim-allowlist.json lets you gate which VC-derived claims each downstream app is allowed to see.
Authoritative references.
• EUDI ARF main — github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework
• PID rulebook (Annex 3.01) — pid-rulebook.md
• mDL rulebook (Annex 3.02) — mdl-rulebook.md
• CIR (EU) 2024/2977 (PID + EAA) — EUR-Lex
• APTITUDE LSP (mVRC track) — aptitude.digital-identity-wallet.eu
• DC4EU LSP (EHIC track) — dc4eu.eu
• ISO/IEC 18013-5 (mDL) — iso.org/standard/69084.html
• ISO/IEC DIS 7367-1 (mVRC) — iso.org/standard/85555.html
• SPRIND funKe (DE PID) — sprind.org · EUDI Wallet Prototypes
Want the mDL as mdoc, or a DE-tenant-issued PID?
The SD-JWT VC path is live today. If you need the mdoc-normative mDL wire format for driving-privilege verification, or a Bundesdruckerei / KBA source-federation, tell us your target relying-parties and country.
Frequently asked questions
Is the German Personalausweis supported in the European Digital Identity Wallet today?
Yes. The Personalausweis maps to PID (Person Identification Data), a ratified attestation in the EUDI ARF Attestation Rulebooks catalog. It is issued in both mdoc format (doctype eu.europa.ec.eudi.pid.1) and SD-JWT VC (vct eu.europa.ec.eudi.pid.1).
What about the Fuehrerschein?
The mobile Driving Licence (mDL) is ratified under ISO/IEC 18013-5 and EUDI ARF Annex 3.02. It is mdoc-only in the normative profile; SD-JWT VC form is offered by our issuer for interop testing but is non-normative for driving-privilege verification.
Is the Fahrzeugschein already standardised?
Not yet. The mobile Vehicle Registration Certificate (mVRC) is in draft under ISO/IEC DIS 7367-1, with the APTITUDE Large Scale Pilot working out the EU-wide profile. CodeB supports it under a -draft URN so the identifier can be renamed once ratified.
Does the Versicherungskarte mean the eGK?
No. The German electronic Health Card (eGK, gematik) is a national scheme outside EUDI ARF scope. The EUDI EHIC (European Health Insurance Card) EAA is a separate credential currently in draft under the DC4EU LSP and the CEN WS/eEHIC working group -- that is what our wallet targets.