EUDI Wallet and digital credentials, explained
Each guide takes one topic from the European digital identity rules and answers the same three questions: what it is, why it matters, and who has to do what. They are meant to be read on their own, in any order.
They are written for the people who decide what an organisation builds or buys: product owners, compliance officers and the managers who have to sign off on a wallet programme. No specifications to read first.
EUDI Wallet and eIDAS 2.0
eIDAS 2.0 explained: what it means for your business
What eIDAS 2.0 means for your business: the timeline, who must accept the EUDI Wallet, and a checklist to prepare.
Read the explainerRelying party explained
What it means to be the organisation asking for data, who has to accept the EUDI Wallet and from when, and what connecting to it actually takes.
Read the explainerThe EUDI Wallet for HR and recruitment: what actually changes
What the EUDI Wallet changes for hiring: candidate identity, right to work, diplomas, screening, agency mandates, and what it leaves untouched.
Read the explainerTS11 explained
The two European catalogues that record which attributes exist and which rules an attestation has to follow, and what each of them means for issuers and verifiers.
Read the explainerWallet Unit Attestation explained
How a wallet proves to an issuer that it is genuine and that its keys are stored securely, before any credential is handed over to it.
Read the explainerBusiness wallets
The European Business Wallet explained
What the European Business Wallet is, what the EU proposal asks public bodies to accept, and how your company can prepare for it today.
Read the explainerDigital Product Passport explained
How a Digital Product Passport works: the data carrier, the unique identifier, what the passport holds, who hosts it and how its claims are verified.
Read the explainerCredentials and protocols
DCQL explained
How a verifier asks a wallet for exactly the data it needs and nothing more, without building a separate integration for every issuer.
Read the explainerDID explained
What a Decentralized Identifier is made of, what resolving one gives you, how did:web, did:webvh and did:key differ, and what a DID on its own does not prove.
Read the explainerdid:web explained
How did:web turns a domain you already own into a DID, how the identifier maps to a URL, what it secures, and where its limits start.
Read the explainerDigital Credentials API explained
How a website asks your wallet for a credential straight through the browser, with no QR code to scan on your phone and no jump out to another app.
Read the explainerHolder binding explained
How a credential is tied to a key only its holder controls, why that makes a stolen copy worthless, and what holder binding still does not prove.
Read the explainerJSON-LD explained
What JSON-LD adds to plain JSON, how a @context gives every field one meaning, and where verifiable credentials use it.
Read the explainermdoc explained
What an mdoc is, what is inside one, how it is presented in person and online, and why the EUDI Wallet carries it next to SD-JWT VC.
Read the explainerOpenID Federation explained
How issuers, verifiers and wallet providers check each other through one shared trust anchor, instead of signing an agreement with every counterparty.
Read the explainerOpenID4VCI issuance explained
The full path a credential travels, from the moment you offer it to the moment it sits in someone’s wallet, and the points where an issuance can fail.
Read the explainerSame-device and cross-device flows explained
How a wallet and a website reach each other on one phone or across two, why a QR code changes the security picture, and when your service needs both.
Read the explainerStatus List revocation explained
How a verifier checks that a credential is still valid, without revealing to the issuer which credential it just looked up.
Read the explainerWhat are verifiable credentials?
Verifiable credentials explained: what they are, what the issuer, holder and verifier do, and why they beat PDFs and manual checks.
Read the explainerTechnical deep dive
These guides stop where the implementation work starts. The developer documentation covers the interfaces, the credential formats and the integration steps behind every topic on this page.
Read the technical documentationNot sure which guide applies to you?
Tell us what your organisation wants to issue or verify. We will point you at the right guide and walk you through what it means in practice.
Talk to our team