Use Compact Credential Verifier SDK


We’ve transformed our Credential Verification capabilities to support the wider platform by making it work on your own mobile experience or integrating them into other types of your applications. Utilizing SDK will significantly reduce your development time while ensuring you are leveraging safe and reliable code libraries.

Interested in learning more about how you might use the MATTR Verifier SDK? Get in touch with us today.


We wanted to make our Verifier SDK as easy to use and as flexible as possible. This allows you to start building your own verifier App or adding these core pieces of functionality to your own apps. 

Capabilities include: 

  • Build your own Compact Credential verification solution into existing applications

  • Validate Compact and Semantic Compact Credentials' authenticity 

  • Offline verification of your trusted credentials

  • Refresh cached revocation lists and trusted issuers

  • Privacy-preserving features

Key Benefits

Build using the same tools as the MATTR Verifier App

The MATTR Verifier SDK allows you to take advantage of the credential verification capabilities and use them to build your own mobile verifier experiences without needing to start from scratch. You can also use the SDK to integrate credential verification functionalities into other types of applications while maintaining a consistent brand and user experience. This means you can leverage the security, privacy and trust benefits of digital identity and verifiable credentials, while significantly reducing your development time and maintaining a consistent user experience.  

Ongoing support for evolving standards  

MATTR is actively engaged in the communities that define the fast-evolving standards for digital trust and verifiable data. Our investment in updating our SDK to support these standards means that you can rely on our expertise in this space to keep your application relevant and compliant. 

Using the same codebase for iOS and Android 

We’ve built the MATTR Verifier SDK in React Native, which means you can create both iOS and Android apps using the same codebase. React Native is ideally suited to developing complex hybrid apps – given its advanced features and ability to provide a natural user experience. In fact, React Native took the 6th spot in the Stack Overflow Developer Survey 2021, with 14.51% of all respondent votes. 


The SDK has the following limitations: 

  • The SDK is implemented with an initial focus on developers who want to build React Native apps. 

  • The SDK provides a set of operations only, there are no UI elements provided by the SDK. 

  • Users will be given access to the NPMJS modules that contain obfuscated and minified packages.  

How it works


Creating a new verifier

Copy to clipboard.
1import { init } from "@mattrglobal/verifier-sdk-react-native";
3const initOptions: InitOptions = {
4  issuerCacheTtl: 60000,
5  revocationListCacheTtl: 60000,
6  trustedIssuers: [""], // defaults to trust any issuer
7  assertExpiry: true, // defaults to true
8  assertNotBefore: true, // defaults to true
9  checkRevocation: true, // defaults to true
12const verifier = await init(initOptions);

Verifying a credential

Copy to clipboard.
1// Verify a credential payload as encoded & signed string
2const verifyResult = await verifier.verify({ payload });
4if (verifyResult.isErr()) {
5  // Handle error from verifyResult.error
6  return;
9const { verified } = verifyResult.value;


The following allows you to get the expiry date of the cached revocation lists and trusted issuers, and refresh the icache.

Getting expiry date of the cache

Copy to clipboard.
1const expiry = await verifier.getCacheExpiry();

Refreshing the items in the cache

Copy to clipboard.
1const refreshCacheResult = await verifierSdk.refreshCache();
3if (refreshCacheResult.isErr()) {
4  /**
5   * The error contains the cache expiry date
6   * This date may have changed after partial refresh
7   */
8  console.log(refreshCacheResult.error.expiryDate);
9  // Handle error from refreshCacheResult.error
10  return;
13// New expiry date of the cache
14const { expiryDate } = refreshCacheResult.value;

Error Handling

Functions that are expected to have an error path return a Neverthrow Result type that represents either success (Ok) or failure (Err). Although this pattern is more verbose, it encourages the handling of possible errors and reserves throwing exceptions for truly exceptional situations.

Copy to clipboard.
1import { open } from "@mattrglobal/verifier-sdk-react-native";
3const openVerifierResult = await open();
5if (openVerifierResult.isErr()) {
6  // Handle error from openVerifierResult.error
7  return;
10const verifier = openVerifierResult.value;


A utility function is provided for convenience if you decide not to handle your errors as results. This function will simply throw an error if the function passed in returns a Result,where Result.isErr() is true.

Copy to clipboard.
1import { unwrap } from "@mattrglobal/verifier-sdk-react-native";
3try {
4  const verifier = unwrap(await open());
5} catch (error) {
6  // Handle thrown error

Known Issues

1. Build error: "ld: symbol(s) not found for architecture x86_64"

This error can arise when using flipper and react-native-bignumber together. Disabling flipper is the only solution at the moment. See here for more details.

2. Build error: "Plugin with id 'maven' not found."

Currently, react-native-securerandom is not compatible with Gradle 7+ (see issue) and will not build for Android without downgrading Gradle to 6.9 or below.

Get in touch if you wish to find out more about using the Verifier SDK in production.