Skip to content

Joining the Ecosystem

One Onboarding Process for All Roles

Whether you plan to verify credentials (Relying Party), issue credentials (EAA Provider), or do both, you complete the same onboarding process once. During Stage A (Plan), simply declare all the roles you intend to fulfill in your use case description.

Prerequisites

To participate in the German EUDI Wallet Ecosystem Sandbox, your organization should meet the following prerequisites:

One of the following must be true:

  • You are based in Germany and operate a digital service or platform requiring user verification, credential issuance, or related identity services.
  • You are a service provider actively serving or expecting to serve organizations registered in Germany.
  • You are an international party desiring to test interoperability in the German Sandbox, recognizing that a German legal entity is required to enter production.

All of the following must be true:

  • You can integrate web-based APIs and manage secure HTTPS endpoints.
  • You are able to designate a technical contact for integration activities.
  • You are able to designate an operational contact for compliance communication.
  • You are authorized to process user identity or attribute data under applicable law.

Sandbox Environment

The ecosystem is under constant development. Solutions developed in the sandbox today may require modifications before entering the production environment when it becomes available.

Initial Functionality

The sandbox initially launches with PID functionality only. Therefore, PID-related use cases will be prioritized for support in the earliest stages.

Onboarding Stages

The onboarding process involves you getting a formal introduction and access to support resources, culminating in a trusted status in the EUDI Wallet Ecosystem Sandbox.

We define the process in three main stages:

Stage Goal Output
Stage A: Plan Define your use case and requirements & organizational alignment Internal alignment & resource allocation
Stage B: Integrate Build out technical components Verified sandbox integration
Stage C: Operate Use case expansion, lifecycle management Sandbox operations

The first stage is meant for prospective participants to research the support materials, get organized internally, index the needs they have, and reserve the necessary resources for participation.

When the planning stage has been completed, you can reach out to us and start engaging with the technical part of the onboarding.

Kick-off calls happen on a monthly schedule, and upcoming dates are posted in the Ecosystem Knowledge Center. The kick-off call is the entry point for access to the Support Resources associated with the sandbox. This process allows us to scale the sandbox in a controlled way, as we roll out our support features. Additionally, there will be regularly recurring sessions for technical support and Q&A. Once the technical integration has been achieved, you can move on to operating in the sandbox.

Stage A: Plan

A.1 Define Your Use Case

Document your intended participation mode (credential issuance, verification, or both), why it is required, and which level of assurance is needed.

A.2 Research the Ecosystem

A.3 Assess Organizational Readiness

  • Evaluate benefits for your users and organization
  • Consider privacy and security implications
  • Estimate technical effort and resources required
  • Identify team members and their roles

A.4 Organize Internally

As you have decided the initial scope of your work, we ask you to align your team and resources before seeking contact with us.

A.5 Declare Your Intent to Join

Please declare your intent to join the sandbox and share the working title of your use case via the intent form. Per use case, one intent form should be submitted. Once you have submitted the form, our team will reach out to you.

Stage B: Integrate

B.1 Attend a Kick-Off Call and Gain Access

After attending the kick-off call, you will be offered access to the EUDI Wallet Closed Beta. Additionally, you will gain access to the German EUDI Ecosystem Sandbox Registrar. Access to this environment allows you to configure and issue the necessary certificates for your participation.

B.2 Complete Technical Integration

Depending on your intended role(s), complete the relevant technical integration(s):

  • If you are an EAA Provider (issuing credentials): Follow the EAA Provider integration steps
  • If you are a Relying Party (verifying credentials): Follow the Relying Party integration steps
  • If you are both: Complete both integration processes. You only onboard to the ecosystem once, but you'll need to set up both technical components (issuer and verifier).

Stage C: Operate

The Sandbox is a place for you to iterate and collaborate.

C.1 Test in Sandbox

Validate your integration flows using the provided Wallet and credentials.

C.2 Maintain Your Service

Manage certificate lifecycle and operational logs.

C.3 Prepare for Production

Fine-tune logging, preparation for scaling, and compliance processes.

C.4 Collaborate on New Use Cases

Explore opportunities to expand your participation or collaborate with other ecosystem participants.

Note: Use this stage to document lessons learned and operational improvements.

Compliance Responsibilities

All participants must adhere to a minimum set of operational responsibilities:

Requirement Responsibility
Secure Operation HTTPS endpoints, secure key and credential management
Purpose Limitation Process only data necessary for the declared service
Logging & Auditing Maintain minimal logs, pseudonymize identifiers
Certificate Management Renew and revoke certificates as required
Trust Registry Updates Maintain status in the appropriate registry
Policy Adherence Agree to terms and conditions

Support Resources

  • Mattermost Community: Join our technical discussion channels
  • Documentation: Access comprehensive technical guides
  • Regular Q&A Sessions: Participate in scheduled support calls
  • Sandbox Registrar: Manage your certificates and configuration