Anywhere
In Person and Online
mDLs are used in person and online. walt.id supports both: in person via QR code or NFC (ISO/IEC 18013-5), online via OpenID4VP and the Digital Credentials API (ISO/IEC 18013-7).
ISO mDL
Issue, store and verify mobile driving licenses
walt.id's Issuer, Wallet and Verifier support ISO mdoc and mobile driving licenses (ISO/IEC 18013-5) alongside SD-JWT VC and W3C Verifiable Credentials. Start with the open-source Community Stack and scale with the Enterprise Stack, on premises or in your own cloud.
- Open-Source
- Standard & Regulatory Compliant
- Gov & Enterprise Proven
Used by +70.000 developers and organisations
Trusted by leading organizations
End-to-end
One stack for the whole mDL lifecycle
Issue, store and verify mobile driving licenses using open standards.
Issue
Turn data from your existing systems into signed mdocs, such as mobile driving licenses, and deliver them to any compliant wallet via OpenID4VCI.
Issuer SDKs & APIsStore
Launch your own wallet or add wallet features to your app, custodial, non-custodial or hybrid, so users can receive, hold and present mDLs.
Wallet SDKs & APIsVerify
Request only the data elements you need, online via OpenID4VP or the Digital Credentials API, and check the issuer's certificate against a VICAL, the signature and status.
Verifier SDKs & APIs
New to mDL? Read ISO mdoc & mDL explained in the docs.
Built for production
Everything you need to launch mDLs in production
Open standards, your own keys and full credential lifecycle control.
Developer-First
APIs and SDKs for Every Layer
Eliminate fragmentation with agnostic APIs/SDKs that support mDLs and other mdocs across platforms and ecosystems.
Issuer API
Wallet API
Verifier API
REST APIs
Kotlin Multiplatform
Android
iOS (Swift)
ISO mDL
SDKs & Libraries
Future-Proof ID Infrastructure
Regulatory Alignment
Aligned with emerging global frameworks, ensuring your credentials are accepted by governments and compliant wallets worldwide (incl. eIDAS 2).
Interoperable by Design
Global Standards
ISO/IEC 18013-5 for mDLs and other mdocs, ISO/IEC 18013-7 for online presentation, issued via OpenID4VCI and presented via OpenID4VP and the Digital Credentials API.
ISO/IEC 18013-5
ISO/IEC 18013-7
OpenID4VCI
OpenID4VP
Total Data Sovereignty
Your Keys, Your Vault
Keep signing keys in your preferred KMS or HSM, such as AWS KMS, Azure Key Vault, HashiCorp Vault or a PKCS#11 HSM. Available in both product editions, so you keep full control of your keys.
Full Lifecycle Management
Revoke, Suspend, or Restore
Manage mdoc status with the IETF Token Status List.
Automated Trust
Verification Policies
Signature, validity, status and issuer certificate checks out of the box. Add custom rules or pass checks to your external systems via webhooks.
- Signature
- Credential status
- VICAL
- Custom
Trust Anchors
Issuer Identification
Identify mDL issuers through IACA and document signer certificates, and trust them via VICALs.
Partners And Integrations
Works With Your Infrastructure.
Seamlessly connect your existing stack and deploy anywhere with full flexibility and total data control.
Max Freedom, Zero Lock-in
Works with any KMS/HSM, database, cloud provider or application.
Product Editions
Build or Buy.
Build on top of the industry's leading open source stack or scale quickly with our secure, regulatory compliant enterprise solution.
Open Source
Community Stack
The easiest way to get started and build. Own infrastructure and develop your platform based on the leading open source stack.
Enterprise
Enterprise Stack
Everything you need to roll-out and scale. The fast and worry-free way to build ID platforms, ship complex use cases and ensure compliance.
FAQs
Frequently asked questions.
Answers to common questions about mobile driving licenses with walt.id.
Does walt.id support ISO/IEC 18013-5 mobile driving licenses?
Yes. walt.id issues, stores and verifies mobile driving licenses and other mdocs following ISO/IEC 18013-5 and the ISO/IEC 23220-2 mdoc data model, in both the open-source Community Stack and the Enterprise Stack.
Can mDLs be verified online?
Yes. walt.id supports ISO/IEC 18013-7 for remote presentation, both via OpenID4VP (Annex B) and via the Digital Credentials API (Annex C). In person, the walt.id mobile wallet presents mdocs via QR code or NFC, with the data sent over Bluetooth or NFC.
How does a verifier know an mDL is genuine?
The issuer signs each mDL with a document signer certificate that chains up to its IACA (Issuing Authority Certificate Authority). The walt.id Verifier checks this certificate chain against a VICAL, a signed list of trusted IACAs, together with the signature, validity and status.
How do I revoke or suspend an mDL?
With the IETF Token Status List. In the Community Stack you create and sign status lists and host and update them yourself; the Enterprise Stack manages the credential lifecycle, including status updates and publishing.
mDL, SD-JWT VC or W3C VC: which format should I use?
It depends on the ecosystem you need to work with. ISO mdoc is the format for mobile driving licenses, SD-JWT VC and ISO mdoc are the formats used for PID in the EU Digital Identity Wallet, and many other ecosystems build on the W3C data model. walt.id's Issuer, Wallet and Verifier support all three, so you don't have to choose up front. See SD-JWT VC and W3C Verifiable Credentials, or compare the formats in the docs.
Which key stores are supported?
Signing keys can stay in your preferred KMS or HSM, for example AWS KMS, Azure Key Vault, HashiCorp Vault or HSMs via the PKCS#11 interface, or be managed locally. This applies to both editions. For all supported key stores, see the feature list in the docs.
Is walt.id a hosted service?
No. Both editions, the open-source Community Stack and the Enterprise Stack, are self-managed: you run them on premises or in your own cloud. A fully managed Cloud Platform is not yet available. The public demos are for testing only.