Digital Credentials API (mDL and wallet IDs)
Lets a site ask for a government ID or other credential from a digital wallet.
In one line
Can ask for facts from your digital ID, only the ones you approve
Lets a site ask for a government ID or other credential from a digital wallet.
Requests only fields the person approves (age over 21, name, address) from a wallet such as Google Wallet or Apple Wallet, with a browser prompt.
What it can and can't do
What the user does: You tap Verify with ID and approve each item in your wallet
It can
- Ask your wallet for one fact such as age over 21, name or address
- Receive only the fields you approve in the wallet
- Prove you are an adult or a resident without handing over the whole ID
It cannot
- See your full ID card or photo when you approve only one field
- Get anything without your approval in the wallet
- Work in Firefox or Safari on most devices today
- Keep the ID facts after the check unless the site chooses to store them
How it differs between platforms: Chrome and Edge support it. Safari support is partial. Firefox does not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 141 | 2025-09-30 | None |
| Edge | Supported | 141 | 2025-10-03 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Partial | 26 | 2025-09-15 | mdoc only |
| Safari on iPhone | Partial | 26 | 2025-09-15 | mdoc only |
| Chrome on Android | Supported | 141 | 2025-09-30 | Play services 24.0+ |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | navigator.credentials.get({digital:{requests:[{protocol:'openid4vp-v1-unsigned'|'org-iso-mdoc', data}]}}), DigitalCredential.userAgentAllowsProtocol() |
| Permissions policy | digital-credentials-get |
| Browser compat keys | api.DigitalCredential |
| How access is granted | prompt |
| What the user sees | Browser wallet picker plus per field consent in the wallet |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | Yes |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: Lets a site ask for a government ID or other credential from a digital wallet.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
protocol | enum | None | openid4vp-v1-unsigned, org-iso-mdoc | Not listed |
data | object | None | verifiable presentation or mdoc response | fields chosen by the person |
Technical limits
- Android needs Play services 24.0 or newer; desktop uses QR plus BLE proximity
- Firefox no stable support
- Spec still a W3C Working Draft
The story
What it is
A site can ask your phone wallet for a government ID, with you approving what is shared.
For you
A prompt appears on your computer or phone asking if you agree to share things like 'over 21' from your wallet ID. You scan a code or tap and approve with Face ID. Nothing is shared until you agree.
For makers
Makers use it for age checks, account opening and fraud checks without collecting photos of ID. It lowers risk and cost, and they store less data about the person.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | An online liquor or vape shop asks wallet ID to prove 'over 21' without storing a driver's license photo. | None named |
| banking | A bank opens an account online by asking the wallet for a verified name and address instead of an upload. | None named |
| games | A game or betting site proves a player is an adult with a single wallet approval, with no ID scan. | None named |
| travel | A car rental site verifies a driver's license from the wallet before it releases the booking. | Hertz |
| social | A social or dating site uses a wallet age check to keep kids out, sharing only the yes or no. | None named |
| security | A site checks that the ID is signed by a real government issuer, which stops forged scans. | None named |
Risks
- Oversharing if you approve too much
- Wallet vendor sees the request
What the platform says
- Google Chrome: Digital Credentials API. Chrome describes it as a way for sites to request verified documents like a driver's license from a wallet, with the person in control.
- Apple: Verify with Wallet. Apple pitches showing ID in Wallet to apps and sites, sharing only the details a person approves.
Good uses and abuse
Legitimate uses
- Age verification
- KYC
- Account recovery
Known abuse
- Over collection of personal data by relying parties
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2025-09, Chrome 141: Digital Credentials ships (OpenID4VP and ISO 18013-7 Annex C)
- 2025-09, Safari 26: Safari 26 supports only org-iso-mdoc
- 2026-09, Safari 27: DigitalCredentialRequest renamed DigitalCredentialGetRequest
Sources
How well checked: Checked against real behavior.