light-mode-image
Learn
MobileSDKs

Verifier Mobile SDKs Overview

Overview

The mDocs Verifier SDK are based on the ISO/IEC 18013-5:2021 and ISO/IEC 18013-7:2025 standards, which establish an interoperable digital representation of mobile-based credentials such as mobile drivers licenses (mDL). However, these SDKs can extend the same technology and architecture to more than just mDLs, but rather any conforming mobile document (mDoc) - a term defined in ISO/IEC 18013-5.

The mDocs Verifier SDKs are available for React Native, iOS, and Android. They help developers add mDocs verification capabilities to their apps, allowing secure and privacy preserving verification of presented mDocs in various interoperable workflows.

To get started with any of our mDocs Verifier SDKs, please contact us.

SDK Capabilities

The mDocs Verifier SDKs offer tools to assist developers integrating the following capabilities into their applications:

  • Interface with an mDoc holder to request presentations of issued mDocs via:
    • Proximity verification: Verify an mDoc presented in-person as per ISO/IEC 18013-5:2021.
    • Remote mobile app verification: Remotely verify an mDoc presented from a different app installed on the same mobile device (as per ISO/IEC 18013-7:2025 and OID4VP).
  • Manage a list of trusted issuer certificates which presented mDocs can be validated against.
  • Manage status lists which can be used to check mDocs' revocation status.
  • Interface with an mDoc holder to request presentations of issued mDocs via:
    • Proximity verification: Verify an mDoc presented in-person as per ISO/IEC 18013-5:2021.
    • Remote mobile app verification: Remotely verify an mDoc presented from a different app installed on the same mobile device (as per ISO/IEC 18013-7:2025 and OID4VP).
  • Manage a list of trusted issuer certificates which presented mDocs can be validated against.
  • Manage status lists which can be used to check mDocs' revocation status.
  • Interface with an mDoc holder to request presentations of issued mDocs via:
  • Manage a list of trusted issuer certificates which presented mDocs can be validated against.
  • Manage status lists which can be used to check mDocs' revocation status.

Supported features

Supported ISO/IEC 18013-5 Features

Below is a summary of ISO/IEC 18013-5 features supported by the mDocs Verifier SDKs:

FeatureSupported optionsDefault
Device engagementQR codeQR code
Device retrieval data transportBLE with either mDocPeripheralServer or mDocCentralClient modeDetermined by holder application
Ephemeral session key curveAny NIST P-* keysDetermined by holder application
Device authentication modeDigital Signature or ECDH-agreed MACDetermined by holder application
FeatureSupported optionsDefault
Device engagementQR code and NFCQR code
Device retrieval data transportBLE with either mDocPeripheralServer or mDocCentralClient modeDetermined by holder application
Ephemeral session key curveAny NIST P-* keysDetermined by holder application
Device authentication modeDigital Signature or ECDH-agreed MACDetermined by holder application
FeatureSupported optionsDefault
Device engagementQR codeQR code
Device retrieval data transportBLE with either mDocPeripheralServer or mDocCentralClient modeDetermined by holder application
Ephemeral session key curveAny NIST P-* keysDetermined by holder application
Device authentication modeDigital Signature or ECDH-agreed MACDetermined by holder application

System requirements

The SDK is developed in the Swift programming language and is meant for integration into iOS applications developed in Swift and/or Objective-C. Specifically, it currently only supports applications developed in iOS 15 and above.

This SDK is developed in the Kotlin programming language and is meant for integration into Android applications. It currently supports Android 7 (API level 24) and above.

This SDK is meant for integration into React Native applications using React Native 0.78 and above. Supported operating systems are:

  • iOS 15 or higher.
  • Android 7 or higher.

Dependencies

This section lists all dependencies for using mDocs Verifier SDKs.

Third party dependencies

Apple frameworks

Toolchain dependencies

  • Swift 5.10.
  • iOS support: The SDK functionality is only available for devices from iOS 15 onwards.
  • Xcode: The SDK is built with the latest stable Xcode available in GitHub Actions (setup-xcode action with latest-stable label). The current version is Xcode 26.0.0 (17A324).
  • macOS 15.

Kotlin, AGP, Gradle, and Android Studio

The Android Verifier SDK is built using Kotlin 2.0. This adds some intrinsic dependencies into your build tools.

  • Kotlin 2.0 is supported from AGP version 8.5.
  • AGP 8.5 is supported from Gradle version 8.7 and Android Studio Koala 2024.1.1.

Runtime

A list of runtime dependencies and licenses is generated at build time and packaged in res/raw/dependencies_licenses.html. The majority are Kotlin and Android, the rest are listed below:

Standard libraries

Third-party libraries

  • None.

Versions

Below are the available versions of the mDocs Verifier Mobile SDKs, including the current active version, supported versions, and those that have reached end-of-life (EOL).

Major versionStatusLatest releaseEnd of Life dateDocumentation
v5Active5.0.0-SDK Docs
v4Maintenance4.1.013-05-2026SDK Docs
v3End of Life3.0.07-10-2025-
v2End of Life2.0.026-08-2025-
v1End of Life1.0.105-05-2025-
Major versionStatusLatest releaseEnd of Life dateDocumentation
v6Active6.0.0-SDK Docs
v5Maintenance5.3.213-05-2026SDK Docs
v4End of Life4.1.130-12-2025-
v3End of Life3.0.07-10-2025-
v2End of Life2.0.026-08-2025-
v1End of Life1.0.105-05-2025-
Major versionStatusLatest releaseEnd of Life dateDocumentation
v8Active8.1.1-SDK Docs
v7End of Life7.1.012-12-2025-
v6End of Life6.0.026-08-2025-
v5End of Life5.0.005-05-2025-
v4End of Life4.1.113-04-2025-
v3End of Life3.0.015-02-2025-
v2End of Life2.0.017-12-2024-
v1End of Life1.0.105-07-2024-

Release candidates (RC) are pre-release versions that may contain new features or changes that are not yet fully tested. They are intended for testing purposes, are not subject to our SLA and should not be used in production environments.

How would you rate this page?

Last updated on

On this page