What is Verifiable Digital Credentials (VDCs)

Verifiable Digital Credentials (VDCs) are digitally issued credentials containing information about a person, organization or entity that can be cryptographically verified. They provide a way to prove identity, qualifications, eligibility or other attributes without relying on physical documents or manually checking digital copies. [1][2]

Unlike traditional identification documents, VDCs are issued with cryptographic protections that allow organizations to verify their origin and integrity. For example, a government-issued digital identity credential can contain information about an individual's identity or age, with a digital signature that enables an organization to verify that the information was issued by the relevant authority and has not been altered.

Examples include mobile driver's licenses (mDLs), digital identity cards, educational qualifications and professional certifications. VDCs can be stored in digital wallets and presented to organizations online or in person, allowing information to be verified using cryptographic methods. [1][3]

Unlike a scanned ID or PDF certificate, a VDC contains structured information protected against undetected modification. Altering information covered by its cryptographic protections causes the relevant integrity check to fail. Depending on the credential format, individuals may also be able to share only the information required for a particular interaction rather than disclosing the entire credential. [1]

This page focuses on credentials in the ISO mdoc format, defined in ISO/IEC 18013-5 for in-person presentation and extended to online presentation by ISO/IEC TS 18013-7. Mobile driver's licenses (mDLs) and other government-issued photo identity credentials are commonly issued in this format. Where the article describes a capability as required, such as selective disclosure or device binding, the requirement comes from ISO mdoc. Other formats may make the same capability optional, implement it differently or omit it. SD-JWT VC, for example, supports selective disclosure but makes key binding optional, and in the W3C Verifiable Credentials Data Model both depend on the securing mechanism.

Verifiable Digital Credentials at a glance

Verifiable Digital Credentials (VDCs)
Definition
Digitally issued credentials containing claims or attributes that can be cryptographically verified.
Primary purpose
Enable trusted verification of identity, qualifications, eligibility or other information.
How it works
An issuer creates a protected credential, a holder receives it, and a verifier checks its authenticity when presented.
Key participants
Issuer, holder and verifier.
Common examples
Mobile driver's licenses, digital identity cards, educational certificates and proof-of-age credentials.
Storage
Commonly stored in digital wallets, although other architectures are possible.
Privacy capabilities
Selective disclosure, data minimization and privacy-preserving proofs, depending on the implementation.
Verification methods
Cryptographic signatures or proofs, issuer trust checks, credential status and holder binding where applicable.
Relevant standards
W3C Verifiable Credentials Data Model v2.0, OpenID4VCI, OpenID4VP, ISO/IEC 18013-5, ISO/IEC TS 18013-7, W3C Digital Credentials API, SD-JWT VC and credential status mechanisms.

‍

Why are Verifiable Digital Credentials important?

Traditional identity verification often requires individuals to present physical documents, upload images of identification or repeatedly provide personal information to different organizations.

For example, an online identity verification process may require a customer to photograph their driver's license, complete a facial comparison and submit the information for automated or manual review. These processes can introduce additional steps for customers and require organizations to collect and process more personal information than is necessary for a particular interaction.

Verifiable Digital Credentials provide an alternative by allowing trusted issuers to create digitally verifiable information that can be presented and checked electronically. [1][2]

Rather than relying on an image of a physical document, an organization can verify the cryptographically protected information contained in a credential. This can reduce reliance on manual document inspection and enable more targeted information sharing.

For example, someone applying for a financial service may need to verify their identity, while a person accessing an age-restricted service may only need to prove they meet a minimum age requirement.

VDCs can support both scenarios without necessarily requiring the individual to share a complete identity document.

The main benefits include:

  • Cryptographic verification: Organizations can check whether protected credential information has been altered and verify the authenticity of its issuer.
  • Greater privacy: Selective disclosure can allow individuals to share specific attributes without revealing unnecessary personal information.
  • Reusable credentials: A credential may be presented to multiple compatible organizations without repeating the entire issuance process.
  • Digital and in-person verification: Supported credentials can be presented through online services or at physical locations.
  • Reduced manual processing: Digital verification can reduce the need to inspect physical documents or manually validate document images. [1][3][4]

These benefits depend on the credential format, issuer trust, digital wallet capabilities and verification requirements.

