Embed the SDKs into your application

MATTR provides SDKs that abstract the protocol complexity so you can focus on your user experience. This page covers the recommended integration approach, the SDK options for each channel, and the backend configuration remote channels require.

Embed the SDKs into your application

MATTR provides SDKs that abstract the protocol complexity so you can focus on your user experience.

Integration approach

The recommended approach is to embed the MATTR Pi Verifier SDK directly into your application rather than redirecting users to an intermediate verification service. This:

• Maintains trust continuity. Wallets validate your app's origin directly.
• Delivers a seamless user experience without navigation interruptions.
• Ensures compatibility with platform-specific security requirements.

See implementation guidelines for detailed guidance on direct integration.

SDK options by channel

Backend configuration (remote channels)

For remote verification (web and mobile), you also need a MATTR VII tenant configured with:

• A verifier application registered with your domain or app identifiers.
• A wallet provider configuration for each wallet ecosystem you accept.
• Trusted issuer certificates for the jurisdictions and credential types you support.

Next steps

Next, establish trust with issuers so your application recognizes the credentials it receives.