Stop asking customers to photograph their ID. Remote mDL verification is here.
ISO 18013-7 gives you a standardized path from document-photo-selfie workflows to cryptographically verifiable identity online and in app.
✓ Support proximity-based mDL presentation with ISO 18013-5 (NFC/BLE/QR)
✓ Keep your architecture flexible across mdoc/mDL, SD-JWT VC, W3C VC, and AnonCreds
How mDL verification works
A mobile driver’s license is a digital version of your driver’s license stored in a digital wallet on a mobile phone. Issued by a government authority and cryptographically signed so the data cannot be altered without discovery. Can be verified instantly.
The international standard (ISO 18013-5) for creating a digital, machine-readable, tamper-proof version of a physical document: driver’s licenses, national IDs, health cards, professional licenses, age attestations. An mDL is one type of mdoc.
The standard for in-person (proximity) mDL presentation using NFC, BLE, or QR codes. Covers face-to-face verification scenarios: border gates, bar counters, law enforcement stops, pharmacy pickups.
The standard that allows an mDL to be verified online and remotely. Uses OpenID4VP to enable web and app-based identity checks without physical proximity: bank onboarding, age-gated content, government portals.
OpenID for Verifiable Presentations — the protocol that lets a relying party (website, app) request and receive a verifiable credential presentation from a user’s wallet over the internet. The transport layer for 18013-7.
Where remote mDL verification shows ROI first
Confirm age without collecting personal data. Selective disclosure enables data minimization that satisfies GDPR and consumer expectations. Instant, no-friction proof of age for access and purchases at a counter or on a screen.
Replace document uploads and manual review with cryptographic verification. Add biometric authentication for identity assurance. Turn identity into a portable, reusable proof KYC cost drops from dollars to cents per verification.
Frictionless access to digital services with cryptographic assurance. Mitigate deepfakes and synthetic identities. Meet citizens’ data privacy and security expectations while streamlining operations and reducing costs.
From issuance to verification
A government authority issues an mDL credential to a person’s digital wallet on their phone. The credential and its data attributes are cryptographically signed at issuance.
When a person needs to prove their identity online (e.g., opening a bank account), the relying party’s app or website sends a verification request to their wallet via OpenID4VP.
The wallet lets the person selectively present attributes — such as “over 21” — without revealing name, address, or ID number. The person consents to share this data.
The verification service validates the credential’s cryptographic signatures, confirming the issuer is authentic and the data hasn’t been tampered with. Pass or fail, in under a second.
18013-5 got mDL started. 18013-7 makes it useful online.
The holder taps or brings their phone close to a reader. The credential is presented over NFC, BLE, or QR. No internet connection is required and cryptographic verification happens locally. This is the foundation that most state DMV rollouts and wallet-based credential programs are built on today.
The holder presents the credential over the internet using OpenID4VP. Same cryptographic trust, delivered remotely. This unlocks web and app identity checks and the use cases where most digital customer journeys actually happen. Without 18013-7, mDL is limited to face-to-face scenarios.
Identity verification shouldn’t feel like 2015
With deepfake and synthetic identity fraud surging, document-photo-selfie workflows are both slow and unsafe. With Indicio Proven, you get state-of-the-art document validation and biometric authentication; your customers get an instant, cryptographic way to prove who they are, anywhere they are. No uploads. No AI fakery. Just portable, frictionless digital trust.
Indicio Proven supports mdoc/mDL, SD-JWT VC, JSON-LD, AnonCreds, OID4VC, DIDComm, EUDI, ICAO DTC, and Open Badges 3.0, all working together in a single solution. Cross-jurisdictional by design: credentials issued in any region can be verified anywhere.
Government-issued identity documents from around the world can be authenticated and converted into tamper-proof Verifiable Credentials. Biometric authentication with liveness checks and face mapping is incorporated directly into credential issuance, closing deepfake and synthetic ID risks.
Proven is a trust layer you add to existing systems — no rip and replace. Integrate with existing IAM, mobile apps, and cloud environments through APIs and a mobile SDK. Start small: a simple implementation can take just days. Even complex national deployments take only months.
Frequently asked questions
A mobile driver’s license — a government-issued driver’s license stored digitally in a phone wallet. It’s cryptographically signed, so it can be verified instantly without manual document review.
An mDL is a specific type of mdoc (a driver’s license). The mdoc specification, established by ISO, is a generic container that can support many credential types for mobile devices: national IDs, health cards, professional licenses, age attestations, and more.
If you have any remote onboarding, online access, or web/app identity checks: yes. 18013-5 handles in-person presentation only. 18013-7 is the pathway for remote presentation via OpenID4VP, which is where most digital customer journeys happen.
The mdoc specification supports selective disclosure. An age check can confirm “over 21” without exposing name, address, or ID number. This aligns with GDPR, state privacy laws, and consumer expectations for data minimization.
You don’t just get 18013-5 (proximity) and 18013-7 (remote) verification, you get a globally interoperable platform that deploys credentials across sectors and jurisdictions. White-label wallet, mobile SDK, APIs, continuous support, and every major credential format from a single codebase. You have everything you need today and everything you might need tomorrow.
Get your license to verify
Whether you’re a state DMV issuing mobile driver’s licenses, a bank accepting them for KYC, or a platform preparing for EUDI, we’ll show you how Proven makes mdoc issuance and verification a drop-in capability.
Book a session →