How do Verifiable Digital Credentials work?

VDCs generally operate through a model involving three participants: the issuer, holder and verifier.

The World Wide Web Consortium (W3C) describes this model in its Verifiable Credentials Data Model, which defines how credentials can be created, exchanged and verified. [1]

1. The issuer creates a credential

The issuer is an organization or authority that makes claims about a person, organization or other subject. For example, a government authority may issue a mobile driver's license, while a university may issue a digital qualification. The credential contains relevant attributes and is protected using cryptographic mechanisms, such as digital signatures, that allow its integrity and origin to be verified.

2. The holder receives the credential

The holder receives the credential, often through a compatible digital wallet on their smartphone. The wallet can store credentials, manage associated cryptographic keys and enable the holder to respond to verification requests. OpenID for Verifiable Credential Issuance (OpenID4VCI) defines a standardized protocol for issuing credentials to wallets. [3]

3. The verifier requests information

When an organization needs to check a person's identity or eligibility, it acts as the verifier. For example, a business may request confirmation that someone is over 18 or holds a particular professional qualification. OpenID for Verifiable Presentations (OpenID4VP) defines a protocol for requesting and receiving credential presentations. [4]

4. The holder presents the credential

The holder reviews the request and presents the appropriate information through their wallet. Depending on the credential format and available privacy features, they may be able to share selected attributes rather than the complete credential. For example, a digital identity credential may support sharing confirmation that an individual meets an age requirement without disclosing their full name, residential address or date of birth.

5. The verifier validates the information

The verifier checks the presented credential using the applicable cryptographic and trust requirements.

Verification can include confirming:

  • The credential's cryptographic signature or proof is valid.
  • The protected credential information has not been altered.
  • The issuer is recognized and trusted for the relevant purpose.
  • The credential has not expired or been revoked, where applicable.
  • The presenter satisfies any required holder-binding checks. [1][4][5]

Depending on the implementation, cryptographic verification may be performed without contacting the issuer during each presentation. This can offer privacy benefits by limiting the issuer's visibility into where and when a credential is used.

However, verification is not universally offline or independent of external services. Some implementations require access to issuer trust information, credential status services or other supporting infrastructure. Privacy-preserving status mechanisms may allow verifiers to check revocation information without directly identifying each credential being verified.

Importantly, a valid cryptographic signature does not automatically establish that the credential's claims are accurate or that its issuer is appropriate for a particular purpose.

For example, a digitally signed membership credential may be authentic but would not necessarily provide sufficient identity assurance for opening a bank account. The verifier must assess whether the issuer, credential type and underlying verification requirements are appropriate for the interaction.

What is an example of a Verifiable Digital Credential?

A mobile driver's license (mDL) is a practical example of a VDC.

Instead of relying only on a physical driver's license, an individual may receive a digital credential issued by an authorized government agency.

Consider someone purchasing an age-restricted product:

  1. The individual holds a government-issued mobile driver's license in a compatible digital wallet.
  2. The business requests proof that the individual meets the required age threshold.
  3. The individual reviews the request and authorizes the appropriate presentation.
  4. Depending on the wallet and credential capabilities, the individual may share an age-related attribute rather than their full name, address and date of birth.
  5. The business cryptographically verifies the presented information and evaluates the issuer's trustworthiness.

For example, some mobile driver's license implementations support issuer-signed age threshold attributes, such as confirmation that the holder is over 18. The wallet can present this attribute without disclosing the holder's complete date of birth or other unrelated identity information.

This allows the business to verify the information it needs while potentially collecting less personal data than it would through a complete document inspection. [1][2]

However, selective disclosure is not supported by every credential or wallet. The available information and presentation methods depend on the implementation.

How can Verifiable Digital Credentials be used in financial services?

Financial institutions can use Verifiable Digital Credentials to support identity verification during high-risk interactions, such as account recovery or high-value transactions.

For example, consider a customer who needs to recover access to their bank account after losing their usual authentication method. Rather than relying solely on security questions or uploading an image of their driver's license, the customer could present a government-issued digital identity credential from a compatible wallet.

The bank can cryptographically verify the credential, confirm that it was issued by a trusted authority and, verify that the person presenting the credential is its authorized holder.

