MATTR Pi mDocs Holder SDKs Overview
Overview
The mDocs Holder SDKs are based on the ISO/IEC 18013-5 standard which establishes 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 Holder SDKs are available for React Native, iOS, and Android. They help developers add mDocs holding features to their apps, allowing users to securely claim and present mDocs in various interoperable workflows.
To get started with any of our mDocs Holder SDKs, please contact us.
SDK Capabilities
The mDocs Holder SDKs offer tools to assist developers integrating the following capabilities into their applications:
-
Claim an mDoc
- Interact with a credential offer and claim an mDoc as per OpenID4VCI (OpenID for Verifiable Credential Issuance). The SDK supports both the Authorization Code and Pre-authorized Code flows.
- Manage a list of trusted issuers which mDoc offers can be validated against.
- Store claimed mDocs and manage access to that storage.
- Manage access to device keys which are bound to issued mDocs.
- Use referenced Status lists to check mDocs' revocation status.
-
Present an mDoc
- Present a claimed mDoc for verification via a proximity presentation workflow as per ISO 18013-5.
- Present a claimed mDoc for verification remotely as per ISO/IEC 18013-7:2025 and OID4VP.
-
Claim an mDoc
- Interact with a credential offer and claim an mDoc as per OpenID4VCI (OpenID for Verifiable Credential Issuance). The SDK supports both the Authorization Code and Pre-authorized Code flows.
- Manage a list of trusted issuers which mDoc offers can be validated against.
- Store claimed mDocs and manage access to that storage.
- Manage access to device keys which are bound to issued mDocs.
- Use referenced Status lists to check mDocs' revocation status.
-
Present an mDoc
- Present a claimed mDoc for verification via a proximity presentation workflow as per ISO 18013-5.
- Present a claimed mDoc for verification remotely as per ISO/IEC 18013-7:2025 and OID4VP.
-
Claim an mDoc
- Interact with a credential offer and claim an mDoc as per OpenID4VCI (OpenID for Verifiable Credential Issuance). The SDK supports the Authorization Code flow.
- Manage a list of trusted issuers which mDoc offers can be validated against.
- Store claimed mDocs and manage access to that storage.
- Manage access to device keys which are bound to issued mDocs.
- Use referenced Status lists to check mDocs' revocation status.
-
Present an mDoc
- Present a claimed mDoc for verification via a proximity presentation workflow as per ISO 18013-5.
- Present a claimed mDoc for verification remotely as per ISO/IEC 18013-7:2025 and OID4VP.
Supported features
ISO/IEC 18013-5
Below is a summary of ISO/IEC 18013-5:2021 features supported by the mDocs Holder SDKs:
| Feature | Supported options | Default |
|---|---|---|
| Device engagement | QR code | QR code |
| Device retrieval data transport | BLE with either mDocPeripheralServer or mDocCentralClient mode | BLE with mDocPeripheralServer |
| Ephemeral session key curve | Any NIST P-* keys | P-256 key using secure enclave |
| Device authentication mode | Digital Signature or ECDH-agreed MAC | Digital Signature with a P-256 key using secure enclave |
| Feature | Supported options | Default |
|---|---|---|
| Device engagement | QR code | QR code |
| Device retrieval data transport | BLE with either mDocPeripheralServer or mDocCentralClient mode | BLE with mDocPeripheralServer |
| Ephemeral session key curve | Any NIST P-* keys | P-256 key using secure enclave |
| Device authentication mode | Digital Signature or ECDH-agreed MAC | Digital Signature with a P-256 key using secure enclave |
| Feature | Supported options | Default |
|---|---|---|
| Device engagement | QR code | QR code |
| Device retrieval data transport | BLE with either mDocPeripheralServer or mDocCentralClient mode | BLE with mDocPeripheralServer |
| Ephemeral session key curve | Any NIST P-* keys | P-256 key using secure enclave |
| Device authentication mode | Digital Signature or ECDH-agreed MAC | Digital Signature with a P-256 key using secure enclave |
ISO/IEC 18013-7
Below is a summary of ISO/IEC 18013-7:2025 features supported by the mDocs Holder SDKs:
| Feature | Options Supported | Default Option Selected |
|---|---|---|
| Data Retrieval methods | OID4VP | OID4VP |
| Wallet Invocation | Custom URL and QR Code-based | Both |
| MDoc Reader validation | Stored verifier certificates, client Metadata retrieval | Both |
| Authorization Response Encryption | ECDH in Direct Key Agreement mode | ECDH in Direct Key Agreement mode |
| Feature | Options Supported | Default Option Selected |
|---|---|---|
| Data Retrieval methods | OID4VP | OID4VP |
| Wallet Invocation | Custom URL and QR Code-based | Both |
| MDoc Reader validation | Stored verifier certificates, client Metadata retrieval | Both |
| Authorization Response Encryption | ECDH in Direct Key Agreement mode | ECDH in Direct Key Agreement mode |
| Feature | Options Supported | Default Option Selected |
|---|---|---|
| Data Retrieval methods | OID4VP | OID4VP |
| Wallet Invocation | Custom URL and QR Code-based | Both |
| MDoc Reader validation | Stored verifier certificates, client Metadata retrieval | Both |
| Authorization Response Encryption | ECDH in Direct Key Agreement mode | ECDH in Direct Key Agreement mode |
System requirements
The iOS mDocs Holder 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.
While the SDK functionalities are only available for devices from iOS 15 and onwards, the minimum deployment target is currently set to iOS 13. This enables clients to support users up to iOS 13, as long as the SDK is not initialized.
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.
While the SDK functionalities are only available for devices from iOS 15 and onwards, the minimum deployment target is currently set to iOS 13. This enables clients to support users up to iOS 13, as long as the SDK is not initialized.
Dependencies
This section lists all dependencies for using mDocs Holder SDKs.
Third party dependencies
- CBORCoding (MIT license).
- swift-certificates 1.7.0 (Apache-2.0 License).
- swift-asn1 1.3.1 (Apache-2.0 License).
Apple Frameworks
- Security Framework.
- CryptoKit Framework.
- LocalAuthentication Framework.
- AuthenticationServices Framework.
- CoreBluetooth Framework.
- Combine Framework.
- OSLog Framework.
- UIKit Framework.
- AppKit Framework (on macOS).
Toolchain dependencies
- Swift 5.10.
- iOS support:
- The SDK functionality is only available for devices from iOS 15 onwards.
- The minimum deployment target is set to iOS 13 so that clients can continue support end users up to iOS 13 without initializing the SDK.
- Xcode: The SDK was built with the latest stable Xcode available in GitHub Actions (setup-xcode action with latest-stable label), and the current version is Xcode Xcode 16.3.0 (16E140).
- macOS 15.
Standard libraries
androidx.core:core-ktx:1.13.1androidx.appcompat:appcompat:1.7.0androidx.activity:activity-ktx:1.9.0androidx.fragment:fragment:1.5.4androidx.annotation:annotation:1.8.0androidx.biometric:biometric-ktx:1.2.0-alpha05androidx.browser:browser:1.8.0org.jetbrains.kotlin:kotlin-reflect:1.9.22org.jetbrains.kotlinx:kotlinx-coroutines-core:1.7.3org.jetbrains.kotlinx:kotlinx-datetime:0.4.0org.jetbrains.kotlinx:kotlinx-serialization-json:1.6.3
Third-party libraries
com.upokecenter:cbor:4.2.0com.jakewharton.timber:timber:5.0.1
- None.
Versions
Below are the available versions of the mDocs Holder SDKs, including the current active version, supported versions, and those that have reached end-of-life (EOL).
| Major version | Status | Latest release | End of Life date | Documentation |
|---|---|---|---|---|
| v4 | Active | 4.2.0 | - | SDK Docs |
| v3 | End of Life | 3.0.0 | 7-10-2025 | - |
| v2 | End of Life | 2.0.0 | 26-08-2025 | - |
| v1 | End of Life | 1.0.0 | 05-05-2025 | - |
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?