Skip to main content

ISBE Wallet

The ISBE Holder Wallet is the ISBE ecosystem's reference mobile app for citizens to store, manage, and present their Verifiable Credentials (VCs). It is available for iOS and Android.

What is the wallet?

The wallet is the app that adopts the holder role in the ISBE trust model: the citizen receives credentials from accredited issuers, stores them securely on their device, and presents them to verifiers when needed.

The wallet is not a cloud service or an SDK embeddable in third-party applications. It is a native mobile app that citizens install on their phone and that keeps their credentials under their exclusive control.

What you can do with the wallet

  • Receive credentials from ISBE-accredited issuers via a QR code or a direct link.
  • Store credentials encrypted on the device, without depending on any central server.
  • Present credentials to verifiers that request them, after explicit user confirmation.
  • Manage your identity: create and export your decentralized identifier (DID), back up and restore your account.
  • Revoke access to credentials by deleting them from the wallet (revocation on the issuer side is a separate process).

Supported standards

StandardUse
OID4VCI 1.0 (pre-authorized flow)Receiving credentials from an issuer
OID4VP 1.0 with DCQLPresenting credentials to a verifier
W3C VC Data Model 2.0Credential format (jwt_vc_json)
did:key, did:jwkHolder DID methods

Sections of this documentation

PageDescription
ConceptsGlossary and role model: holder, issuer, verifier
InstallationRequirements and how to install the wallet on iOS and Android
Receive a credentialComplete reception flow via QR or OID4VCI deep link
Present a credentialOID4VP flow: request, selection, and consent
Identity managementDID, backup, restore, and biometric PIN
Security and privacyEncryption model, key storage, and privacy
API ReferenceDetailed OID4VCI and OID4VP flows for integrators
TroubleshootingCommon errors and how to resolve them

For integrators

If you are building an issuer or a verifier that interoperates with the wallet, the technical entry point is the API Reference. Issuers must implement OID4VCI 1.0 (pre-authorized flow) and verifiers must issue OID4VP requests with DCQL.

The wallet acts as a client in both flows: it does not expose any public API of its own.