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.

European Digital Identity Wallet · German credentials

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`

The Versicherungskarte here is the EU EHIC, not the German eGK. The elektronische Gesundheitskarte (eGK) issued by the Krankenkassen under gematik is a national scheme outside EUDI ARF scope. The credential that will land in an EU wallet is the cross-border European Health Insurance Card, currently drafted by the DC4EU Large Scale Pilot in cooperation with the CEN WS/eEHIC working group. If you need the eGK specifically, that is a separate integration path via gematik connectors.

Detail per credential.

Personalausweis → PID Ratified

Person Identification Data, the identity anchor of every EUDI Wallet.

RulebookEUDI ARF Annex 3.01, PID Rulebook v1.5 (Jan 2026)

Legal basiseIDAS 2 · Reg. (EU) 2024/1183 · CIR 2024/2977

SD-JWT VC typeeu.europa.ec.eudi.pid.1

mdoc doctypeeu.europa.ec.eudi.pid.1

Mandatory: family_name, given_name, birth_date · Common: nationality, birth_place, resident_address, personal_administrative_number, issuing_country, issuing_authority, expiry_date, portrait

CodeB has issued PID in both formats since the round2-arf-vct sprint (July 2026). No new work needed — the Personalausweis is the ratified backbone that lets a wallet prove its holder's legal identity to any EU relying party. Bundesdruckerei is the notified PID Provider prototype in Germany; the SPRIND funKe project shaped the German profile.

Fuehrerschein → mDL Ratified

Mobile Driving Licence per ISO/IEC 18013-5.

RulebookISO/IEC 18013-5 · ARF Annex 3.02

Legal basis4th Driving Licence Regulation COM(2023)127 · eIDAS 2

Normative formatmdoc · org.iso.18013.5.1.mDL

SD-JWT VC (interop)eu.europa.ec.eudi.mdl.1

Mandatory: family_name, given_name, birth_date, issue_date, expiry_date, issuing_country, document_number, driving_privileges · Common: issuing_authority, un_distinguishing_sign, portrait

CodeB emits mDL both as an SD-JWT VC (developer convenience) and as an mdoc (normative). Because ISO 18013-5 is normative for driving-privilege verification, verifiers that gate access to hire cars or rental scooters SHOULD request the mdoc form. Kraftfahrt-Bundesamt (KBA) is the expected DE issuer; POTENTIAL Large Scale Pilot has yet to publish the DE issuance profile.

Fahrzeugschein → mVRC Draft

Zulassungsbescheinigung Teil I — the vehicle registration document.

Working specISO/IEC DIS 7367-1

EU pilotAPTITUDE Large Scale Pilot (mVRC track)

Working URNurn:eu.europa.ec.eudi:mvrc:1-draft

DE issuer (expected)Kraftfahrt-Bundesamt (KBA)

Mandatory (working): registration_number, vehicle_identification_number (VIN), date_first_registration, vehicle_holder, vehicle_category_code · Common: make, model, mass_in_service, permitted_max_mass, issuing_country, issuing_authority

The identifier ends in -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

European Health Insurance Card — cross-border, not the national eGK.

Working specDC4EU LSP working draft, CEN WS/eEHIC

Working URNurn:eu.europa.ec.eudi:ehic:1-draft

DE issuer (expected)DVKA (via EESSI network)

Not thisgematik eGK — separate national scheme

Mandatory (working): family_name, given_name, birth_date, personal_administrative_number, issuing_institution_id, issuing_country, document_number, expiry_date

Same -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 corresponding vct string. The issuer returns an openid-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, in App_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 Attestation Rulebooks Catalog — github.com/eu-digital-identity-wallet/eudi-doc-attestation-rulebooks-catalog
• 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.

Talk about your DE deployment Back to Web Wallet overview