Remote mobile verification quickstart guide

1. Log into the MATTR Portal.
2. Expand the Credential Verification menu in the left-hand navigation panel.
3. Select Applications.
4. Select Create new.
5. Enter a meaningful Name for your application (e.g. "My iOS Mobile Verifier Application").
6. Use the Type dropdown to select iOS.
7. Enter your Apple Developer Team ID in the Team ID field. You can find it in the Membership details section of your Apple Developer account. For this evaluation the value is not validated, so if you don't have it to hand you can enter any suitably formatted placeholder string (e.g. ABCDE12345) to continue.
8. Enter the bundle identifier you will use for the sample app in the Bundle ID field (e.g. com.yourname.mobileverifier). You will set this same value on the sample app in Part 2.
9. In the OID4VP configuration section, enter a redirect URI structured as {your_app_bundleId}://my/path (e.g. com.yourname.mobileverifier://my/path). This is the URI the user is redirected to after presenting the credential from their wallet.
10. Select Create.
11. Make note of the generated application ID. You will use this value to configure the sample app later.

1. Log into the MATTR Portal.
2. Expand the Credential Verification menu in the left-hand navigation panel.
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.
7. Enter the package name you will use for the sample app in the Package Name field (e.g. com.yourname.mobileverifier). You will set this same value on the sample app in Part 2.
8. In the Signing certificate thumbprints field, enter a temporary placeholder value (e.g. 3A9F6C1D4E8B72F0A5C3D6E19B4F8A2C7D1E0B9F3A6C5D4E7B8F2A1C9D0E3F5B). You will update this with your app's real signing certificate thumbprint in Part 2.
9. In the OID4VP configuration section, enter a redirect URI structured as {your_app_packageName}://oid4vp-callback (e.g. com.yourname.mobileverifier://oid4vp-callback). This is the URI the user is redirected to after presenting the credential from their wallet.
10. Select Create.
11. Make note of the generated application ID. You will use this value to configure the sample app later.

A React Native app runs on both iOS and Android, and the MATTR VII tenant validates requests differently for each platform. Create a verifier application for the platform you intend to run the sample app on, following the steps in the iOS or Android tab.

let platformConfiguration = PlatformConfiguration(
    tenantHost: Constants.tenantHost
)

do {
    mobileCredentialVerifier = MobileCredentialVerifier.shared
    try mobileCredentialVerifier.initialize(platformConfiguration: platformConfiguration)
} catch {
    print(error.localizedDescription)
}

• tenantHost : URL of your MATTR VII tenant, defined in the Constants file.

val platformConfiguration = PlatformConfiguration(
    tenantHost = URL(Constants.TENANT_HOST)
)

lifecycleScope.launch {
    MobileCredentialVerifier.initialize(
        context = this@MainActivity, platformConfiguration = platformConfiguration
    )
}

• tenantHost : URL of your MATTR VII tenant, defined in the Constants file.

const result = await initialize({
  platformConfiguration: { tenantHost: Constants.TENANT_HOST },
});

if (result.isErr()) {
  console.error("Failed to initialize SDK:", result.error);
}

• tenantHost : URL of your MATTR VII tenant, defined in the Constants file. The SDK returns a Result, so check result.isErr() rather than relying on a thrown exception.

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).

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).

const 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 : An object 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).

let onlinePresentationResult = try await mobileCredentialVerifier.requestMobileCredentials(
    request: [mobileCredentialRequest],
    challenge: UUID().uuidString,
    applicationId: Constants.applicationID
)

• 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.

val onlinePresentationResult = MobileCredentialVerifier.requestMobileCredentials(
    activity = activity,
    request = listOf(mobileCredentialRequest),
    applicationId = Constants.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.

const result = await requestMobileCredentials({
  request: [mobileCredentialRequest],
  applicationId: Constants.APPLICATION_ID,
  challenge: Crypto.randomUUID(),
});

• request : Array of MobileCredentialRequest objects defining what information to request.
• applicationId : The id returned when you created the verifier application configuration.
• challenge : A unique, unpredictable value to identify this presentation session and prevent replay attacks. Generate a new challenge for every request.

.onOpenURL { url in
    // Navigate to response screen
    viewModel.navigationPath.append(NavigationState.viewResponse)
    viewModel.mobileCredentialVerifier.handleDeepLink(url)
}

Add this modifier to your SwiftUI view to navigate to the response screen and pass the redirect URL to the SDK's handleDeepLink method. The SDK processes the response and updates the receivedDocuments variable with the verification results.

The SDK handles the redirect via the Openid4VpCallbackActivity declared in your AndroidManifest.xml. Register the callback activity with an intent filter that matches the redirect URI of your verifier application:

<activity
    android:name="global.mattr.mobilecredential.verifier.a2apresentation.callback.Openid4VpCallbackActivity"
    android:exported="true">
  <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="com.yourname.mobileverifier"
        android:host="oid4vp-callback" />
  </intent-filter>
</activity>

• android:scheme : Must match the redirect custom scheme you defined when you created the verifier application.
• android:host : Must match the redirect host you defined when you created the verifier application.

Handling the redirect differs by platform:

• iOS: Forward the wallet's redirect URL to the SDK with handleDeepLink so it can complete the pending requestMobileCredentials call:

  useEffect(() => {
    if (Platform.OS !== "ios") {
      return;
    }
    const subscription = Linking.addEventListener("url", ({ url }) => {
      handleDeepLink({ url });
    });
    return () => subscription.remove();
  }, []);

• Android: The withOpenid4VpCallbackActivity config plugin declares the SDK's Openid4VpCallbackActivity in AndroidManifest.xml, bound to {your_packageName}://oid4vp-callback. The SDK handles the redirect automatically, so requestMobileCredentials resolves directly and no additional code is required.

guard let receivedCredentials = onlinePresentationResult.mobileCredentialResponse?.credentials else {
    let errorMessage = onlinePresentationResult.error?.message ?? "No error message"
    print("No response received: \(errorMessage)")
    return
}
receivedDocuments = receivedCredentials

• 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 sample app assigns the result to the receivedDocuments variable, which a DocumentView then renders. A DocumentViewModel converts each MobileCredentialPresentation (docType, verification result, claims, and claim errors) into a human-readable format for display.

_receivedDocuments.value =
    onlinePresentationResult.mobileCredentialResponse?.credentials ?: emptyList()

• 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 sample app assigns the result to the _receivedDocuments state flow, which a DocumentView composable then renders. The composable reads the docType and verification result and flattens document.claims into a list of label and value pairs for display.

const session = result.value;
if (!session.isSuccess) {
  console.error(`Verification session failed: ${session.error.message}`);
  return;
}

const response = session.mobileCredentialResponse;
setVerificationResults(response ?? null);

• result.value : The OnlinePresentationSessionResult. Check session.isSuccess to distinguish a successful session from a failed one (session.error).
• mobileCredentialResponse : Contains the verified credentials and their claims.
• credentials : A list of presented credentials with their data, status, and verification results.

The sample app stores the response and renders it in a VerificationResultsModal, which reads each MobileCredentialPresentation (docType, verification result, claims, and claim errors) and displays it in a human-readable format.