OpenID4VCI is not merely a VC format effort. The core spec defines an OAuth-protected API for issuing credentials and explicitly supports multiple credential families, including W3C VCDM credentials, ISO mdocs, and SD-JWT VC.
The most important structural contribution is the decomposition of issuance into separate protocol surfaces: credential offers, authorization, token exchange, nonce retrieval, credential retrieval, deferred retrieval, notifications, and metadata publication are all first-class parts of the spec.
The spec’s support for both authorization-code flow and pre-authorized-code flow is analytically important because it makes two distinct trust and UX postures explicit: a full OAuth-style user authorization path and a lighter pre-arranged issuance path.
Credential-offer-by-value and credential-offer-by-reference are worth retaining as a separate design seam. They show that cross-device onboarding and wallet handoff are not incidental implementation details but part of the standard’s transport model.
Metadata is a major control plane in this stack. Credential issuer metadata, authorization-server metadata, and client metadata determine which formats, endpoints, proof types, and behaviors are available to wallets in practice.
Deferred issuance and notification flows make the spec more than an instant-download transport. They expose the fact that many real issuance processes are asynchronous and policy-gated.
The official repository structure matters because it shows the spec as a live maintained standards surface with explicit 1.0 and 1.1 tracks, rather than a dead PDF or one-off draft.
The conformance materials matter because they show the standard already moving from paper specification into implementation governance. By early 2026, OpenID Foundation materials describe open-source tests, self-certification, jurisdiction-specific profiling, and repeated interop events as part of the standard’s operating environment.
Specific source signals worth retaining
The 1.0 specification page is the main primary source for the protocol surface itself: it exposes the endpoint decomposition, authorization-flow split, metadata sections, proof types, security/privacy considerations, and credential-format appendices.
The OpenID4VC specifications index is the best compact source for situating OpenID4VCI inside the broader OpenID4VC family and for seeing how OIDF treats the specifications as a maintained package rather than a single isolated document.
The OpenID4VCI GitHub repository and README are the clearest sources for implementation-adjacent maturity signals: active working-group maintenance, versioned branches, and published WG-draft build targets.
The conformance-testing page is the key source showing that interoperability is being operationalized through an official test suite rather than left purely to informal interpretation of the spec.
The February 2026 self-certification announcement is the best source for the adoption/governance layer: OIDF positions OpenID4VCI and related specs as deployable infrastructure across dozens of jurisdictions, with local profiling, CI integration, and eventual published certification results.
Why this entry belongs in the corpus
It gives the corpus a standards-level issuance baseline beneath app-specific credential products, wallets, and regional digital-ID programs.
It strengthens the identity cluster by isolating a frequently flattened layer: credential issuance transport and metadata governance are not the same thing as credential format design, issuer trust, or proof-wallet UX.
The durable insight is that a large share of power in credential ecosystems can migrate away from the credential object itself and into offer transport, wallet acceptance, metadata publication, conformance profiles, and certification expectations. OpenID4VCI makes those seams unusually visible.