Open source · Open standards · On your infrastructure

Your Diplomatic Layer for EUDI Wallet Integration.

EUDIPLO bridges your backend and EUDI Wallets through a unified API and open standards. Issue and verify credentials with production-ready protocol handling, while your team keeps focus on business logic.

Start building View on GitHub

OID4VCI SD-JWT VC mdoc OpenID Federation OID4VP

OpenWallet Foundation project ✓ OIDF conformance tested ✓ Self-hosted by design ✓ Built for issuer & verifier use cases

01 / Docs

Getting Started

Run locally, configure credentials, and issue your first wallet-compatible credential.

02 / Docs

Architecture

Understand issuer, verifier, key management, trust model, and protocol abstraction boundaries.

03 / Docs

API Reference

Explore endpoints, authentication, DTOs, and generated API documentation.

04 / Docs

Deployment

Deploy with Docker Compose or Kubernetes and run with observability and key controls.

The diplomatic layer

Your business logic speaks API.
EUDIPLO speaks wallet.

Keep attributes and decisions in your own systems. EUDIPLO translates a clean integration into the protocol flows, metadata, security mechanisms and wallet interoperability the ecosystem expects.

Your application

Provides credential data through a webhook or API.

EUDIPLO

Orchestrates authorization, proof validation, credential formats, signing and status.

EUDI Wallet

Receives a standards-compliant credential.

Simple on the outside

Configure the outcome. Not the protocol.

Define what you want to issue or request. EUDIPLO turns configuration into complete issuer and verifier behavior.

Bring your existing backend

Connect through webhooks and APIs without moving your business data into another cloud.

Stay adaptable

Support SD-JWT VC and mdoc while keeping protocol changes out of your application.

Operate with confidence

Use tenant isolation, auditable sessions, OpenTelemetry and production-grade key management.

event-access-attestation.json

// Shortened real-world shape used by EUDIPLO configs
{
  "id": "event-access-attestation",
  "description": "Event Access Attestation",
  "lifeTime": 7776000,
  "keyBinding": true,
  "statusManagement": false,
  "vct": "urn:eudi:eaa:event-access-attestation:1",
  "config": {
    "format": "dc+sd-jwt",
    "display": [{ "name": "Event Access Pass", "locale": "en-US" }]
  },
  "fields": [
    {
      "path": ["event_name"],
      "type": "string",
      "mandatory": true,
      "disclosable": true
    },
    {
      "path": ["access_type"],
      "constraints": { "enum": ["full_access", "vip_access"] }
    }
  ]
}

Built for real deployments

The infrastructure behind a trustworthy wallet service.

{ issuer }

Credential issuance

Authorization Code and Pre-Authorized Code flows, SD-JWT VC and mdoc, batch issuance, status and notifications.

{ verifier }

Presentations

OID4VP, DC API and DCQL with same-device and cross-device flows, secure responses and webhooks.

{ trust }

Trust & registration

Trusted lists, Access and Registration Certificates, OpenID Federation and registrar integration.

{ keys }

Key management

Local keys, Vault, AWS KMS, remote KMS and PKCS#11/HSM adapters through a unified model.

{ teams }

Multi-tenant operations

Separate tenants, role-based access, PostgreSQL support and an administration interface for teams.

{ observe }

Observable by default

Persistent session logs and OpenTelemetry integration for the visibility production environments need.

Quick start one command to a local issuer/verifier demo

npx @eudiplo/cli demo Learn the CLI

Prefer a standalone CLI? The release workflow publishes a Node SEA binary for eudiplo.

Open source. Ready to integrate.

Let your product focus on
what makes it different.

EUDIPLO takes care of the wallet protocol layer—so your team can build the service users actually came for.

Read the documentation → Star on GitHub ↗