SDK or ready-made wallet?
Before diving into integration, decide which path suits your product strategy. This page compares embedding the MATTR Pi Holder SDK against deploying the ready-made MATTR GO Hold wallet.
SDK or ready-made wallet?
Before diving into integration, decide which path suits your product strategy.
MATTR Pi Holder SDK: build it into your app
Best for: teams that want credential holding embedded within their existing mobile application, with full control over the user experience and branding.
The MATTR Pi mDocs Holder SDK provides native libraries for iOS, Android, and React Native. You integrate the SDK into your existing codebase, and your app gains the ability to claim, store, and present credentials directly.
Choose the SDK when you:
- Already have a mobile app and want to add credential capabilities to it.
- Need full control over the user interface and interaction flow.
- Want credential holding to be seamless within your existing app experience.
- Need to customize presentation consent screens, credential displays, or notification handling.
- Are building a purpose-specific application (e.g., employee app, government services app).
MATTR GO Hold: use a ready-made wallet
Best for: teams that want to offer credential holding without building or maintaining a custom wallet, or that need a wallet for testing and pilot deployments.
MATTR GO Hold is a downloadable wallet application that supports credential claiming and presentation out of the box. It can serve as a white-label starting point or a production wallet for end users.
Choose MATTR GO Hold when you:
- Want to get to market quickly without custom mobile development.
- Need a wallet for pilot programs, proofs of concept, or testing.
- Don't require deep integration with an existing app experience.
- Want a standalone wallet app for your users.
- Need a reference implementation to guide your own SDK integration later.
Comparison
| Consideration | MATTR Pi Holder SDK | MATTR GO Hold |
|---|---|---|
| Integration effort | Medium–high (native SDK integration) | Low (deploy existing app) |
| UX customization | Full control | Limited to configuration |
| Branding | Your app, your brand | MATTR GO or white-label |
| Platform support | iOS 15+, Android 7+, React Native 0.78+ | iOS 15+, Android 7+ |
| Credential claiming | OID4VCI (Auth Code + Pre-authorized) | OID4VCI (Auth Code + Pre-authorized) |
| Proximity presentation | ISO/IEC 18013-5 via BLE | ISO/IEC 18013-5 via BLE |
| Remote presentation | ISO/IEC 18013-7 + OID4VP | ISO/IEC 18013-7 + OID4VP |
| Time to first credential | Days–weeks (development cycle) | Hours (configuration only) |
Next steps
If you are integrating the SDK, review the platform requirements next.
How would you rate this page?
Last updated on