demo · v143
mDL vs VC flows
Two real issuance shapes Chrome 143 exposes through navigator.credentials.create(): an ISO mDL credential configuration and a W3C-style SD-JWT VC credential configuration. Both use the current openid4vci-v1 issuance protocol; the old preview protocol is shown only as a legacy path that this demo does not send.
chrome://flags/#web-identity-digital-credentials-creation. This page renders and validates the wire shapes even when the API or a wallet is unavailable.
...create()
navigator.credentials.create({ digital }) is the issuance entry point.
...openid4vci-v1
DigitalCredential.userAgentAllowsProtocol() checks the browser protocol gate, not wallet availability.
...preview
Some builds still advertise the pre-spec protocol, but it is not the current issuance path.
why this angle
The other concept builds a single request and reports support probes. This one contrasts two credential configurations inside the same OpenID4VCI handoff — US/EU mDL issuance vs an SD-JWT VC ecosystem credential — so issuers know which metadata belongs in the wallet-targeted request.