Digital euro pilot — User journeys & minimum UX requirements
2170 lines. Illustrative “happy flow” user journeys (frontend-agnostic, one wireframe
example per journey) plus minimum UX requirements — mandatory unless marked
[optional]. Covers access management, transaction management, and liquidity management
journeys, plus a generic UX requirements chapter (error handling, feedback/information/
positioning, transactions, end-user support) applicable across all journeys.
Fully digested (2026-07-22)
Every journey, wireframe and requirement in this document is now covered in the wiki:
- All 19 domain journeys (10 Access Management, 8 Transaction Management, 1 Liquidity Management) — step-by-step, cross-referenced to their src-end-to-end-process-flows flow IDs, wireframes extracted as PNG — in access-management-flows, transaction-management-flows, liquidity-management-flows respectively.
- The generic UX requirements chapter (§2: authentication, accessibility/branding/ controllability, error handling, feedback/information/positioning, transactions & end-user support) — in generic-ux-requirements.
- Wireframe PNGs (200dpi, extracted via Poppler) live in
raw/ecb-pilot/docs/img/user-journey-ux-requirements/(not part of the publish mirror — see access-management-flows’s caveat note, applies to all four pages above).
Feeds into
pilot-psp · online-and-offline-payments · authentication · access-management-flows · liquidity-management-flows · transaction-management-flows · generic-ux-requirements