Guide
A digital credential has to answer two questions: does it really come from the issuer, and does it belong to the person presenting it? The procedures used in Germany answer them in different ways.
Building block 1: digital signatures
Almost all credentials rely on public-key cryptography. The issuer signs the data with a private key; anyone checking it uses the matching public key. If a single character changes, the signature no longer matches. Which public keys are trustworthy is published in trust lists – for the EU COVID certificate, these came from the national authorities via an EU gateway.
Building block 2: QR codes – the COVID certificate as an example
The EU COVID certificate packed its data into a compact signed structure (CBOR with a COSE signature), compressed it and encoded it as a QR code. Checking worked offline and no server learned who was checked where. The downside: whoever scanned the code saw everything in it – name, date of birth, vaccine and date.
Building block 3: the chip in the ID card
- PACE ensures that only a reader with your PIN can open an encrypted connection to the chip.
- Authorisation certificates define which service may read which fields. An age check does not get your address.
- Chip and terminal authentication make sure both the chip and the service are genuine.
- A pseudonym function lets a service recognise you again without learning your name.
The procedure is considered very secure; its weakness used to be usability. With NFC smartphones and the AusweisApp it has become much easier.
Building block 4: the telematics infrastructure
The electronic patient record and e-prescriptions run on the telematics infrastructure (TI), a closed network for practices, hospitals, pharmacies and insurers specified by gematik. Patient record data is stored encrypted on servers in Germany; access requires the health card in the practice or authentication in the insurer’s app.
Building block 5: standards of the EU wallet
| Standard | Used for | Benefit |
|---|---|---|
| ISO/IEC 18013-5 (mdoc) | Driving licence and ID data in person | Transfer via QR code or NFC, also offline |
| SD-JWT VC | Credentials online | Selective disclosure of single attributes |
| OpenID4VCI / OpenID4VP | Issuing and presenting | Common flows between wallet, issuers and verifiers |
| Relying party registration | Protection against over-asking | Verifiers must declare which data they may request |
Stored locally or centrally?
One principle of the former CovPass app is still the benchmark: credentials live on your own device, not in a central database. The EU wallet follows it. The patient record is deliberately central, because practices need access even when your phone is off.
German version: Technische Details.