GO Verifier

MATTR GO Verifier onboarding guide

We created MATTR GO to take the complexity away from launching a branded verifier. To align with that, we have created an onboarding process that is as simple and straightforward as possible:

  1. Ready: You provide us with your visual, content and development assets.
  2. Set: We build the app, brand it as yours, test it and provide you with unsigned builds.
  3. Go: You sign the builds and upload them to the Apple and Google Play stores.

That's it. Your branded verifier is good to GO!


You kickstart the process by providing us with the assets we need to build and brand the verifier. Our design and development teams will collaborate closely with you regarding exact requirements, specifications and best practices to fine tune this process.

Branding assets

Our design team will work closely with you to make sure the verifier truly looks and feels yours. This means we will need the following collateral:

  • Typography: The verifier can be configured with one font family and three weights, to closely match your brand and design. While letter spacing and weights allocation can be customised, changes to text size are not supported to ensure accessibility standards and UI integrity.
  • Iconography: The verifier uses iconography to depict functions and status to the user. We encourage changing the default icons to align with your design and style. This can include adjusting icons colors as well as the icon itself if you provide a replacement pictogram.
  • Illustrations and graphics: The verifier uses illustrations to support the visual tone and content of various screens and flows throughout the UI. These come in either SVG or animated Lottie files (JSON). Replacements must be of exactly the same size and format.
  • Splash screen & App icon: In addition to the illustrations detailed above, the verifier requires a graphic splash screen and an app icon.
  • UI Configuration: The verifier includes a number of tokens that are available for configuration, including colours and shapes of different UI elements. We highly recommend adjusting these so that the verifier matches your brand and design. Special attention should be paid to contrast and light/dark considerations.

Content assets

The following content assets are required so we can embed them in the app:

  • Language Files: We provide you with a template you can use to provide us with translations for any languages your verifier will support.
  • Legal Documents: These include an End User License Agreement (EULA) and a Privacy Policy which should incorporate MATTR flow-through terms, as well as any other terms you choose to include. For verifiers that support multiple languages, both documents must be translated for all supported languages.

Development assets

The following development assets are required for building your verifier:

  • Build Parameters: These include various parameters such as the verifier app name, version, default language, caching / offline configuration and results screen configuration.
  • AWS Account Details: To enable your secure access to the verifier builds, the preferred option is for you to provide us with your Role Amazon Resource Name (ARN).


Once all the assets are provided, we can begin the development process:

  • Creating your verifier using the provided development assets.
  • Branding your verifier using the provided visual assets.
  • Testing your verifier.


Once development, branding and testing are completed, we will provide you with two unsigned builds - one for iOS and one for Android.

You can now:

  • Further test the verifier as per your internal workflows and policies.
  • Release the verifier to the Apple and Google Play stores.

Once the app is released, your users can download it to their mobile devices and get GOing.

For any required updates, our team will guide you with the required information:

  • App version: This is changed for every new build.
  • Version checker details: Set your verifier versioning policy.
  • Visual/Content/Development assets: As per the content of the update.