> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-3-comparative-analysis-of-regulations/digital-credentials.md). # Digital Credentials Standard comparative entry. Why ‘digital credentials’ is a technical abstraction rather than a legal category, the W3C Verifiable Credentials layer, and educational qualifications as the core educatio {% hint style="info" %} **A note on how this category should be read.** Unlike the other nine categories in this Primer — each of which corresponds to a recognisable body of law and regulatory practice that preceded digital government — the category of digital credentials is a retrospective technical abstraction. The term 'credential' as a common category emerged primarily from the digital identity and IT architecture communities as a way to describe what government documents have in common technically: they assert something about a person to a third party. But a driver's licence, a medical degree, a professional certification, a birth certificate, and an export licence have nothing else in common — they are governed by entirely different laws, issued by entirely different institutions, for entirely different purposes, under entirely different business processes. This profile explains why the concept is used despite this heterogeneity, what it refers to precisely when used carefully, and what the actual regulatory questions are — which turn out to be narrower and more specific than the general framing implies. {% endhint %} ## 1. What This Category Is — and Is Not ### 1.1 The problem with 'credentials' as a regulatory category Before proceeding to comparative analysis, it is worth being precise about what this regulatory category actually covers and where the concept comes from — because the framing in much of the digital government literature is an IT industry perspective that can mislead policymakers with legal or political science backgrounds. In administrative and legal terms, the documents that digital government literature groups together as 'credentials' are categorically different things. A birth certificate is a civil registry record of a fact — it belongs squarely to the population registry domain, not to any 'credentials' category. A driver's licence is a regulatory permission granted by a road authority after a skills test, governed by road safety law. An export licence is a conditional administrative authorisation by a trade ministry. A medical degree is an attestation of academic achievement by a higher education institution, recognised through a separate professional licensing regime. A professional certification is a competency confirmation by a regulated body. Each of these has its own legal basis, its own issuing authority, its own conditions and processes, and its own recognition regime. What these documents share — and what makes the technical concept of 'credentials' meaningful — is a single functional property: they assert something about a person or organisation to a third party who needs to verify that assertion. Before digitalisation, each was a physical document whose authenticity was verified by examining it manually or by contacting the issuing institution. Digitalisation raises a common question for all of them: how can an assertion that was previously made on paper be made digitally in a way that is equally trustworthy, portable, and verifiable? The concept of digital credentials as a regulatory category therefore emerged from the digitisation question, not from any pre-existing legal or administrative category. IT architects and digital identity specialists noticed that all these documents had the same technical structure — issuer, holder, claim, verification — and developed common technical frameworks for handling them digitally. The W3C Verifiable Credentials standard is the most significant product of this observation: a common technical architecture for issuing, holding, and verifying assertions of any kind in a cryptographically secure, machine-readable format. This is a genuine technical contribution. It does not mean that the underlying governance of any specific document type has changed — a driver's licence is still governed by road safety law — but it provides a common transport layer that cuts across sectoral boundaries. ### 1.2 What this category actually covers — three distinct questions Once the conceptual heterogeneity is acknowledged, the regulatory questions in this category become clearer and more specific. There are three distinct questions, and they require different regulatory instruments and different governance approaches. The first is the **legal standing of digital documents**: does a digital version of a document carry the same legal weight as the physical original? This is essentially the electronic signatures and digital legal validity question that the eIDAS framework and its national equivalents address. It is primarily a question for the foundational digital government legal framework, not for specific credential governance. A digital copy of a driving licence with a qualified electronic seal from the issuing authority should be legally equivalent to the physical one — but establishing this equivalence requires explicit legislative provision in the road traffic law, not a general 'digital credentials law.' The governance sits in each sector's specific legislation. The second is the **technical interoperability infrastructure**: can digitally issued documents from different sectoral domains be presented and verified using common technical infrastructure, so that a person does not need separate apps or verification processes for each document type? This is what the eIDAS 2 European Digital Identity Wallet primarily addresses — not a 'credentials governance' question but a digital identity architecture question about how verified attributes and document copies are stored, carried, and presented. The wallet is the container; the governance of what goes into it remains in the sector-specific legal frameworks. This is correctly understood as part of [Category 2 (Digital Identity)](/experience-digital-transformation/regulations/component-3-comparative-analysis-of-regulations/digital-identity-and-trust-services-global-landscape-and-best-practice.md) rather than as a separate category, and the Primer's Digital Identity profile covers it. The third is specific to **educational qualifications**: how are formal educational achievements — degrees, diplomas, certifications, micro-credentials — issued, verified, and recognised across institutional and national boundaries? This is where there is a genuinely developed and education-specific regulatory and technical framework, distinct from both the foundational legal standing question and the digital wallet question. Educational qualification recognition has an international treaty framework (the Lisbon Recognition Convention), a global network of verification bodies (the ENIC/NARIC centres), and now a specific European digital infrastructure (the Europass European Digital Credentials for Learning) that makes electronic qualification verification practical at scale. This is the dimension of the category that the Primer addresses in most depth, because it is directly relevant to the education sector demonstration. **Why this category is retained despite the conceptual complexity.** The ten categories in this Primer's landscape map reflect how digital transformation regulatory frameworks are organised in practice, not how a legal theorist would organise them. Governments and international organisations do increasingly discuss 'digital credentials' as a common regulatory challenge, and the technical standards work (W3C VC, Open Badges) has created practical regulatory questions around adoption and recognition that policymakers need to address. The category is therefore retained, but with the understanding that its content is primarily the technical interoperability infrastructure and the educational qualifications recognition framework — the two dimensions where there is genuinely shared regulatory substance across document types — rather than the governance of any specific document category, which remains in its sectoral home. ## 2. The Technical Interoperability Infrastructure ### 2.1 W3C Verifiable Credentials — the common technical layer The W3C Verifiable Credentials Data Model 2.0, published as a full W3C Web Standard in May 2025, provides the common technical architecture that makes it possible to issue, hold, and verify any type of assertion in a cryptographically secure, machine-readable, interoperable format. Its three-party model — issuer, holder, verifier — maps the general structure of document verification: an institution issues an assertion to a person, who can present it to any party who wants to verify it. The standard defines how assertions are structured, how they are cryptographically secured, and how selective disclosure works, allowing a person to share only the attributes relevant to a specific transaction without exposing the full document. The standard's significance is not that it creates a new regulatory category but that it provides common technical plumbing that any sectoral credential can use. A road authority issuing digital driving licences, a university issuing digital degrees, and a professional body issuing digital certifications can all use W3C VC as the format — and a verifier can verify all of them using the same technical approach, regardless of the underlying sectoral governance. This technical commonality is the basis for the 'digital credentials' framing without changing the fact that the governance of each remains in its sectoral home. ### 2.2 The trust registry question Technical cryptographic signing is necessary but not sufficient for verification trust. A verifier receiving a W3C VC-formatted assertion needs to know that the public key used to sign it actually belongs to the claimed issuing institution — not a fraudulent actor presenting forged assertions. This is the trust infrastructure problem common to all digital document types, and it requires an institutional solution: a registry of public keys belonging to authorised issuers, operated by an authority whose own trustworthiness is established. eIDAS 2's qualified trust service framework provides this infrastructure for EU member states: each member state maintains a national trusted list of qualified trust service providers, and a qualified electronic seal issued by a registered provider has automatic legal recognition across the EU. For developing countries outside the EU, a national registry of authorised document issuers — each with a registered public key, maintained by a designated public authority, accessible through an API — provides the equivalent trust infrastructure at national level. The choice of whether to build this nationally, connect to a regional framework, or rely on the EU framework for internationally recognised documents is a governance design choice that should be made explicitly. ## 3. Educational Qualifications — the Core Education Sector Case ### 3.1 Why educational qualifications are the most developed case Of all the document types that digital credentials literature addresses, educational qualifications have the most developed international recognition framework and the most directly relevant regulatory infrastructure for this Primer's purposes. The reasons are practical: a driver's licence needs to be recognised in other countries only in limited circumstances, and the recognition framework is primarily bilateral. An export licence is by definition country-specific. But an educational qualification — a degree, a professional certification, a vocational qualification — is something its holder carries throughout a working life and needs recognised by employers, further education institutions, and professional licensing bodies in multiple countries over decades. The international portability question is central to the value of the document in a way it is not for most other document types. The Lisbon Recognition Convention (1997), administered jointly by the Council of Europe and UNESCO, is the international treaty framework establishing the obligation to recognise qualifications from other states parties. The ENIC/NARIC network — national credential evaluation centres in each state party — provides the human verification infrastructure for recognition decisions. These pre-digital frameworks remain the legal foundation for international qualification recognition even as the technical infrastructure for verification becomes digital. ### 3.2 European Digital Credentials for Learning — the most developed operational example The EU's European Digital Credentials for Learning (EDC) infrastructure, operated through the Europass platform, is the most operationally developed digital qualification system currently functioning at scale. Any educational institution in participating countries can issue qualifications in a standardised, multilingual, W3C VC-aligned format based on the European Learning Model — itself aligned with the European Qualifications Framework. The credentials carry qualified electronic seals under eIDAS, are stored in the learner's Europass digital wallet, and are verifiable across the EU in seconds without any contact with the issuing institution. The EDC infrastructure's significance is that it demonstrates what functional digital qualification issuance and verification looks like end-to-end. It required alignment of: the eIDAS qualified trust service framework (for the signing infrastructure), the European Qualifications Framework (for the content schema), the Europass wallet (for storage and presentation), and specific institutional participation (universities and other institutions must register and issue through the system). None of these elements alone was sufficient — all four needed to be in place simultaneously. For developing countries designing digital qualification systems, the EDC provides the most complete operational reference available. ### 3.3 Micro-credentials — the recognition challenge Micro-credentials — short, focused learning programmes certifying specific skills or competencies — have become a significant policy priority as labour markets increasingly require skills-based rather than qualification-based hiring. UNESCO's Global Convention on the Recognition of Qualifications concerning Higher Education (2019) and the EU's European approach to micro-credentials both reflect recognition that learning increasingly happens in formats that traditional qualifications frameworks do not adequately capture. The digital credentials technical infrastructure is the same for micro-credentials as for traditional qualifications — W3C VC, institutional trust registry, wallet presentation. The recognition challenge is different: a traditional degree from a recognised university has established mechanisms for international recognition that micro-credentials lack. A micro-credential's value depends heavily on whether the issuing institution and the competency framework are trusted by the verifier, and there is no equivalent of the ENIC/NARIC network for micro-credential recognition. For developing countries, starting with formal qualifications and extending to micro-credentials as the recognition infrastructure matures is the appropriate sequencing. ## 4. Key Published Regulations and References | Jurisdiction / Source | Instrument | Year | Scope / status | Key features and Primer relevance | | -------------------------- | --------------------------------------------------------------------------------------------- | ------------------ | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | W3C / Global | Verifiable Credentials Data Model 2.0 (W3C Recommendation) | May 2025 | Global open standard | The common technical layer. Three-party model: issuer, holder, verifier. Cryptographically secure, privacy-preserving, interoperable. Applicable to any document type. Does not replace sectoral governance — provides common technical format. | | European Union | eIDAS 2 (Regulation EU 2024/1183); European Digital Credentials for Learning (EDC) / Europass | 2024 / operational | EU binding; EDC open to non-EU | eIDAS 2: qualified trust service framework providing the signing infrastructure. EUDI Wallet: container for documents — primarily a digital identity architecture instrument. EDC: most complete operational digital qualification system. W3C VC-aligned, multilingual, EQF-linked. | | Council of Europe / UNESCO | Lisbon Recognition Convention; ENIC/NARIC network | 1997 / ongoing | International treaty; 55+ state parties | Foundational international framework for mutual recognition of qualifications. ENIC/NARIC: national credential evaluation bodies. Pre-digital framework that remains the legal foundation for international recognition regardless of digital issuance format. | | 1EdTech / Global | Open Badges 3.0; Comprehensive Learner Record (CLR) Standard 2.0 | 2022 | Global; education sector standards | Education-specific implementation of W3C VC. Open Badges: digital recognition for achievements and micro-credentials. CLR: fuller learner journey record. Most widely adopted education credentials standards. | | UNESCO / Global | Global Convention on Recognition of Qualifications in Higher Education | 2019 | International; 50+ state parties | Updated Lisbon framework. Addresses digital qualifications and portability explicitly. Countries issuing digital qualifications should ratify to ensure international portability. | | GovStack / Global | Digital Credentials Building Block Specification | 2023 / ongoing | Global; developing countries focus | Technology-neutral specification for government digital document issuance. Open standards first. Starting point for developing countries designing national systems without vendor lock-in. | ## 5. Key Regulatory Considerations ### 5.1 What developing countries actually need to do Given the conceptual clarification in Section 1, the practical regulatory agenda for developing countries in this area is more specific and more achievable than a 'digital credentials framework' framing implies. Three things are actually needed. First, **legal standing provisions for digital documents in each relevant sectoral law**. The question is not whether digital documents in general have legal standing — it is whether a digital university degree is legally equivalent to a paper one for all the purposes for which paper degrees are used, whether a digital professional licence is valid for practice purposes, and so on. Each sectoral law needs an explicit provision establishing this equivalence. This is incremental legislative work rather than a new horizontal framework. Second, **a national trust registry** — a public register of authorised document-issuing institutions and their cryptographic public keys — that enables verification without contacting the issuing institution. This infrastructure is best built as an extension of the national digital identity framework rather than as a separate system, because the same trust architecture serves all document types. The registry should be governed by the digital government authority with input from the relevant sectoral regulators for their specific institution lists. Third, and specifically for educational qualifications, **accession to the Lisbon Recognition Convention and UNESCO's 2019 Global Convention**, and establishment or designation of a national ENIC/NARIC centre. These international recognition mechanisms are the governance layer that makes digital qualification portability meaningful beyond the technical verification capability. ### 5.2 What not to do — common mistakes {% hint style="warning" %} * Do not create a horizontal 'digital credentials law' attempting to govern all document types in a single instrument. The governance of each document type belongs in its sectoral law. A horizontal instrument creates confusion about which law governs and typically fails to address the specific requirements of any sector adequately. * Do not conflate the digital wallet architecture with credentials governance. The wallet is a container for documents whose governance remains in sectoral law. Design the wallet infrastructure as part of the digital identity system, not as a separate credentials framework. * Do not build proprietary national credentials platforms. Use open standards (W3C VC, Open Badges 3.0 for education) from the outset. Proprietary formats create the lock-in and non-portability that defeat the primary purpose of digital document issuance. * Do not start with micro-credentials. The recognition infrastructure for micro-credentials is immature internationally. Build the digital issuance and verification infrastructure for formal qualifications first, and extend to micro-credentials as institutional capacity and international recognition frameworks develop. {% endhint %} ## 6. Education Sector Implications ### 6.1 Digital educational qualifications — the primary use case Educational qualifications are the document type where the case for digital issuance is strongest and the regulatory framework is most developed. The portability value is high — qualifications travel with people throughout their careers — the verification burden is significant for institutions currently handling requests manually, and the fraud risk is real and growing as AI-generated fake credentials become more convincing. Digital qualifications with proper cryptographic signing are practically impossible to forge if the trust infrastructure is functioning correctly, which is a qualitative security improvement over paper documents. For developing countries, the human capital mobility argument is particularly important. A nurse trained in Ghana, an engineer from India seeking employment in the Gulf, a teacher from the Philippines working in Europe — all face slow and expensive qualification recognition processes that are barriers to both individual mobility and efficient cross-border deployment of skills. Digital qualifications do not eliminate recognition barriers, which require policy agreements, but they remove the verification friction that currently makes recognition so burdensome. This benefit requires the Lisbon Convention and ENIC/NARIC recognition infrastructure to be in place alongside the technical verification capability. ### 6.2 The learner registry and credential issuance A national learner registry that reliably tracks learners through the education system is the foundational infrastructure for authoritative digital qualification issuance. A digital degree is only as trustworthy as the underlying record that the person named in it actually completed the programme of study claimed. If the learner registry is incomplete, inaccurate, or not linked to the graduation records of educational institutions, digital qualifications issued from it inherit these weaknesses. The sequencing recommendation from [Section 5.4 of Component 3 Category 2 (Digital Identity)](/experience-digital-transformation/regulations/component-3-comparative-analysis-of-regulations/digital-identity-and-trust-services-regulatory-reference-and-the-education-sector.md) applies here: the learner registry must be built on a reliable civil registry and digital identity foundation before digital qualification issuance can be trustworthy at national scale. {% hint style="warning" %} **Editorial note.** The source draft for this profile cited “Section 5.2 of Component 3 Category 5” for this sequencing recommendation. Category 5 (Interoperability and Digital Government) has no such §5.2 — its Section 5 is a published-regulations reference table. The sequencing recommendation being referenced is actually Section 5.4 of Category 2 (Digital Identity and Trust Services), “The sequencing recommendation for education sector digital identity.” The citation and link above have been corrected accordingly during the build of this Knowledge Product. {% endhint %} ### 6.3 AI-generated fraud and the verification imperative The growing ease with which convincing fake credentials can be generated using AI tools makes the technical verification infrastructure more rather than less urgent. A PDF certificate, however well-designed, can be generated by anyone with access to image editing software. A W3C VC-formatted credential with a qualified electronic seal from a registered institution cannot be forged without access to the institution's private key — which, if properly managed, is computationally infeasible to compromise. For employers, universities, and professional licensing bodies receiving credentials from developing countries whose paper credentials are already frequently questioned, digital verification provides a qualitative assurance that the credential is what it claims to be. This is not primarily a technical argument but a trust and recognition argument: digital verification infrastructure makes developing country educational qualifications more credible internationally. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/regulations/component-3-comparative-analysis-of-regulations/digital-credentials.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.