Skip to main content

dewa Platform

This documentation describes the dewa platform components that implement European digital identity standards: the Core API, the VX API, and the wallet SDK. Our goal is to provide clear, auditable information for customers, compliance reviewers, procurement teams, and integration engineers so they can verify that our implementation follows the EU Reference Framework for digital identity and the relevant OpenID standards.

We build to the EU Reference Framework and modern OpenID specifications so organizations can confidently rely on dewa for issuing, presenting, and verifying privacy-preserving digital credentials across wallets and relying parties.

The documentation focuses on three practical goals:

  • Standards alignment: show how dewa maps to the EU Reference Framework and OpenID/W3C specifications.
  • Interoperability: provide protocol flows, example vectors, and test guidance so integrators can interoperate with compliant wallets and relying parties.
  • Security & privacy: document cryptographic choices, transport and deployment hardening, and privacy-preserving patterns.

Overview of components​

  • Core API — Implements OpenID for Verifiable Credential Issuance (OpenID4VCI). Core API is intended for credential issuers such as PID, QEAA, and EAA authorities. See our technical OpenAPI docs: https://add-id.eu/scalar/
  • VX API — Implements OpenID for Verifiable Presentations (OpenID4VP). VX API is intended for wallet relying parties and services that request presentations from wallet holders. See our OpenAPI docs: https://verify-id.eu/scalar/
  • Wallet SDK — Wallet-focused libraries and UI components for building GDPR- and eIDAS-compatible wallet integrations, secure key handling, and user-facing flows.

Standards, compliance, and the EU reference​

The dewa platform aligns with the European Reference Framework for digital wallets and credential ecosystems. It adheres to OpenID4VCI and OpenID4VP standards, ensuring interoperability, security, and privacy. For detailed mappings to compliance requirements, refer to the "Compliance" sections in the Core API, VX API, and SDK documentation.

Key audiences and how this documentation helps​

  • Customers and Integrators: architecture overviews, sequence diagrams, example requests/responses, and SDK/endpoint guides to speed integration and reduce risk.
  • Compliance teams and auditors: explicit mapping to the EU reference framework, security controls, and an audit-friendly checklist to demonstrate conformity.
  • Procurement and legal reviewers: concise summaries of implemented standards and links to normative specifications to support requirements and tender evaluation.

How to read this documentation​

Start with the component overviews above, then follow these paths depending on your role:

  • Integrators: jump to the VX API or Core API sections for endpoint reference, authentication, examples, and SDK usage.
  • Auditors: read the "Compliance" sections in each API reference to verify implemented controls.
  • Product/Procurement: read the summary sections and the normative references to confirm standards alignment.

Status​

This documentation is actively maintained. If you find gaps or have additional questions, please contact the dewa engineering team.