Digital euro pilot — Functional requirements
The FUR.##-numbered requirement catalogue — the closest thing to a formal spec document
among the non-API pilot docs. 756 lines; requirements are grouped by topic (DEAN, alias,
authentication, and more not yet summarized below — re-read for later sections if a
question needs requirements beyond §1-1.3).
Key takeaways
- Defines functional/operational model per service; end-to-end flows are in src-end-to-end-process-flows, illustrative user journeys in src-user-journeys-ux-requirements — this doc is the “requirements” layer connecting both.
- §1.2.1 DEAN: format, issuance flow, agnosticism — see dean for the extracted rules.
- §1.2.2 Alias: voluntary, phone-number-only, 1:1 with DEAN, verification rules — see alias.
- §1.3 Authentication: seamless vs. redirect vs. PSP-proprietary SCA — see authentication.
When precision matters for implementation, quote the FUR.## ID directly rather than
paraphrasing — that’s the traceable unit ECB documentation and any future PSP↔Eurosystem
conversation will reference.
Feeds into
dean · alias · authentication · pilot-psp