Skip to content

Introduction

In a decentralized identity architecture, the wallet is the holder's side of the equation. It is a mobile application that receives, stores, and presents verifiable credentials on behalf of the end user - without routing data through any central server.

What a Wallet Does

The wallet is intentionally simple from the holder's perspective: scan a QR code to receive a credential, scan another to share it. The cryptographic complexity — signature verification, selective disclosure, zero-knowledge proofs — happens under the hood.

Credential storage: Credentials are stored locally on the device — not in the cloud. The holder retains full custody of their data at all times.

Credential issuance: When an issuer triggers a credential offer (as a QR code or a deep link), the wallet receives the offer, authenticates with the issuer, and stores the resulting credential.

Credential presentation: When a verifier requests data, the wallet generates a verifiable presentation and submits it. The holder must explicitly approve before any data is shared.

Selective disclosure: Holders can reveal only the specific attributes a verifier has requested — nothing more. For example, sharing only a name and student ID from a credential that also contains an address or date of birth.

Zero-knowledge proofs: The wallet can prove statements derived from credential data (e.g., "age is over 18") without exposing the underlying value.

The Partisia ID Wallet

Partisia provides a reference wallet application — the Partisia ID Wallet — for demonstration and testing purposes. It implements the full MDA protocol stack and is publicly available on both major mobile platforms:

The Partisia ID Wallet is useful for exploring the issuance and verification flows end-to-end before going to production. It is not intended as a production wallet for end users in a branded deployment — for that, see the white-label offering.

What's Next