Wallet compatibility
Supported wallets and jurisdictions
Section titled “Supported wallets and jurisdictions”These tables show which wallets are supported for each credential type. This list updates as support expands. You can restrict which jurisdictions are accepted for a session using jurisdiction filtering.
US mobile driver’s licenses
Section titled “US mobile driver’s licenses”Only jurisdictions with at least one supported wallet are listed.
| Jurisdiction | Apple Wallet | Google Wallet | State-Issued Wallet |
|---|---|---|---|
| Arizona | ✅ | ✅ | — |
| California | ✅ | ✅ | ✅ |
| Colorado | ✅ | ✅ | — |
| Georgia | ✅ | ✅ | — |
| Hawaii | ✅ | — | — |
| Iowa | ✅ | — | — |
| Maryland | ✅ | ✅ | — |
| New Mexico | ✅ | ✅ | — |
| Ohio | ✅ | — | — |
| Puerto Rico | ✅ | — | — |
ePassports
Section titled “ePassports”| Wallet | Supported |
|---|---|
| Google Wallet | ✅ |
| Apple Wallet | — |
The SDK handles wallet selection and compatibility detection automatically — you don’t need any wallet-specific logic in your application.
Browser and platform requirements
Section titled “Browser and platform requirements”The SDK uses the Digital Credentials API (DC API) when available and falls back to a QR code flow otherwise — no configuration needed.
For current DC API browser and platform support, see the DC API ecosystem support matrix. In browsers or platforms without DC API support, the SDK automatically falls back to the QR code flow, which works in any modern browser.
How wallet selection works
Section titled “How wallet selection works”You don’t choose a wallet — the end user does. When the verification iframe opens, the SDK:
- Detects the browser’s capabilities (DC API support, platform).
- Shows the user wallets that are compatible with their browser and jurisdiction.
- Handles protocol negotiation for whichever wallet the user selects.
If a wallet isn’t compatible with the current browser (e.g., Apple Wallet on Chrome/Android), the iframe shows guidance directing the user to the QR code flow or a supported browser.