#Overview

walt.id's Wallet Service enables organizations and wallet providers to create digital wallets that use draft OpenID4VCI and OpenID4VP protocols. It supports consumer wallets for end users as well as organizational wallets for companies.

#Feature Flag

Legacy Wallet routes and inventability require the wallet-draft-routes feature in _features.conf. The feature defaults to off. When it is disabled:

• /v1/.../wallet-service-api draft Wallet routes are not registered
• Creating a service with "type": "wallet" is rejected (use "wallet2" instead)

Enable it only if you need draft-protocol wallets or existing integrations that depend on them.

#Supported Standards

#Service Type and API

"wallet" and "wallet2" are different resource types. A node created as "wallet" is not served by the Wallet2 /v2 API until you migrate it.

#Migrating to Wallet2

An optional manual MongoDB migration rewrites _t: "wallet" to _t: "wallet2" on organization tree documents (same document shape; no field remapping). After migration, use Wallet2 /v2 APIs and clients. If you never run the migration, existing "wallet" nodes continue to work only with this legacy /v1 Wallet Service (when wallet-draft-routes is enabled).

#Core Features

#KMS & Identifiers

• Holder Keys — via the KMS Service.
• DIDs — via the DID Service and DID Store.

#Credential Storage

• Persist received credentials using the Credential Store Service.

#Credential Exchange

• Draft OID4VCI/VP flows for receiving and presenting credentials.
• Presentation Exchange and DCQL on present (legacy Wallet present path).
• Optional client attestation and holder policy store dependencies.

#Getting Started

• Setup — init-wallet wizard and "type": "wallet" create (requires wallet-draft-routes).

Receive & present (draft protocols)

• Receive: W3C · SD-JWT VC · mDL/mDOC
• Present: W3C · SD-JWT VC · mDL/mDOC