Intent to Experiment: Digital Credentials API (issuance support)

[Chromestatus]

Contact emails

rby...@chromium.org, ma...@chromium.org, ashim...@google.com

Explainer

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

Specification

https://w3c-fedid.github.io/digital-credentials

Summary

This Web Platform feature enables issuing websites (e.g., a university, government agency, or bank) to securely initiate the provisioning (issuance) process of digital credentials directly into a user's mobile wallet application. On Android, this capability leverages the Android IdentityCredential CredMan system (Credential Manager). On Desktop, it leverages cross-device approaches using the CTAP protocol similar to Digital Credentials presentation.

Blink component

Blink>Identity>DigitalCredentials

Web Feature ID

Missing feature

TAG review

https://github.com/w3ctag/design-reviews/issues/1119

TAG review status

Pending

Origin Trial documentation link

https://w3c-fedid.github.io/digital-credentials

Risks

Interoperability and Compatibility

There are multiple standards efforts involved here. We have been working with WebKit and Mozilla in the WICG on defining this specific API. But the greater interoperability risk will come from the data that is sent and returned via this API. Details of that are driven outside the web browser community in the OpenID Foundation.

Gecko: Negative (https://github.com/mozilla/standards-positions/issues/1003)

WebKit: Support (https://github.com/WebKit/standards-positions/issues/332) Presentation support is shipped, but timeline for adding issuance support yet.

Web developers: No signals

Other signals:

Activation

The primary activation concern is enabling existing deployments using technology like OpenID4VCI to be able to also support this API. As such we have left the request protocol unspecified at this layer, to be specified along with existing request protocols to maximize activation opportunity.

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None

Goals for experimentation

Ongoing technical constraints

None

Debuggability

None necessary - just new JS API. For testing we plan to add a developer option to provide a fake wallet, but this effort is still ongoing.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

No

Is this feature fully tested by web-platform-tests?

Yes
https://wpt.fyi/results/digital-credentials?label=experimental&label=master&aligned

Flag name on about://flags

web-identity-digital-credentials-creation

Finch feature name

WebIdentityDigitalCredentialsCreation

Requires code in //chrome?

True

Tracking bug

https://crbug.com/378330032

Launch bug

https://launch.corp.google.com/launch/4418038

Estimated milestones

Origin trial desktop first	143
DevTrial on desktop	133
Origin trial Android first	143
DevTrial on Android	133

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5099333963874304?gate=5124632629870592

This intent message was generated by Chrome Platform Status.

[Mike Taylor]

Could you clarify which milestones you're requesting? I see M143 as the start, but no ending milestone.

Non-blocking question: I note that the WPTs for navigator.credentials.create() are all failing (except one) - is that expected?

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68ed3208.050a0220.30571e.0360.GAE%40google.com.

[Rick Byers]

On Mon, Oct 13, 2025 at 7:31 PM Mike Taylor <mike...@chromium.org> wrote:

Could you clarify which milestones you're requesting? I see M143 as the start, but no ending milestone.

Like for presentation, I believe we're expecting issuance trials to go slowly over an extended time period. So I'd request 6 milestones (and wouldn't be surprised if we make some tweaks and ask for an extension after that). 

Non-blocking question: I note that the WPTs for navigator.credentials.create() are all failing (except one) - is that expected?

Good question, Mohamed? 

[Mike Taylor]

On 10/14/25 9:50 a.m., Rick Byers wrote:

On Mon, Oct 13, 2025 at 7:31 PM Mike Taylor <mike...@chromium.org> wrote:

Could you clarify which milestones you're requesting? I see M143 as the start, but no ending milestone.

Like for presentation, I believe we're expecting issuance trials to go slowly over an extended time period. So I'd request 6 milestones (and wouldn't be surprised if we make some tweaks and ask for an extension after that). 

Thanks - LGTM to experiment from M143 to M148 inclusive.

[Mohamed Amir Yosef]

On Tue, Oct 14, 2025 at 1:31 AM Mike Taylor <mike...@chromium.org> wrote:

Could you clarify which milestones you're requesting? I see M143 as the start, but no ending milestone.

Non-blocking question: I note that the WPTs for navigator.credentials.create() are all failing (except one) - is that expected?

Because the content feature flag controlling the feature is currently disabled. (and can only be overridden from the chrome://flags_

It will be enabled as part of the CL that starts the OT.