Skip to content

White Label P4P Mobile Wallet and Demo Experience Suite Specification

1. Executive Summary

  • Purpose: Deliver a white -label Digital Identity wallet to showcase existing P4P functionality for citizens and businesses, supporting Issuer, Holder, and Verifier roles. The white-label wallet will be complemented with a website allowing a guided experience (what does it mean to have wallets everywhere) that will cover both business questions (e.g. lowering risk, improving existing business processes, passwordless authentication) and technical questions (e.g. cryptographic signing, audit trails, data minimization)
  • Scope: Includes mobile app design and guided walk-through website, relying on existing mobile app logic, credential issuance capability (issuer module) and verification capability (verifier module), and self-issued signing certificates.
  • Standards: Must align with eIDAS2, latest ARF, and EU interoperability frameworks.

2. Functional Requirements

  • The wallet will be able to
    • receive one or more credential(s).
    • store one or more credential(s).
    • scan a presentation request (PR).
    • respond to a PR with required and/or optional claims (selective disclosure).
    • delete one or more credential(s).
  • Credential Lifecycle:
    • Issue PID and other Verifiable Credentials (VCs).
    • Present credential(s) with selective disclosure.
    • Support credential suspension and revocation.
  • Electronic Signature Functionality:
    • Support signing documents within the Wallet.

3. Non-Functional Requirements

  • Security:
    • PIN-based access with anti-brute-force and secure (element) storage.
    • Optional biometric authentication (fingerprint/face) with device-only processing.
    • Compliance with OWASP Top 10 and secure coding standards.

4. UI/UX Guidelines

  • Must follow user-centricity, privacy by design, and security by design principles.
  • Accessibility aligned with EU standards.
  • Support intuitive flows for credential issuance, presentation, and signing.

5. Branding & Theming

  • The white-label wallet and demo experience suite will have matching logos and theming to support the website walk-through experience.
  • White-label capability: configurable logos, colors, fonts, and localized content.
  • Created to maintain consistent UX across tenants.
  • Rule-of-thumb: the white-label wallet will be the foundation upon which all customer/end-user variations will be built.

6. Governance & Documentation

  • Deliverables:
    • White-label specification (this document).
    • Mobile wallet for iOS and Android (do we do iOS only first?).
    • Website with a welcome page, simple navigation and guided walk-through the acquisition, storage and use of credentials and digitial signatures.
    • Documentation allowing independent build from source(s).
  • Within the three-layered model (Layer 1 SOWL, Layer 2 P4P, Layer 3 Customer-specific implementation), the white-label wallet and demo suite resides in the P4P layer and is developed and versioned at the TTI github across code, documentation and design assets.

7. Acceptance Criteria

  • The mobile app is respnsive in comparison to similar apps:
    • takes no more than 5 seconds to load initially.
    • refreshes and presents current state under 5 sec.
    • has no lag in switching between screens or depths of display (e.g. card of credential vs content of credential)