Credentials, programmable
Integrations
Cloud Wallet is just another holder from Broker's perspective. Cross-sells Wallet SDK for ARF high-assurance.
Cloud Wallet speaks standard OID4VCI + OpenID4VP. Every Thoryn service that talks to holder wallets sees a standard protocol — no Cloud-Wallet-specific API.
Thoryn catalog composition
Cloud Wallet + Broker
Pattern: Cloud Wallet holds credentials; Broker verifies them. From Broker's perspective, Cloud Wallet is just another holder — standard OpenID4VP flow, no Cloud-Wallet-specific logic.
Cloud Wallet + Credential Issuer
Pattern: Cloud Wallet receives credentials via standard OID4VCI. No issuer-side changes needed. The user-facing flow: user pastes the offer URI into the wallet, wallet fetches the credential.
Cloud Wallet + Trust Registry
Pattern: Cloud Wallet validates issuer signatures against Trust Registry on credential receipt. Rejects credentials from untrusted issuers before storing.
Cloud Wallet + eIDAS Verifier
Pattern: For EUDIW presentations, Cloud Wallet is the medium-assurance counterpart to a hardware-backed wallet. Use case: cross-border identity verification where the holder prefers a browser flow.
Also on Cloud Wallet
Ready to hold credentials for your users?
Request access to stand up Cloud Wallet and connect it to your issuer.