Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
ISO/IEC 18013-5 mobile IDs and NFC smart cards are not interchangeable credentials. An mDL (mobile driving licence) defines a digital data model, cryptographic trust and reader/issuer interfaces; an NFC card is a physical contactless credential whose security depends on its chip, issuer profile and reader. An mDL can use NFC for device engagement, but an NFC reader alone cannot be assumed to read or validate an mDL. In practice, mDLs offer strong origin authentication, integrity checks and potentially data-minimising presentations, while cards provide a battery-independent, familiar form factor. The safer and more compatible choice depends on the deployment, trust configuration, legal rules and fallback procedures.
At a glance
| Name | Best for | Key spec | Checked |
|---|---|---|---|
| ISO/IEC 18013-5 mobile driving licence (mDL) | Machine-verifiable digital presentations with holder binding and cryptographic checks | mDL data and interfaces defined by ISO/IEC 18013-5:2021; engagement and retrieval depend on the profile and implementation | November 2026 |
| NFC smart card | Card-present, battery-free contactless identification | Typically ISO/IEC 14443 contactless communication plus chip and issuer security controls; ISO/IEC 18013-5 compliance is separate | November 2026 |
What does ISO/IEC 18013-5 actually define?
ISO/IEC 18013-5:2021 specifies a mobile driving-licence (mDL) application and the interfaces among the mDL, an mDL reader and issuer infrastructure. Its stated purpose is to let a machine obtain mDL data, tie that data to the person holding the mDL, authenticate the data’s origin and verify its integrity. Those are protocol and trust functions, not a guarantee that every phone, reader or government accepts every digital licence.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
The 2021 edition was published in September 2021 and is 152 pages in the ISO catalogue. ISO is developing ISO/IEC DIS 18013-5, second edition, intended to replace the 2021 edition. A draft is not the same as a final, universally deployed profile, so a project should identify the edition and national implementation it supports.
The standard also draws boundaries. It does not prescribe how an mDL holder’s consent is obtained or set requirements for storing mDL data and private keys. Those controls are supplied by the wallet, phone operating system, issuing authority and deployment policy. A claim that an mDL is automatically private or secure merely because it follows ISO/IEC 18013-5 therefore goes beyond the standard.
Popular on Amazon
Is an ISO 18013-5 mobile ID safer than an NFC card?
Neither format is universally safer. An mDL has standardized mechanisms for authenticating origin and checking data integrity, while a smart card can use a hardened chip, protected key storage and mature contactless controls. The resulting assurance depends on implementation, key management, reader configuration, issuer practices and the verifier’s ability to match the credential to its presenter.
| Security question | mDL | NFC smart card |
|---|---|---|
| Can the verifier check who issued the data? | Yes, through the mDL origin-authentication and trust mechanisms when correctly configured. | Depends on the card technology, issuer profile and authentication protocol; NFC by itself says nothing about issuer authentication. |
| Can altered data be detected? | Integrity verification is part of the mDL design. | Depends on chip cryptography and the card scheme; a plain NFC data exchange is not proof of integrity. |
| Where are private keys protected? | Storage requirements are outside the 2021 standard and rely on the wallet, operating system and issuer deployment. | Often in secure chip hardware, but the exact assurance varies by card, personalization and national rules. |
| Is holder consent specified? | No. Consent UX and policy are deployment responsibilities. | Usually expressed through physically presenting the card and the verifier’s process; detailed privacy behavior is jurisdiction-specific. |
| Can conformance be tested? | ISO/IEC TS 18013-6:2025 defines mDL and reader conformity test methods, including an optional reader-to-issuer interface. | Testing follows the card scheme and applicable national or industry rules; generic NFC support is not an ISO/IEC 18013-5 test result. |
For an mDL, a verifier should validate the issuer’s certificate chain, check signatures and validity information, enforce the approved data elements and confirm that the person presenting the phone is the holder. For a card, it should use the card scheme’s authentication and key-diversification procedures rather than treating the card’s identifier or readable fields as trustworthy on their own.
What security does an NFC smart card provide?
An NFC smart card is a physical contactless credential. It communicates over a short-range radio interface, commonly an ISO/IEC 14443 family interface, and can contain a secure integrated circuit that performs cryptographic operations without exposing private keys. European rules for licences with storage media reference ISO/IEC 14443 interfaces, ISO/IEC 18013 data-protection mechanisms and smart-card testing; the European Commission regulation is a useful example of how a jurisdiction can combine those requirements.
That description does not make every contactless card equivalent. A card may expose only a serial number, use static data, or implement a stronger challenge-response protocol. The issuer’s personalization, certificate lifecycle, reader’s trusted keys and local law determine the real assurance. Skimming resistance, mutual authentication, counters, PIN rules and revocation behavior must be checked in the card scheme documentation.
Cards have practical security advantages: they do not need a battery, an app or a network connection at the point of presentation, and a lost phone cannot be remotely unlocked by guessing a device passcode. They also have risks: a card can be lost or copied if its scheme lacks effective cryptographic protection, and a verifier may collect more data than necessary if the card presents a fixed record rather than allowing a tailored disclosure.
How does an mDL transaction differ from a card transaction?
An mDL transaction is a coordinated exchange among a mobile device, a reader and, in some deployments, issuer infrastructure. A card transaction is usually a card-present exchange between a chip and a reader, with online authorization or revocation checks added when required. The radio technology is only one layer in either case.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Also popular on Amazon
- Engagement: The reader and the credential discover each other. The engagement channel may be NFC, a QR code or another method allowed by the profile. The draft second edition lists NFC and QR for device engagement.
- Session setup: The mDL and reader negotiate the data retrieval session and cryptographic parameters. For the draft second edition, Bluetooth Low Energy is listed for data retrieval; an implementation must state which edition and profile it supports.
- Request: The verifier requests specific data elements. The request should be limited to what the transaction legally needs.
- Holder decision: The wallet presents the request to the holder according to its consent design. ISO/IEC 18013-5 does not dictate that user interface or storage policy.
- Response and verification: The reader receives an mdoc, validates issuer signatures and integrity, checks freshness or validity information as required, and applies its trust list.
- Person matching: The verifier compares the received attributes and portrait or other approved evidence with the person present. ISO/IEC TS 18013-7:2024 explicitly places this responsibility on the mDL verifier, including internet-presented transactions.
For a card, the reader powers the chip through the contactless field, selects the relevant application, performs the scheme’s authentication and reads the permitted records. There is no assumption that a phone wallet, QR engagement or BLE session exists.
Can an NFC reader read a mobile driving licence?
Only if the reader and mDL implementation support the same engagement method, data model, cryptographic trust configuration and retrieval protocol. NFC capability alone is not enough. An NFC reader designed for an ISO/IEC 14443 smart-card application may not understand an mDL engagement message, mdoc structure or issuer trust list.
An mDL may use NFC as the initial tap, but the rest of the exchange can move to another channel. Conversely, an mDL wallet may offer QR engagement or another approved path. Before buying hardware, obtain the issuer or wallet’s exact profile, supported ISO edition, engagement channels, BLE requirements, certificate format and offline behavior.
Compatibility should be demonstrated at five layers:
- Data model: The reader understands the mDL namespaces and requested data elements, rather than only card files.
- Engagement: NFC, QR or another channel is implemented on both sides.
- Transport: The chosen channel, including BLE where required, is supported and permitted by the operating system.
- Trust: The verifier has current issuer certificates, revocation information and policy for unknown or expired keys.
- Application: The issuing authority and verifier have agreed on legal fields, user consent and audit handling.
What hardware and software does a verifier need?
A basic mDL verifier needs a compatible reader application, a phone or reader with the engagement and transport capabilities required by the selected profile, and a secure trust-store update process. If the transaction uses BLE after NFC or QR engagement, the device must support BLE and allow the verifier application to manage that session. An internet connection may be needed for issuer or revocation checks, but an implementation should document what can be verified offline.
A card verifier needs an ISO/IEC 14443-capable contactless reader and software for the particular card application. A USB NFC reader can be suitable for inspection or development, but the product description should be checked for supported protocols, secure messaging, PC/SC behavior, operating-system drivers and the card scheme’s test requirements. A reader that reports an NFC UID is not automatically an identity verifier.
Also popular on Amazon
For production, use the conformity approach in ISO/IEC TS 18013-6:2025 for the mDL and reader, and retain evidence of issuer, reader and optional reader-to-issuer interface testing. Keep test evidence separate from a generic statement such as “NFC supported.”
Which format is better for privacy?
An mDL can support a more selective transaction because the verifier can request defined data elements instead of receiving a fixed card record. That benefit appears only when the wallet, issuer profile and verifier enforce data minimisation and provide a clear consent screen. The verifier’s logs, screenshots, analytics and retention settings can still reveal more than the presentation itself.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesA smart card is easier to use consistently at a physical counter, but many card profiles expose a relatively stable set of fields. A verifier should read only authorized fields, avoid retaining raw card dumps and protect any images or document numbers it stores. Privacy obligations come from local law and the credential scheme, not from the presence of an NFC antenna.
For online presentation, TS 18013-7:2024 adds internet functions but does not remove the verifier’s duty to match received data to the person presenting the document. A remote flow therefore needs a separate identity-binding step, fraud controls and a policy for unattended or delegated presentations.
What happens when the phone, card or network is unavailable?
A card works without a battery and is usually the simplest fallback for a dead or damaged phone. An mDL depends on the phone being powered, unlocked as required by the wallet, in a usable state and still holding valid credential data. A robust issuer should provide recovery after phone loss, device replacement and wallet restoration, with revocation for the old device or credential.
Offline operation is not a single feature. The verifier may be able to authenticate a signed mdoc offline while lacking current revocation or status information. The card may support offline chip authentication while the jurisdiction still requires an online check for certain decisions. Document which checks are mandatory, which are advisory and what happens when connectivity returns.
Also popular on Amazon
Fallback policy should cover at least: no battery, broken screen, lost device, unavailable BLE, expired issuer certificates, unknown credential version, failed biometric or passcode unlock, and a card presented after an mDL was revoked. Staff need a clear escalation path rather than an informal decision to accept an unverified screenshot.
How do issuance, renewal and revocation differ?
Issuing an mDL involves binding a digital credential to a holder and a device or wallet, delivering issuer keys and certificates, and maintaining software and trust-list updates. Renewal can be pushed to the wallet, but a device change or operating-system migration may require re-enrolment. Revocation can target the credential, device binding or issuer certificate, subject to the deployment’s status mechanism.
Issuing a smart card involves manufacturing or personalizing a chip, loading keys and certificates, distributing the card and managing replacement. Renewal normally means producing a new physical credential. Revocation may rely on online status checks, hotlists, chip counters or other scheme mechanisms. Reader fleets must be updated for new card profiles and certificate authorities.
Operations teams should maintain an inventory of supported editions and profiles, a certificate-rotation schedule, incident procedures for compromised keys, and a method to reject retired credentials. The mDL standard does not eliminate these lifecycle duties; it makes the interfaces and data checks more explicit.
Recommended Free Tools
Does ISO/IEC 18013-5 compliance mean a device is legally accepted?
No. ISO/IEC 18013-5 is a technical standard, not a worldwide acceptance rule. A jurisdiction must authorize mDL use, specify which attributes and readers are accepted, and define whether a verifier may rely on offline or internet presentation. The same applies to cards: an ISO/IEC 14443 interface does not prove that a card is a legally recognized driving licence.
Check the issuing authority’s approved wallet, the verifier’s authorization, the accepted document types and the transaction’s geography. A cross-border verifier may need the issuer’s trust anchor and a local legal basis before accepting an mDL from another country. Keep legal approval and technical conformance as separate gates in procurement.
Also popular on Amazon
How should an organization choose between mDL and NFC cards?
Choose an mDL-first flow when the service benefits from machine-verifiable signatures, controlled data requests, digital issuance and a smartphone-based user journey. Choose a card-first flow when battery independence, rapid counter transactions and broad existing reader support are the priority. Many deployments should support both, with explicit rules for which checks each channel can satisfy.
| Requirement | Usually favors mDL | Usually favors NFC card |
|---|---|---|
| Selective data requests | Yes, if the wallet and profile implement them. | Less flexible when the card presents a fixed record. |
| Battery-free operation | No; phone availability is required. | Yes. |
| Remote or internet presentation | Supported through the TS 18013-7 add-on and a compliant verifier flow. | Not inherent to a card-present interface. |
| Existing contactless reader estate | Requires mDL-aware software and possibly BLE support. | May fit, but only when the reader supports the card’s application and security profile. |
| Centralized software updates | Wallet and verifier updates can be managed digitally, with change-control risk. | Cards remain stable, but readers and trust lists still need maintenance. |
| Failure recovery | Requires device-loss, wallet-restoration and certificate procedures. | Requires replacement-card and revocation procedures. |
Implementation checklist for an mDL verifier
- Record the exact ISO edition, national profile and issuer(s) you will accept.
- List supported engagement channels: NFC, QR and any other approved method.
- Confirm transport support, including BLE if the selected profile uses it.
- Load and rotate issuer certificates, revocation data and trust lists securely.
- Implement signature, origin, integrity and validity checks before displaying a pass result.
- Request only the data elements authorized for the transaction.
- Provide a holder-consent screen and document what is logged and retained.
- Match the received data to the person presenting the mDL, as required by the verifier’s responsibility.
- Test failure states: expired credential, unknown issuer, altered data, revoked device, interrupted BLE and no network.
- Keep conformity evidence aligned with ISO/IEC TS 18013-6:2025 and the jurisdiction’s approval process.
Implementation checklist for an NFC-card verifier
- Identify the card application and authentication scheme; do not rely on an NFC UID.
- Verify reader support for the required ISO/IEC 14443 mode, secure messaging and drivers.
- Install the card scheme’s issuer keys, certificates and status data using protected administration.
- Enforce chip authentication and integrity checks before accepting fields.
- Define online and offline decision rules, including stale status data.
- Limit field reads and retention to the legal purpose.
- Maintain reader firmware, trust lists and card-profile updates.
- Provide a fallback for damaged, expired or revoked cards without bypassing verification.
Common misconceptions and fixes
- “NFC means ISO 18013-5.” NFC is a transport or engagement capability. Fix: verify the mDL data model, protocol, trust configuration and conformance evidence.
- “Any phone can verify an mDL.” Fix: check the wallet, operating-system permissions, engagement channel, BLE support and reader application.
- “A readable card number proves identity.” Fix: require the card scheme’s cryptographic authentication and match the card to its presenter.
- “The standard guarantees consent and key storage.” Fix: audit wallet, operating-system and issuer controls because those subjects are outside the 2021 document’s scope.
- “A screenshot is an mDL.” Fix: accept only a live, protocol-compliant presentation that produces verifiable data and a holder match.
- “Online presentation removes the need for person matching.” Fix: apply the TS 18013-7 requirement to match received data to the presenting person.
What changed in the standards by November 2026?
ISO/IEC 18013-5:2021 remains the published first edition. The second edition, ISO/IEC DIS 18013-5, is under development and is intended to replace it; projects should not silently mix draft behavior with a 2021 implementation. ISO/IEC TS 18013-6:2025 adds conformity test methods, while ISO/IEC TS 18013-7:2024 adds internet presentation functions.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11No authoritative, broadly applicable adoption rate, attack rate, latency or cost figure establishes one format as universally superior. Decisions should therefore be based on the documented profile, threat model, legal authorization, fallback needs and verified interoperability rather than an invented headline number.
Bottom line
An ISO/IEC 18013-5 mDL is a cryptographically structured digital credential, not simply an NFC card stored in a phone. It can provide strong origin and integrity verification and a more controlled data request, but consent, private-key storage, holder matching and legal acceptance remain deployment responsibilities. An NFC smart card offers battery-free, card-present operation and can be highly secure when its chip and scheme are properly designed, yet NFC alone proves neither ISO/IEC 18013-5 compliance nor identity. Treat the two as different credential systems, verify every protocol and trust dependency, and keep a documented fallback for the failures each format can encounter.
Frequently Asked Questions
Can I use a normal contactless bank-card reader to verify an mDL?
Not reliably. A payment or generic ISO/IEC 14443 reader may lack the mDL application, engagement protocol, BLE hand-off, issuer certificates and verification logic required for an mDL transaction. The reader vendor and issuing authority must specify profile-level interoperability.
What should happen if an mDL wallet shows a valid-looking screen but the cryptographic exchange fails?
Treat the presentation as unverified and follow the deployment’s fallback procedure, such as requesting an approved physical credential or directing the person to a staffed channel. Visual inspection of a screen or screenshot is not a substitute for signature, integrity and holder checks.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Can an mDL be verified with no internet connection?
Some profiles can validate signed data offline, but current revocation or status information may still require connectivity. The issuer and verifier must define which checks are mandatory offline and how stale trust data is handled.
Who is responsible for matching an online mDL presentation to the person using it?
The verifier is responsible. ISO/IEC TS 18013-7:2024 makes that responsibility explicit, so a remote service needs its own person-matching and fraud controls rather than assuming the mDL protocol performs that step automatically.
Does replacing a phone automatically revoke the old mDL?
Not necessarily. Revocation and re-enrolment behavior is set by the issuer and wallet deployment. A secure program should support device-loss reporting, old-device invalidation and issuance of a new device binding.

