Pieces Falling into Place: Verifiable Credentials 2.0 & Android Digital Credentials Support

Published: May 16, 2025

The W3C has officially advanced the Verifiable Credentials 2.0 family of specifications to W3C Recommendation status, providing a robust, privacy-preserving framework for expressing and exchanging digital credentials on the Web. Learn more.

What’s in VC 2.0?

VC 2.0 comprises seven core Recommendations—such as the Verifiable Credentials Data Model v2.0, Data Integrity cryptosuites, and JOSE/COSE security bindings—that together enable issuers, holders, and verifiers to interoperate, selectively disclose claims, and cryptographically verify credentials.

Android’s Digital Credential Push

Just weeks ago, Android announced native support for digital credentials via its Credential Manager’s DigitalCredential API, letting apps present and even issue verifiable credentials using OpenID4VP and OpenID4VCI flows. Read the announcement.

Wallets like Google Wallet, Samsung Wallet, and 1Password are already integrating this into their platforms, making it easy to store and display mobile driver’s licenses, health passes, and more.

Why It Matters

With the spec now an official Recommendation and platform support landing on Android, developers can quickly prototype new credential types and build seamless user experiences—while preserving selective disclosure and user privacy.

Issuers gain a clear roadmap for implementation, and verifiers benefit from standardized, interoperable proof formats.

Looking Ahead: The Ketchup Effect

All these pieces—W3C RC status, Android integration, major wallet support—mean we’re on the brink of a “ketchup effect.” Issuers (governments, universities, enterprises) and verifiers (wallets, service providers) will suddenly race to ship compatible solutions.

Before long, pilots will give way to widespread, seamless digital credential exchange—ushering in a new era of trusted, privacy-respecting identity on Web and mobile. Huge thanks to everyone in the W3C Verifiable Credentials Working Group and the Android team for making this possible!

Cheers,

Ludwig