By clicking "Accept", you agree to the storing of cookies on your device to enhance site navigation, analyze site usage and assist in our marketing efforts. More info

Remote mDL Verification: Hidden Roadblocks You Should Know

Published
March 14, 2025

Many of our clients at Dock Labs have been asking for clarity on the current state of remote verification of mobile driver’s licenses (mDLs), specifically regarding the ISO 18013-7 standard.

Here’s what we know:

First, a Quick Refresher: ISO 18013-5 vs. ISO 18013-7

  • ISO 18013-5:
    This standard defines how in-person verification of mobile driver’s licenses works. It has been around for a while and is mature. When organizations mention "real-world verification of mDLs," they're typically referring to verification using ISO 18013-5.

  • ISO 18013-7:
    This standard was only recently published (September 2024) and defines how remote verification of mDLs should be conducted. Despite its recent publication, ISO 18013-7 is already due to be replaced by an updated version, which is expected soon. It's important to note that ISO 18013-7 can also be used for in-person verification, as long as both the mDL and the reader are online. ISO 18013-5 applies when either the mDL, the verifier, or both are offline.


Why Remote Verification (ISO 18013-7) Is Still in Development

ISO 18013-7 depends on multiple other standards and protocols, all of which are also still evolving.

Here are the key dependencies that directly impact remote mDL verification today:

  1. OpenID for Verifiable Credentials (OID4VC)
    ISO 18013-7 significantly relies on OID4VC protocols. These protocols do not yet have an official v1.0 release, with the most recent draft published as recently as December 2024.

  2. Digital Credentials API (W3C Standard)
    ISO 18013-7 also depends on the Digital Credentials API, a W3C standard defining how mobile browsers will access digital credentials stored in mobile wallets. This standard is still in active development. Google has launched a public beta, but we don’t yet see public support from Apple or Samsung.

  3. Verifier Lists from AAMVA
    In North America, verifying mDLs depends on verifier lists provided by the American Association of Motor Vehicle Administrators (AAMVA). Currently, these verifier lists are only available via manual downloads or through an undocumented API service.

Current Status of US States Supporting Remote Verification

While more than 12 US states actively support ISO 18013-5 for in-person verification, none yet officially support ISO 18013-7 in production.

Currently, California is the only state we are aware of that has announced a public beta for remote verification based on ISO 18013-7. Their program should be widely available in Q1 2025.

Our Perspective and Next Steps

Given these multiple dependencies and evolving standards, Dock Labs continues to track these developments closely.  

We are actively engaging with industry groups and participating where possible. However, we recognize that practical implementation of remote verification using ISO 18013-7 remains dependent on the maturity of several evolving standards and protocols. We remain committed to supporting our clients as the standards and technologies continue to mature.

We’ll keep you informed about new developments as soon as we learn more.

Create your first Verifiable Credential today

Truvera enables IDV providers and IAM systems to verify the same person across multiple businesses or siloed systems. It enables them to easily confirm that a user has been verified before, create a consistent view of that user’s identity and significantly reduce onboarding friction.