Digital Credentials API (presentation support)

Category: Miscellaneous
Type: New or changed feature
Status: Origin trial (Chrome 141)
Intent stage: None

Summary

Websites can and do get credentials from mobile wallet apps through a variety of mechanisms today (custom URL handlers, QR code scanning, etc.). This Web Platform feature would allow sites to request identity information from wallets via Android's IdentityCredential CredMan system. It is extensible to support multiple credential formats (eg. ISO mDoc and W3C verifiable credential) and allows multiple wallet apps to be used. Mechanisms are being added to help reduce the risk of ecosystem-scale abuse of real-world identity (see https://docs.google.com/document/u/1/d/1L68tmNXCQXucsCV8eS8CBd_F9FZ6TNwKNOaFkA8RfwI/edit).

Motivation

Without this, websites and wallets can only communicate in ways that are more opaque to the browser and OS.

Standards & signals

Specification: https://w3c-fedid.github.io/digital-credentials
Firefox: Negative — We share most of Mozilla's concerns and continue to work with them (and the broader community) on mitigations. I believe we feel greater risk for the established practice of custom schemes becoming prevalent than Mozilla does (eg. due to Google being mandated by eIDAS regulation to accept EUDI credentials).
Safari: Shipped/Shipping — WebKit implementation progress: https://bugs.webkit.org/show_bug.cgi?id=268516 Shipping in iOS 26: https://developer.apple.com/videos/play/wwdc2025/232/
Web developers: No signals
Tracking bug: https://issues.chromium.org/issues/40257092

Samples: https://digitalcredentials.dev/docs/requirements

Explainers: https://github.com/w3c-fedid/digital-credentials/blob/main/explainer.md

View on chromestatus.com