Platforms

MATTR helps build trust into the digital world, ensuring that interactions remain seamless, secure, and privacy preserving. By integrating our products with your procedures, policies and business logic, you can streamline the management of digital credentials across their lifecycle. To support this, we offer three key platforms:

• MATTR VII is a cloud-based platform offering scalable digital trust services through advanced APIs and a web Portal, catering to credential issuers, verifiers and network providers.
• MATTR Pi provides SDKs for creating bespoke experiences or extending existing applications. Ideal for those requiring cross-platform and cross-channel integrations.
• MATTR GO offers a quick-start solution with configurable white-label apps, perfect for early-stage network operators, wallet providers and verifiers aiming for rapid deployment without extensive resource allocation.

Each platform is designed to fit different needs within the digital trust ecosystem, helping you to embed digital credentials into your solution.

Choosing the right platform

The three platforms address different layers of a credential ecosystem and most production deployments use more than one of them together. The decision usually comes down to three trade-offs: how much you want to build yourself, how distinctive the end-user experience needs to be, and how quickly you need to reach production.

MATTR VII

MATTR VII is the cloud platform that issuers, verifiers, and ecosystem operators build on. It exposes the full credential lifecycle through REST APIs and a web Portal, and provides the services Pi SDKs and GO apps depend on for backend operations.

Who it is for

• Government agencies and commercial credential issuers operating at scale.
• Relying parties running web or service-based verification.
• Ecosystem operators (trust framework providers, network coordinators) orchestrating issuers and verifiers across a community.

What it provides

• Credential lifecycle services for issuance, management, and verification across multiple credential profiles, including mDocs (ISO/IEC 18013-5 and 23220) and CWT credentials.
• Digital Trust Services that expose signed lists of trusted issuers and verifiers, including PKI for chain of trust and trust registry capabilities across ecosystem members.
• Platform management, including custom domains, a web based Portal, and public key infrastructure.

Choose VII when the credential workflow itself, not just the user-facing application, is what you need to operate. Issuance policy, revocation, trust configuration, and verifier resolution all live here. Read the MATTR VII spec sheet for more.

MATTR Pi

MATTR Pi is a set of SDKs that embed credential holding and verification into your own mobile and web applications. The SDKs abstract standards compliance, cryptography, transport flows, and platform-specific behaviors so your team can focus on the user experience.

Who it is for

• Wallet providers building a distinctive brand experience, or integrating credentials into an existing consumer app.
• Verifier organizations that need credential verification inside their own iOS, Android, or web application (for example at a kiosk, point-of-sale, or front-of-house workflow).
• Development teams with the engineering capacity to own the application layer while leveraging MATTR's standards implementation.

What it provides

• Holder SDKs for iOS, Android, and React Native to claim mDocs using OID4VCI flows, store them on device, present them in person (per ISO/IEC 18013-5) and remotely (per ISO/IEC 18013-7), and manage credential authentication policies (biometrics, PIN, passcode).
• Verifier mobile SDKs for iOS, Android, and React Native, supporting QR and NFC device engagement and offline in-person verification per ISO/IEC 18013-5, and remote mobile-based verification of same-device holder apps per ISO/IEC 18013-7 using OID4VP and the W3C Digital Credentials API where supported.
• A verifier web SDK for browser-based remote verification using ISO/IEC 18013-7-aligned flows, including OID4VP and the W3C Digital Credentials API where supported.

Pi works alongside VII, which provides the backend services for credential exchange, verification policy, and issuer resolution. Read the spec sheets for the Holder SDK, Verifier Mobile SDK, and Verifier Web SDK.

MATTR GO

MATTR GO is a white-label app platform for organizations that need production-ready holder and verifier apps under their own brand without commissioning custom development. Apps are built from proven templates and configured for your environment, inheriting MATTR's underlying security architecture and standards implementation.

Who it is for

• Government departments and commercial schemes launching credential-enabled apps.
• Organizations prioritizing time-to-market and a branded presence in app stores.
• Service providers that want a turnkey app with the flexibility to evolve later.

What it provides

• GO Hold: a branded holder app that claims, stores, and presents credentials in person and remotely, with selective disclosure, PIN or biometric protection, and revocation handling.
• GO Verify: a branded verifier app for in-field validation, including offline operation and visual signals for credential validity and expiry.
• Flexible service models: a managed model where MATTR delivers signed app bundles for you to publish, or a self-managed model where MATTR signs and submits apps to Apple and Google stores on your behalf.
• A design asset bundle covering icons, splash screens, typography, and layout templates.

Choose GO when the application layer is not where you want to invest engineering effort and you need branded apps in users' hands quickly. Read the MATTR GO spec sheet for more.

Combining platforms

The platforms compose rather than substitute. Common combinations include:

• VII + Pi: a custom wallet or verifier app built with Pi SDKs, backed by VII for issuance, exchange, and verification policy. Typical when you need a distinctive end-user experience and operate your own credential services.
• VII + GO: a branded white-label app backed by your own VII tenant. Typical when you want both ecosystem services and user-facing apps under one operating model, without engineering the apps themselves.
• VII alone: a backend-only deployment where end users interact through third-party wallets and verifiers. Typical for public schemes (for example, an mDL program) where citizens use the compliant wallet of their choice.