light-mode-image
Learn
Mobile

Remote mobile verification quickstart guide

This guide provides a quick overview of how to use the MATTR Pi mDocs Mobile Verifier SDKs to verify an mDoc presented from another application on the same device via a remote presentation workflow as per OID4VP and ISO 18013-7 Annex B.

Use these guides as a quick reference to get started. For detailed information, explore the tutorial and reference documentation tailored for each platform.

Setup the MATTR VII Verifier tenant

Before embedding the Verifier SDK in your mobile application, you must configure your MATTR VII tenant to handle verification requests.

Create a verifier application configuration

  1. Log into the MATTR Portal.
  2. Navigate to Credential Verification > Applications.
  3. Select Create new.
  4. Enter a meaningful name for your application.
  5. Select the application type (e.g., iOS or Android).
  6. Enter your Team ID (iOS) or Package Name (Android).
  7. Enter your application Bundle ID (iOS) or SHA-256 fingerprint (Android).
  8. In the OpenID4VP Configuration section, enter your Redirect URI (e.g., {your_app_bundleId}://my/path).
  9. Select Create.
  10. Make note of the generated application ID. You will need this value to initialize the SDK in your mobile application.
  1. Log in to the MATTR Portal.
  2. In the navigation panel on the left-hand side, expand the Credential Verification menu.
  3. Select Applications.
  4. Select Create new.
  5. Enter a meaningful Name for your application (e.g. "My Android Mobile Verifier Application").
  6. Use the Type dropdown to select Android as you are building an Android application.
  7. In the Package Name field, enter your Android application package name. This is the unique identifier of your Android application, which must match the package name you set later in this tutorial.
  8. In the Signing certificate thumbprints field, enter a temporary placeholder value (e.g. 3A9F6C1D4E8B72F0A5C3D6E19B4F8A2C7D1E0B9F3A6C5D4E7B8F2A1C9D0E3F5B). MATTR VII uses this to verify requests come from your signed app. You will update the placeholder value after you retrieve the signing certificate in Step 1: Environment setup.
  9. In the OpenID4VP configuration section, enter a redirect URI in the Redirect URI field. This is the URI used to return the user to your app after the wallet presents the credential. It must resolve to a path your app can handle (via custom URI scheme or web page). In this tutorial you'll use a custom scheme based on your package name: {your_app_packageName}://oid4vp-callback.
  10. Select Create.
  11. Make note of the generated application ID. You will need this value to initialize the SDK in your mobile application.

Configure a trusted issuer

  1. Expand the Credential Verification section in the left-hand navigation panel.
  2. Select Trusted issuers.
  3. Select the Create new button.
  4. Use the Certificate PEM file to upload the public key certificate of the issuer you want to trust.
  5. Select the Add button to add the new trusted issuer.

Embed the Verifier SDK in your mobile application

Initialize the SDK

Create platform configuration
let platformConfiguration = PlatformConfiguration(
    tenantHost: URL(string: "https://your-tenant.vii.mattr.global")!
)
Initialize the SDK
mobileCredentialVerifier = MobileCredentialVerifier.shared
try mobileCredentialVerifier.initialize(platformConfiguration: platformConfiguration)
  • tenantHost : URL of your MATTR VII tenant.
Create platform configuration
val platformConfiguration = PlatformConfiguration(
    tenantHost = URL("https://your-tenant.vii.mattr.global")
)
Initialize the SDK
MobileCredentialVerifier.initialize(context, platformConfiguration)
  • tenantHost : URL of your MATTR VII tenant.

Coming soon...

Create a presentation request

Create a presentation request
let mobileCredentialRequest = MobileCredentialRequest(
    docType: "org.iso.18013.5.1.mDL",
    namespaces: [
        "org.iso.18013.5.1": [
            "family_name": false,
            "given_name": false,
            "birth_date": false
        ]
    ]
)
  • docType : The type of credential being requested (e.g., org.iso.18013.5.1.mDL).
  • namespaces : A dictionary mapping each namespace to its requested attributes. Each attribute is a key with a Boolean indicating whether the verifier intends to retain this attribute (true) or not (false).
Create a presentation request
val mobileCredentialRequest = MobileCredentialRequest(
    docType = "org.iso.18013.5.1.mDL", namespaces = NameSpaces(
        mapOf(
            "org.iso.18013.5.1" to DataElements(
                mapOf(
                    "family_name" to false, "given_name" to false, "birth_date" to false
                )
            )
        )
    )
)
  • docType : The type of credential being requested (e.g., org.iso.18013.5.1.mDL).
  • namespaces : A map of each namespace to its requested attributes. Each attribute is a key with a Boolean indicating whether the verifier intends to retain this attribute (true) or not (false).

Coming soon...

Request credentials from wallet application

Request credentials
let onlinePresentationResult = try await mobileCredentialVerifier.requestMobileCredentials(
    request: [mobileCredentialRequest],
    challenge: UUID().uuidString,
    applicationId: "your-application-id"
)
  • request : Array of MobileCredentialRequest objects defining what information to request.
  • challenge : Unique challenge to identify this presentation session and prevent replay attacks. Generate a new challenge for every request.
  • applicationId : The id returned when you created the verifier application configuration.

This method starts a presentation session with the MATTR VII tenant and redirects the user to a matching wallet application.

Request credentials
val onlinePresentationResult = mobileCredentialVerifier.requestMobileCredentials(
    activity = activity,
    request = listOf(mobileCredentialRequest),
    applicationId = "your-application-id"
)
  • activity : Defines the current activity context.
  • request : List of MobileCredentialRequest objects defining what information to request.
  • applicationId : The id returned when you created the verifier application configuration.

This method starts a presentation session with the MATTR VII tenant and redirects the user to a matching wallet application.

Coming soon...

Register a custom URL scheme

To handle redirects back to your application after credential presentation, register a custom URL scheme.

  1. Open your project in Xcode and select your application target.
  2. Select the Info tab.
  3. Expand the URL Types section.
  4. Select the plus button.
  5. Enter your bundle identifier in both the Identifier and URL Schemes fields.

This must match the redirectUri configured in your verifier application configuration.

To handle redirects back to your application after credential presentation, configure an intent filter in your AndroidManifest.xml:

AndroidManifest.xml
<intent-filter>
    <action android:name="android.intent.action.VIEW" />
    <category android:name="android.intent.category.DEFAULT" />
    <category android:name="android.intent.category.BROWSABLE" />
    <data
        android:scheme="your-package-name"
        android:host="oid4vp-callback" />
</intent-filter>

This must match the redirectUri configured in your verifier application configuration.

Coming soon...

Handle the redirect from the wallet

Handle redirect URL
.onOpenURL { url in
    mobileCredentialVerifier.handleDeepLink(url)
}

Add this modifier to your SwiftUI view to handle the redirect from the wallet application. The SDK processes the response and updates your application with the verification results.

The SDK processes the response with the verification results.

Coming soon...

Handle the presentation response

The requestMobileCredentials method returns an OnlinePresentationSessionResult object. This response contains the presentation details provided by the holder, including any errors encountered and the verification status of the credentials:

OnlinePresentationSessionResult structure
public struct OnlinePresentationSessionResult {
    public let mobileCredentialResponse: MobileCredentialResponse?
    public let error: OnlinePresentationResultError?
    public let challenge: String?
    public let sessionId: String
}
Handle the response
guard let receivedCredentials = onlinePresentationSessionResult.mobileCredentialResponse?.credentials else {
    let errorMessage = onlinePresentationSessionResult.error?.message ?? "No error message"
    print("No response received: \(errorMessage)")
    return
}

// Process the received credentials
for credential in receivedCredentials {
    print("DocType: \(credential.docType)")
    print("Verified: \(credential.verificationResult.verified)")
    
    if let claims = credential.claims {
        for (namespace, elements) in claims {
            for (elementId, value) in elements {
                print("\(namespace).\(elementId): \(value)")
            }
        }
    }
}
  • mobileCredentialResponse : Contains the verified credentials and their claims.
  • error : Any error that occurred during the verification process.
  • credentials : A list of presented credentials with their data, status, and verification results.

The requestMobileCredentials method returns an OnlinePresentationSessionResult) object. This response contains the presentation details provided by the holder, including any errors encountered and the verification status of the credentials:

OnlinePresentationSessionResult structure
data class OnlinePresentationSessionResult(
    val sessionId: String,
    val challenge: String? = null,
    val mobileCredentialResponse: MobileCredentialResponse? = null,
    val error: OnlinePresentationResultError? = null
)
Handle the response
val receivedCredentials = onlinePresentationResult.mobileCredentialResponse?.credentials
if (receivedCredentials == null) {
    val errorMessage = onlinePresentationResult.error?.message ?: "No error message"
    println("No response received: $errorMessage")
    return
}

// Process the received credentials
for (credential in receivedCredentials) {
    println("DocType: ${credential.docType}")
    println("Verified: ${credential.verificationResult.verified}")
    
    credential.claims?.forEach { (namespace, elements) ->
        elements.forEach { (elementId, value) ->
            println("$namespace.$elementId: ${value.value}")
        }
    }
}
  • mobileCredentialResponse : Contains the verified credentials and their claims.
  • error : Any error that occurred during the verification process.
  • credentials : A list of presented credentials with their data, status, and verification results.

Coming soon...

Next steps

How would you rate this page?

On this page