v143 · miscellaneous

Digital Credentials API (issuance support)

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

concepts

  1. Credential Issuance

    Build an issuance request live and call navigator.credentials.create from the page. Feature probes show what the browser exposes and report the outcome.

  2. mDL vs VC flows

    The two real deployed issuance shapes side-by-side: ISO mobile driving licence metadata and SD-JWT VC metadata, both carried through the current openid4vci-v1 issuance protocol with removed preview handling called out.

  3. Presentation flow

    The relying-party half of the loop. Pick a use case — age verification, KYC, education, employment — and watch the page build the DCQL query, invoke navigator.credentials.get({ digital }), and show the actual rejection or returned presentation.

  4. Protocol explorer

    Cards for every protocol string Chrome accepts: openid4vp, openid4vci, org.iso.mdoc, and deprecated preview. When to use each, what its request body looks like, and which version Chrome 143 understands.

why it shipped

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

references