Digital Euro Wiki

psp-feedback-framework

1 min read

PSP feedback framework

The obligations a pilot-psp has to collect and transmit data/feedback before, during and after the pilot.

Two obligation areas

  1. Data collection and transmission — quantitative data from the PSP’s own technical/ operational systems, plus anonymised end-user feedback, transmitted to an entity designated by the participating ncb.
  2. Qualitative feedback on PSP experience — technical, operational, organisational (integration challenges, process adaptations, collaboration, communication with ECB/NCB).

Data protection rules (§4)

  • Governed by Regulation (EU) 2018/1725 and GDPR (EU 2016/679).
  • No end-user personal data collected/transmitted without explicit, informed, unambiguous consent — and even then, only professional/work email addresses of volunteering end users, used solely to request pilot feedback.
  • Proof of consent must be stored in a verifiable format; consent is withdrawable at any time (withdrawal is not retroactive).
  • Data minimisation + anonymisation required before transmission to ECB/NCB.

Feedback categories (§5)

PSP technical/operational integration · PSP operational satisfaction & experience · end-user product experience/satisfaction/engagement · pilot preparation & execution.

Timeline

Feedback runs from the start of the development phase to six months after the end of the operational phase (see pilot-timeline).

pilot-psp · ncb · ecb · pilot-timeline

Graph View

Backlinks