Some credential implementations support cryptographic holder binding, where the wallet demonstrates possession of a private key associated with the credential. This can help establish that the presentation is being made by an authorized holder rather than someone who has obtained a copy of the credential.

Depending on the wallet and its security requirements, the individual may also need to unlock the wallet using a PIN, biometric verification or another supported method before presenting the credential.

A financial institution could apply a similar process when a customer initiates a high-value transaction that requires additional identity assurance. These use cases can provide additional confidence in the customer's identity while reducing reliance on physical documents and manual verification processes.

However, VDC verification does not automatically authorize a transaction or complete account recovery. Financial institutions must still apply appropriate authentication, fraud prevention and risk-based controls before approving sensitive actions. [2][6][7]

What are the different types of Verifiable Digital Credentials?

VDCs can represent different types of identity information, qualifications and entitlements.

Credential type
Example
What it verifies
Government identity credentials
Digital identity card
Identity attributes issued by an authorized authority.
Mobile driver's licenses
Digital driver's license
Identity information, driving privileges or age-related attributes.
Age verification credentials
Proof-of-age credential
Whether an individual meets a required age threshold.
Educational credentials
Digital degree or diploma
Academic qualifications or educational achievements.
Professional credentials
Professional license
Qualifications, certifications or authorization to practice.
Employment credentials
Employee credential
Employment status or organizational affiliation.
Membership credentials
Digital membership card
Membership status or eligibility to access particular services.

‍

The same general credential model can represent different types of claims, but the reliability of those claims depends on the issuer, issuance process and applicable trust framework. [1][6]

What is the difference between Verifiable Digital Credentials and traditional digital IDs?

Although the terms are closely related, Verifiable Digital Credentials and digital IDs are not necessarily the same.

A digital ID is a broad term for identity information or credentials represented electronically. A VDC is a more specific type of credential that contains claims protected by cryptographic mechanisms, allowing their integrity and origin to be verified.

Verifiable Digital Credentials
Traditional digital IDs
Primary purpose
Provide cryptographically verifiable claims or attributes.
Represent or establish identity digitally.
Verification
Uses cryptographic mechanisms and issuer trust checks.
Varies depending on the identity system.
Issuer involvement
May support independent verification after issuance.
May depend on a central identity provider or database.
Data sharing
May support selective disclosure.
Depends on the underlying system.
Storage
Often held in digital wallets.
May be associated with accounts, applications or identity platforms.

‍

A digital ID can itself be implemented as a VDC. The important distinction is whether the credential's claims can be verified through the relevant cryptographic mechanisms and trust framework. [1][2]

What is the difference between VDCs and Verifiable Credentials?

Verifiable Digital Credentials (VDCs) and Verifiable Credentials (VCs) are closely related terms that are often used interchangeably.

Verifiable Credential (VC) is the terminology used by W3C to describe credentials containing claims that can be verified using specified securing mechanisms. [1]

Verifiable Digital Credential (VDC) is a broader term used in digital identity discussions, including by NIST, to describe digitally issued, cryptographically verifiable credentials across different formats and standards. [2]

Not every VDC follows the W3C data model. For example, mobile driver's licenses may use the ISO mdoc format, while other credentials may use Selective Disclosure JSON Web Token Verifiable Credentials (SD-JWT VC), a format developed through the Internet Engineering Task Force (IETF).

These formats support cryptographically verifiable credentials but are not necessarily based on the W3C Verifiable Credentials Data Model. Standards such as OpenID4VCI and OpenID4VP support multiple credential formats rather than requiring every credential to use a single data model. [3][4]

What is selective disclosure in Verifiable Digital Credentials?

Selective disclosure is a privacy capability that allows credential holders to share specific attributes without revealing all the information contained in a credential.

For example, a digital identity credential may contain a person's full name, date of birth and residential address.

If an organization only needs proof that the person is over 18, a supported selective disclosure mechanism may allow the holder to present the necessary age information without revealing their full identity details. Some mobile driver's license implementations include issuer-signed age threshold attributes that allow a verifier to confirm whether an individual meets a specified age requirement.In this scenario, the wallet can disclose the relevant age attribute while withholding unrelated personal information, such as the individual's residential address or full date of birth.

