Digital ID: mDL Verification

Verify a user with a mobile driver's license (mDL) presented from a phone wallet (such as Apple Wallet, Google Wallet, or a state DMV app like CA DMV Wallet) instead of capturing a photo of a physical ID.

You can offer this in two ways:

• In the Incode Hosted onboarding app, where the wallet option appears automatically on the ID chooser screen after it is enabled in your flow configuration.
• In your own custom web UI, using the Incode Web SDK headless renderWallet API to launch the wallet flow from your own button.

For the full list of supported wallets, schemes, and attributes across regions, see Supported Digital IDs.

How it works

For mDL verification, the user must have their ID saved to their phone wallet. This is called a verifiable digital credential. Verification of a user's digital credential follows the same onboarding session model as the physical id verification:

1. Your application creates or opens an Incode onboarding session.
2. The user chooses to verify with their digital ID.
3. The browser launches the native wallet sheet with navigator.credentials.get().
4. The user selects the credential and consents to share the requested attributes.
5. The encrypted wallet response is sent to Incode Server for decryption and verification.
6. Verification results are stored on the session and can be retrieved using the standard Incode result APIs.

The user's identity attributes are not returned directly to the web page from the wallet call. The wallet response is encrypted for Incode services and verified attributes are made available through the session's standard OCR data, score, and webhook result surfaces.

Supported Wallets

Incode supports CA DMV Wallet app on both platforms. The CA DMV Wallet app is presented through same path for iOS and Android as Apple and Google wallet

Apple requires approval for every individual client (relying party). Contact your Incode representative before going live with Apple Wallet.

Incode is an approved Google Verifier registrar and handles Google Wallet registration on your behalf. The user must still be on a supported Android Chrome environment with a compatible digital ID in Google Wallet. Contact your Incode representative before going live with Google Wallet.

Option 1: Use the Incode Hosted onboarding app

If you use Incode's hosted or embedded onboarding app, no extra front-end integration is required after the flow is configured.

When the user reaches the ID chooser screen, the app shows a digital ID option alongside the normal document capture options, when all of the following are true:

• Digital IDs are enabled in the flow configuration.
• Apple Wallet or Google Wallet is enabled for the flow.
• The user's device and browser support the wallet method.
• The user has a compatible digital ID in their wallet.

The user taps the wallet option, confirms the wallet presentation in Apple Wallet or Google Wallet, and returns to the onboarding flow after the encrypted response is verified.

If the wallet flow cannot be completed, the user can continue with the regular ID capture fallback path depending on your flow configuration.

Option 2: Use the Web SDK headless wallet API

Use the Web SDK renderWallet API when you are building your own UI and want to expose only the wallet functionality.

This is useful when:

• You do not use the Incode ID chooser screen.
• You want a custom button, page, or modal for digital ID verification.
• You want to offer wallet verification in a custom onboarding flow while still using Incode to create the wallet request, decrypt the response, and store results on the session.

Retrieving results

Digital ID results are returned at the end of the Incode onboarding session. Use your existing Incode result retrieval pattern:

• OCR data retrieval for verified identity attributes
• Score or validation result retrieval for decisioning
• Webhooks for session status transitions and downstream automation

The response from renderWallet is not a replacement for the final session result. Treat it as confirmation that the wallet response was submitted and processed.

Recommended integration patterns

For Incode Hosted onboarding app customers:

1. Enable Digital IDs in the flow configuration.
2. Let the wallet option appear in the hosted chooser screen.
3. Use standard Incode session result and webhook handling after completion.

For Web SDK customers using the built-in ID capture UI:

1. Enable Digital IDs in the flow configuration.
2. Use the chooser wallet button by default.
3. Add hideDigitalIdButton: true only if you want to move the wallet entry point into your own UI.

For Web SDK customers with fully custom UI:

1. Enable Digital IDs in the flow configuration.
2. Create your own wallet button.
3. Call renderWallet from the button click handler.
4. Use onSuccess and onError to control your own UX.
5. Fetch final results from the session using standard Incode result APIs.

Error and fallback handling

Wallet presentation can fail when:

• The device or browser does not support Digital Credentials APIs.
• The user does not have a compatible digital ID in their wallet.
• The user cancels the wallet presentation.
• Apple Wallet domain approval is not complete.
• The wallet response cannot be decrypted or verified.

Your application should provide a fallback path, such as retrying wallet verification or continuing with physical ID capture.

Scope notes

• The integration model is flow-based. Requested attributes and enabled wallet methods are configured in Dashboard, not passed ad hoc from the browser.

Related pages

• Supported Digital IDs for the full list of wallets, schemes, and attributes
• ID Capture module configuration for Dashboard setup