Onboarding
Two distinct onboarding layers — don’t conflate them.
1. Pilot PSP onboarding to DESP
Per src-onboarding-overview: the PSP is configured as a user in desp before it can offer any pilot payment service.
- Reference data set-up — PSP submits reference data (predefined format, shared later) to its participating ncb for validation and DESP test/production onboarding. NCB also configures dca access in both environments.
- Connectivity — PSP sources a connectivity provider, connects to DESP, runs an initial connectivity test in both the user-testing and production environments. This is a prerequisite gate: it excludes DCA setup and other pre-operational activities, which are covered elsewhere (see pilot-timeline for sequencing).
2. End-user onboarding (via a pilot PSP)
Covered in src-end-to-end-process-flows §1.1 — separate flows for individual end user onboarding, business end user onboarding, digital euro app configuration + onboarding, and bulk DEAN requests. This is the process a pilot-psp actually implements in its own backend (issuing/mapping a dean, optional alias registration, linking a commercial bank account) — distinct from #1 above, which only concerns the PSP-to-DESP relationship.