Relying Party Readiness Checklist¶
1. Introduction¶
This checklist helps you determine how prepared your organisation is to onboard into the German EUDI Wallet ecosystem. It supports two types of RPs:
- RPs already building with a clear use case and technical resources.
- RPs still exploring their use case and needing consultation support.
1. Organisational Readiness¶
1.1. Internal Alignment¶
- Your organisation understands the purpose of participating in the EUDI Wallet ecosystem.
- A high-level use case or service concept has been defined (even if still exploratory).
- A decision-maker or project sponsor is identified.
- A project lead or primary contact person for the onboarding process is appointed.
2. Use Case Maturity¶
2.1. For RPs Already Building¶
- A concrete use case has been defined with clear user flows, using the PID.
- The credential types required for the use case are known.
- The expected interactions with the Wallet are identified.
- You have initial technical resources allocated (internal dev team or vendor).
- You have reviewed the current ARF-aligned standards relevant to your implementation.
2.2. For RPs Still Exploring¶
- You can describe your domain (public service, private service, regulated sector, etc.).
- You can identify the problem or process you believe the EUDI Wallet may improve.
- You have collected internal requirements or constraints (legal, operational, UX).
- You are prepared to discuss your service concept.
2.3. Participation Preparedness¶
- You have registered and submitted your use case using the Use Case Form.
- You have identified and discussed possible unusual and/or specific requirements with the orchestrator.
3. Technical Readiness¶
3.1. Minimal Technical Readiness (for all RPs)¶
- A technical point of contact is identified.
- You understand that your system will need to integrate with standards such as OpenID4VP, SD-JWT, and ISO mDoc.
3.2. Advanced Technical Readiness (for building RPs)¶
- You can already test or prototype VP requests.
- You have reviewed trust and security requirements (e.g., certificate usage, authentication, cryptographic bindings).
4. Compliance & Trust Framework Readiness¶
- You understand that receiving the Access Certificate and Registration Certificate requires acceptance of the Terms and Conditions.
- You have or can identify the legal/compliance team who will support this.
- You understand that GDPR will apply to your solution.
5. Collaboration & Support Readiness¶
- You have joined or intend to join the RP communication channel.
- You understand that weekly Q&A / tech support sessions are open for ongoing help.
- You understand that the orchestrator is not be able to commit to 1:1 consulting sessions and are prepared to make use of open and shared resources.
6. Next Steps After Completing This Checklist¶
- Register for the next monthly Kick-Off Call upon invitation.
- Prepare initial questions or topics you want support with.
- Bring any existing diagrams, user flows, or technical documents (optional but helpful).
- Join the communication and support channels after the call upon invitation.
- Join the EUDI National Wallet Closed Beta by invitation