21 docs tagged with "Developer"

When designing solutions for the EUDI Wallet Ecosystem, both Relying Parties (RPs) and European Accessibility Act. Providers must consider accessibility requirements that ensure their services are usable by all citizens, including those with disabilities. This document outlines the high-level accessibility frameworks and key considerations for designing accessible solutions.

This page aggregates relevant changes in the German EUDI ecosystem for Relying Parties and EAA Issuers. Where possible, upcoming changes are listed in advance so that integrators can prepare.

How to configure the appearance of an Electronic Attestation of Attributes (EAA) so it renders correctly and legibly in the German EUDI wallet.

Audience: EAA Providers running an issuance service in production. This is phase 4 of the EAA Provider roadmap — what happens after you have built and tested your issuer.

Audience: EAA Providers implementing issuance flows with OpenID4VCI in the German EUDI Wallet Ecosystem.

This guide provides EAA-specific onboarding requirements and technical integration steps for organizations that want to issue Electronic Attestations of Attributes (EAAs) in the German EUDI Wallet Ecosystem.

Organization Overview

Erica is a public, lightweight, locally-runnable tool designed to help Relying Parties (RPs) accelerate their verifier development and testing. Rather than waiting for integration with the full EUDI Wallet ecosystem, you can use Erica to simulate wallet behavior and test your presentation request handling in isolation.

Audience: Developers new to the EUDI Wallet Ecosystem who need to understand how high-assurance credential issuance works in practice.

Audience: Developers new to the EUDI Wallet Ecosystem who need to understand how low-assurance credential issuance works in practice.

This page provides a practical reference for Relying Parties integrating with the German Personal Identification Data (PID) credential. It summarizes the key technical details from the German PID Rulebook (PID-DE) that you need to understand in order to successfully request, receive, and verify a PID.

This page defines terms, abbreviations, and acronyms used across the German EUDI Wallet Ecosystem documentation. Entries are drawn from the Blueprint, the Wallet Architecture Documentation, and this Developer Guide. Each entry links to the primary source specification or regulation where applicable.

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

Effective logging and monitoring are critical for transparency, security, and compliance within the EUDI Wallet Ecosystem. The following guidance distinguishes between sandbox and production environments.

This document provides a non-exhaustive list of open-source libraries that support OpenID4VP (OpenID for Verifiable Presentations). The list is intended as a starting point for Relying Parties exploring OpenID4VP implementations.

Audience: Relying Parties implementing an OpenID4VP flow to enable the consumption of a PID credential in the German EUDI Wallet Ecosystem.

Introduction

This guide provides Relying Party-specific requirements and technical integration steps for organizations that want to verify credentials in the German EUDI Wallet Ecosystem.

A rulebook is the definitive, human-readable, technical, and governance specification for a credential type. It ensures that relying parties understand exactly what a credential contains, how it's issued, and how to verify it.

Audience: Relying Parties building OpenID4VP / HAIP presentation requests for the German EUDI Wallet Ecosystem.

Developers testing with the National EUDI Wallet in the Sandbox should be aware of the following details, peculiarities and known bugs.