Depending on the credential format, cryptographic mechanisms can allow individual attributes to be verified without disclosing every field contained in the original credential.The W3C Verifiable Credentials Data Model identifies selective disclosure as an important privacy consideration. [1]Selective disclosure can help organizations minimize unnecessary personal information collection while giving individuals greater control over the data they share.

However, selective disclosure is not automatically available in every VDC.

Its capabilities depend on the credential format, cryptographic mechanisms, wallet and verifier requirements.

What standards support Verifiable Digital Credentials?

Several international standards and protocols support the issuance, presentation, verification and management of Verifiable Digital Credentials. These specifications help establish interoperability between credential issuers, digital wallets and verifying organizations.

Standard or protocol
Organization
Purpose
W3C Verifiable Credentials Data Model v2.0
W3C
Defines a standardized data model for expressing and exchanging verifiable credentials.
OpenID4VCI
OpenID Foundation
Defines a protocol for issuing verifiable credentials to compatible digital wallets.
OpenID4VP
OpenID Foundation
Defines a protocol for requesting and presenting verifiable credentials between wallets and verifiers.
W3C Digital Credentials API
W3C
Defines a browser API that enables websites to request digital credentials from compatible wallets, supporting online credential presentation.
ISO/IEC 18013-5
ISO/IEC
Defines the data structures and protocols for mobile driver's licenses (mDLs), including proximity-based presentation and verification.
ISO/IEC TS 18013-7
ISO/IEC
Extends ISO/IEC 18013-5 to support remote presentation of mobile driver's licenses over the internet.
SD-JWT VC
IETF
Defines a credential format based on JSON Web Tokens that supports cryptographic verification and optional selective disclosure of individual attributes.
Token Status List (TSL)
IETF
Defines a mechanism for checking credential revocation, suspension and other status information, supporting formats such as SD-JWT VC and ISO mdoc.

‍

These standards address different parts of the credential lifecycle and can be used together. For example, a credential may be issued through OpenID4VCI, presented using OpenID4VP and checked against an appropriate status mechanism to determine whether it remains valid.

What regulations govern Verifiable Digital Credentials?

Regulations and government trust frameworks are helping establish how digital credentials can be issued, trusted and accepted. There is no single global regulation governing all VDCs. Requirements vary by jurisdiction, industry and the type of identity information being verified.

European Union: eIDAS 2.0

The European Union introduced Regulation (EU) 2024/1183, commonly associated with eIDAS 2.0, to establish a European Digital Identity Framework.

The framework requires EU member states to provide European Digital Identity Wallets according to deadlines linked to the relevant implementing acts, with rollout scheduled for the end of 2026. [8] These wallets are intended to support electronic identification, authentication and the presentation of verified attributes such as qualifications, licenses and other identity information. The framework also establishes requirements for certain public and private service providers to accept European Digital Identity Wallets.

Under Article 5f, applicable private-sector acceptance obligations are linked to services requiring strong user authentication under law or contractual obligation, with the relevant deadline falling in 2027. These requirements apply to specified sectors and circumstances rather than every organization operating in the EU. [8]

The framework is a significant development for VDCs because it establishes common legal and technical requirements for interoperable digital identity wallets across member states.

United Kingdom: Digital Verification Services framework

The UK's Data (Use and Access) Act 2025 establishes a statutory framework for digital verification services.

Part 2 of the Act provides for a government trust framework, certification arrangements, a register of digital verification services and a trust mark. [9] The UK Digital Verification Services Trust Framework sets requirements covering identity verification, security, privacy, governance and interoperability. Version 1.0 was finalized in June 2026, and its certification scheme came into effect on September 2, 2026. [10][11]

Although the framework is not specific to one credential format, it provides a structure for evaluating the trustworthiness of digital identity and attribute verification services.

United States: NIST Digital Identity Guidelines

In the United States, the National Institute of Standards and Technology (NIST) provides technical guidance through its Digital Identity Guidelines, SP 800-63-4, published in 2025.

These guidelines cover identity proofing, authentication and federation, including requirements for evaluating identity evidence and applying appropriate assurance levels. [6][7] NIST SP 800-63A-4 also describes how digital evidence, including digital credentials, can be evaluated during identity proofing.

The guidelines do not impose a universal legal requirement for businesses to accept VDCs, but they provide an important technical foundation for assessing digital identity systems.

