Wallets, programmable
Integrations
Your app integrates via the SDK API; the SDK speaks standard OID4VCI / OpenID4VP to every Thoryn service.
Your app embeds the SDK and calls receive() + present(). The SDK speaks standard OID4VCI + OpenID4VP to every Thoryn service — no SDK-specific handshake on the server side.
Thoryn service integrations
- Credential Issuer (receive)
- SDK's
receive(offerUrl)consumes any OID4VCI-conformant offer — from Thoryn Credential Issuer or any other ARF-conformant issuer. - Broker + eIDAS Verifier (present)
- SDK's
present(requestUri)handles the OpenID4VP flow. Biometric gate on every presentation. Works against Thoryn Broker, Thoryn eIDAS Verifier, or any ARF-conformant verifier. - Trust Registry + VCT Registry (resolve)
- Wallet resolves VCT metadata to render credentials with localised display info. Trust-chain validation happens on the verifier side; the wallet focuses on presentation UX.
Your app integrations
- Deep linking
- Register
openid-credential-offer://andopenid4vp://URL schemes in your app. The SDK provides the handlers; your app owns the routing and UX. - Biometric UX
- iOS
LAContext+ AndroidBiometricPromptintegrated; the SDK exposes callbacks for "prompt shown", "auth succeeded", "auth failed" so your app can render an appropriate UI. - Storage backup
- Device-bound by design. No cloud recovery; credentials are re-issued into a new device if the user migrates. Your app can mark credentials with per-app metadata ("primary employment", "training completion") for UX organisation.
Also on Wallet SDK
Ready to embed a wallet in your app?
See the ADR, the scaffold, and the roadmap — book a 30-minute integration call.