Skip to content

Sandbox Support Resources Overview

Introduction

The sandbox is designed to help Relying Parties explore, prepare, and implement their services in alignment with the national EUDI Wallet ecosystem. To ensure fairness, transparency, and efficient use of public resources, the sandbox follows a self-service–first support model. Most early discovery work can be completed independently using the resources outlined below.

Our team provides structured guidance, documentation, and shared support formats. While we are available to answer questions, we cannot offer individual consulting sessions to develop or refine use cases. RPs are encouraged to make use of the self-service materials and the established communication channels before requesting additional guidance.


Support Resources and Expected RP Use

The following resources are arranged in the recommended order of use, particularly for RPs who are still exploring their service concept.


1. Ecosystem Knowledge Center — Start Here

Purpose: The primary and authoritative source for understanding the sandbox, technical standards, and integration expectations.

Recommended use:

  • To gain an overview of the EUDI Wallet ecosystem, its vision, and its standards.
  • To evaluate whether your intended service fits the EUDI Wallet model.
  • To review sample flows, architecture references, terminology, and compliance requirements.
  • To get detailed information on what is needed for technical integration

Link: https://bmi.usercontent.opencode.de/eudi-wallet/eidas2/en/ecosystem_knowledge_centre/


2. Use Case Exploration Materials & Self-Service

Purpose: Helps organisations shape their early ideas into clear, structured use cases before entering formal onboarding.

Includes:

Recommended use:

  • For initial planning and internal alignment.
  • To understand what makes a good RP use case.
  • To understand what is needed on a technical level.

3. RP Communication Channels (Chat)

Purpose: A collaborative space for short clarifications, practical pointers, and peer exchange.

Appropriate use:

  • Quick questions to unblock progress.
  • Requests for direction toward existing documentation.
  • Learning how other RPs approach similar challenges.

Not intended for:

  • Detailed design discussions.
  • Step-by-step consulting.

4. Written Asynchronous Consultation

Purpose: Enables RPs to submit structured questions or early concepts for review without requiring meeting time.

Recommended use:

  • When you have drafted a use case or initial technical flow and you are unsure about its suitability.
  • When you seek confirmation that your approach aligns with ARF requirements.

Guidance: Submissions should be clear and concise. Written summaries ensure faster and more precise responses.


6. Monthly Kick-Off Call — Entry Point to the Sandbox

Purpose: The formal starting point for active participation in the sandbox.

During this session, RPs receive:

  • An introduction to the sandbox structure and expectations.
  • Access to the EUDI Wallet Closed Beta
  • Access to the Sandbox Registrar

Recommended use:

  • Once your organisation has a clear service concept.
  • When you are ready to begin technical integration.
  • OR when you are ready to test your implementation

5. Weekly Q&A / Technical Information Sessions

Purpose: A recurring group format for implementation questions and clarifications.

Recommended use:

  • After reviewing available documentation.
  • When encountering technical challenges during preparation.
  • When questions may benefit multiple RPs.

This offers a platform for questions that are broader than individual implementation difficulties.


7. Sandbox Test Environment (Post Kick-Off)

Purpose: An environment for RPs to test presentation and wallet interactions.

Includes:

  • Debugging support.
  • Test suites (Coming later)

Recommended use:

  • When initial design work is complete.
  • When the RP is ready to validate its implementation.