Why do VDC regulations matter?

Regulations and trust frameworks help establish expectations for identity assurance, issuer trust, security, privacy and interoperability.

For organizations accepting VDCs, verifying a credential's cryptographic signature is only one part of the process. They must also consider whether the issuer is trusted, whether the credential meets applicable requirements and whether the verification process satisfies relevant legal obligations.

Accepting a VDC does not automatically establish compliance with Know Your Customer (KYC), anti-money laundering or other industry-specific requirements.

How do Verifiable Digital Credentials relate to authentication?

VDCs and authentication are closely related, but they perform different functions. Identity verification establishes or checks claims about who someone is or what attributes they possess. Authentication establishes whether someone attempting to access a system controls the required authenticator.

A VDC can provide evidence of identity, qualifications or eligibility. However, verifying a credential does not automatically authenticate someone for ongoing account access. For example, a person may present a government-issued digital identity credential during account recovery to support identity verification. The organization may still require additional authentication or account-binding checks before restoring access.

NIST's Digital Identity Guidelines distinguish identity proofing from authentication and define separate requirements for the assurance provided by each process. [6][7]

How do VDCs compare with passkeys?

VDCs and passkeys both use cryptography, but they are designed for different purposes.

Verifiable Digital Credentials
Passkeys
Primary purpose
Verify claims or attributes about a person or entity.
Authenticate a user to a service.
What they establish
Information issued by a trusted source, subject to verification requirements.
Proof of control over a cryptographic authenticator associated with an account.
Common uses
Identity verification, age assurance and qualifications.
Account login and authentication.
Technology
Cryptographically protected credentials and presentations.
Public-key cryptography using FIDO/WebAuthn.
Information shared
Credential claims or selected attributes.
Authentication-related cryptographic assertions.

‍

The two technologies can complement each other. For example, an organization may use a VDC to verify a customer's identity during onboarding and a passkey for subsequent account authentication.

Related authentication terms

Digital Identity: Information and attributes used to represent or establish the identity of a person or entity in a digital environment.

Digital Identity Wallet: An application or service that enables individuals to receive, manage and present compatible digital credentials.

Mobile Driver's License (mDL): A digitally issued driver's license that supports electronic presentation and verification under applicable standards.

Selective Disclosure: A capability allowing credential holders to reveal selected attributes without disclosing all the information in a credential.

Identity Verification: The process of establishing or checking claims about an individual's identity.

Passkeys: Cryptographic credentials used for phishing-resistant authentication. Learn more about passkeys.

Multi-factor Authentication (MFA): Authentication requiring evidence from more than one distinct authentication factor. Learn more about MFA

Risk-Based Authentication: An authentication approach that evaluates contextual signals to determine whether additional verification is appropriate. Learn more about Risk-Based Authentication.

Credential Issuer: An organization or authority that creates and issues credentials containing claims about a subject.

Credential Verifier: An organization or system that receives a credential presentation and evaluates its authenticity and suitability.

Verifiable Presentation: Information derived from one or more credentials and presented to a verifier, potentially with cryptographic proof relating to the holder or transaction.

What are Verifiable Digital Credentials?

Verifiable Digital Credentials (VDCs) are digitally issued credentials containing claims about a person, organization or entity that can be cryptographically verified. They provide evidence of identity, qualifications, eligibility or other attributes without relying solely on physical documents. [1][2]

What is an example of a Verifiable Digital Credential?

A mobile driver's license is an example of a VDC. It can contain government-issued identity information that compatible systems can verify electronically. Other examples include digital diplomas, professional certifications and proof-of-age credentials. [2]

How do Verifiable Digital Credentials work?

VDCs use an issuer-holder-verifier model. An issuer creates a cryptographically protected credential, a holder receives and manages it, and a verifier checks its authenticity when presented. Depending on the credential format, the holder may also share selected attributes rather than the complete credential. [1][3][4]

Are Verifiable Digital Credentials secure?

VDCs can provide strong protections through digital signatures, cryptographic holder binding and secure presentation protocols. However, their security depends on issuer trust, wallet security, credential status checks and the implementation of verification controls. [1][4][5]

What is the difference between VDCs and VCs?

