Integration architecture
The typical integration involves your existing mobile app, the MATTR Pi Holder SDK, and MATTR VII as the backend platform. This page describes the components and how data flows between them.
Integration architecture
The typical integration involves your existing mobile app, the MATTR Pi Holder SDK, and MATTR VII as the backend platform.
Components
| Component | Role |
|---|---|
| Your mobile app | User interface, business logic, navigation |
| MATTR Pi Holder SDK | Credential operations (claim, store, present) |
| MATTR VII | Issuer/verifier backend (offers, sessions, trust) |
| Device secure storage | Credential and key storage (managed by SDK via platform keychain/keystore) |
Data flow
- Claiming: Your app receives an offer URI → passes it to the SDK → SDK communicates with MATTR VII → credential is stored locally.
- Proximity presentation: Verifier scans your app's QR → BLE session established → SDK handles exchange → user consents → data shared.
- Remote presentation: Verifier sends request → your app receives it → SDK processes and validates → user consents → response sent.
Next steps
Next, review the trust and security considerations for your integration.
How would you rate this page?
Last updated on