5.1. Wallet Solution

The Wallet Solution is issued by the Wallet Provider in the form of a mobile app and services, such as web interfaces. The mobile app serves as the primary interface for Users, allowing them to hold their Digital Credentials and interact with other participants of the ecosystem, such as Credential Issuers and Relying Parties. These Digital Credentials are a set of data that can uniquely identify a natural or legal person, along with other Qualified and non-qualified Electronic Attestations of Attributes, also known as QEAAs and EAAs respectively, or (Q)EAAs for short. Once a User installs the mobile app on their device, such an installation is referred to as a Wallet Instance for the User. By supporting the mobile app, the Wallet Provider ensures the security and reliability of the entire Wallet Solution, as it is responsible for issuing the Wallet Attestation, which is a cryptographic proof about the authenticity and integrity of the Wallet Instance.

The following diagram depicts the Wallet Solution High Level Architecture.

Fig. 5.1 Wallet Solution High Level Architecture.

Wallet Solution Table of Contents

• 5.1.1. Wallet Solution Requirements
  • 5.1.1.1. Wallet Attestation Requirements
  • 5.1.1.2. WSCD Requirements
• 5.1.2. Wallet Solution Components
  • 5.1.2.1. Wallet Backend
  • 5.1.2.2. Wallet Unit
• 5.1.3. Wallet Solution Interaction Patterns
• 5.1.4. Wallet Instance
  • 5.1.4.1. Wallet Instance Lifecycle
  • 5.1.4.2. Wallet Instance Functionalities
• 5.1.5. Backup and Restore
  • 5.1.5.1. Backup Flow
  • 5.1.5.2. Restore flow for Hardware Binding Credential
• 5.1.6. Wallet Provider Entity Configuration
  • 5.1.6.1. Wallet Provider Entity Configuration JWT Header
  • 5.1.6.2. Wallet Provider Entity Configuration JWT Payload
• 5.1.7. Wallet Provider Metadata
  • 5.1.7.1. wallet_provider metadata
  • 5.1.7.2. federation_entity metadata