VDC stands for Verifiable Digital Credential, while VC stands for Verifiable Credential. Both describe cryptographically verifiable digital credentials. VC is the terminology used by W3C, while VDC is often used more broadly to describe the ecosystem of digital credential formats and technologies. [1][2]

Do Verifiable Digital Credentials require a digital wallet?

Not necessarily. Digital wallets are a common way to receive, store and present VDCs, particularly on smartphones. However, credential storage and management can use other architectures, including remotely managed services. [3][4]

Can Verifiable Digital Credentials protect personal privacy?

Yes. Some VDC formats support selective disclosure, allowing individuals to share only the attributes required for a particular interaction. For example, a holder may be able to prove they meet an age requirement without revealing their full date of birth. These capabilities depend on the implementation. [1]

Are Verifiable Digital Credentials legally recognized?

Legal recognition depends on the jurisdiction, credential type and intended use. The EU's eIDAS framework establishes requirements for European Digital Identity Wallets, while the UK's Digital Verification Services framework supports trusted digital identity services. Acceptance of a credential for a particular legal or regulated purpose depends on the applicable requirements. [8][9]

Can Verifiable Digital Credentials replace passwords?

VDCs primarily provide evidence of identity or other attributes, while passwords are authentication credentials. Although VDC presentations may form part of an authentication process, they do not universally replace passwords, passkeys or other authenticators.

Can Verifiable Digital Credentials be used for financial services?

Yes. VDCs can support customer identity verification, onboarding, high-value transaction verification and account recovery. However, using a VDC does not automatically satisfy KYC, anti-money laundering or other regulatory requirements, nor does it independently authorize a transaction. Organizations must evaluate the issuer, assurance level and applicable verification obligations. [6][7]

References & Sources

[1] World Wide Web Consortium. (2025). Verifiable Credentials Data Model v2.0. W3C Recommendation. https://www.w3.org/TR/vc-data-model-2.0/

[2] Fisher, B., & Galluzzo, R. (2024). Digital identities: Getting to know the verifiable digital credential ecosystem. National Institute of Standards and Technology. https://www.nist.gov/blogs/cybersecurity-insights/digital-identities-getting-know-verifiable-digital-credential-ecosystem

[3] Lodderstedt, T., Yasuda, K., Looker, T., & Bastian, P. (2025). OpenID for Verifiable Credential Issuance 1.0. OpenID Foundation, Final Specification. https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-final.html

[4] Terbu, O., Lodderstedt, T., Yasuda, K., Fett, D., & Heenan, J. (2025). OpenID for Verifiable Presentations 1.0. OpenID Foundation, Final Specification. https://openid.net/specs/openid-4-verifiable-presentations-1_0-final.html

[5] World Wide Web Consortium. (2025). Bitstring Status List v1.0: Privacy-preserving status information for Verifiable Credentials. W3C Recommendation. https://www.w3.org/TR/vc-bitstring-status-list/

[6] National Institute of Standards and Technology. (2025). Digital Identity Guidelines: Identity Proofing and Enrollment (NIST Special Publication 800-63A-4). https://doi.org/10.6028/NIST.SP.800-63A-4

[7] National Institute of Standards and Technology. (2025). Digital Identity Guidelines (NIST Special Publication 800-63-4). https://doi.org/10.6028/NIST.SP.800-63-4

[8] European Parliament and Council of the European Union. (2024). Regulation (EU) 2024/1183 establishing the European Digital Identity Framework. Official Journal of the European Union. https://eur-lex.europa.eu/eli/reg/2024/1183/oj

[9] UK Parliament. (2025). Data (Use and Access) Act 2025, Part 2: Digital verification services. https://www.legislation.gov.uk/ukpga/2025/18/part/2

[10] UK Department for Science, Innovation and Technology. (2026). UK digital verification services trust framework (1.0). https://www.gov.uk/government/publications/uk-digital-verification-services-trust-framework-1-0

[11] UK Department for Science, Innovation and Technology. (2026). Certification scheme for the UK digital verification services trust framework. https://www.gov.uk/guidance/certification-scheme-for-the-uk-digital-identity-and-attributes-trust-framework

This article draws on primary technical standards, government legislation and official guidance from W3C, the OpenID Foundation, NIST, the European Union and the UK government.

Last reviewed: November, 2026

‍