eIDAS 2.0 Digital Identity — Without the Central Database
EU Digital Identity Wallet compliance for platforms operating in Europe. OID4VP-compatible verification returns cryptographic attestations — no passport scans, no PII stored.
Architecture
eIDAS Compliance by Design
EU Digital Identity Wallet (EUDIW)
Full OID4VP compatibility. Accept EU Digital Identity Wallet credentials via the OpenID for Verifiable Presentations protocol — the same architecture used by the German EUDI Wallet Sandbox (eudi-wallet.gov.de) and national eIDAS implementations across EU member states.
GDPR-Native Architecture
Right to erasure is impossible when identity data never enters the server. SOS verifies credentials cryptographically and discards the raw data — GDPR Article 17 compliance is an architectural property, not a legal feature.
Cross-Border Recognition
An eIDAS-verified SOS SID is recognized across all EU member states. One verification flow satisfies KYC requirements from Lisbon to Warsaw — without re-verification per jurisdiction.
THE eIDAS 2.0 COMPLIANCE CHALLENGE
EU Identity Compliance Should Not Require A Database of European Citizens.
eIDAS 2.0 mandates that platforms accept EU Digital Identity Wallets — but traditional implementation creates a centralized database of verified European identities. That database is a GDPR liability, a breach target, and the opposite of what the EU Digital Identity framework intended.
Traditional eIDAS Implementation
- Platform collects identity assertion from EU wallet — name, birthdate, national ID number — and stores it server-side.
- Centralized PII database creates GDPR Article 5(1)(e) storage limitation violation risk.
- Re-verification required per jurisdiction — a French eIDAS credential is not automatically accepted by a German-regulated platform.
The SOS ZK Identity Layer
1. OID4VP Zero-Knowledge Verification
SOS accepts the EU Digital Identity Wallet credential via OID4VP, issues a cryptographic attestation (SBT), and discards the raw assertion. The platform receives a boolean — verified / not verified — with no PII.
2. ISO 18013-5 Mobile Document Support
mDL (mobile driving licence) credentials in ISO 18013-5 format are natively supported. Physical document scanning is eliminated — the digital credential is the proof.
Result: eIDAS-Compliant, GDPR-Safe
Full EU Digital Identity Wallet verification without building a database of European citizen identities.
DLT Settlement Infrastructure
The EU Already Has a Live DLT Settlement Sandbox. The Finality Gap Remains.
The EU DLT Pilot Regime has been operational since March 2023 — but regulators acknowledge that cross-border blockchain settlement finality has no harmonized legal standard. SOS + TEA is the compliance layer that bridges this gap.
Mar 2023
DLT Pilot Regime live (EU 2022/858)
Oct 2027
EU moves to T+1 settlement
Dec 2025
Commission proposed MISP expansion
€6B
Aggregate cap for DLT Pilot scope
ESMA Market Surveillance Finding
“On-chain data does not provide sufficient information for market surveillance purposes and needs to be enriched with additional off-chain data.”
— NRF, June 2026 (citing ESMA study)
TEA solves this: Every TEA record carries SSIM-tagged semantic data and FATF travel rule hashes — enriched on-chain data that regulators can use for surveillance without requesting off-chain records.
Cross-Border Finality Gap
“At the moment of writing, there are no EU-level applicable rules governing the cross-border recognition of blockchain-based settlement finality across multiple jurisdictions.”
— Norton Rose Fulbright, “Regulation Around the World — Issue 18” (June 2026). Regulatory analysis cited for informational purposes. NRF does not endorse SOS or PACIO.
The gap: The DLT Pilot Regime permits DLT settlement systems, but no EU rules govern cross-border recognition of blockchain finality. TEA receipts provide cryptographic proof of finality, verifiable by any regulator independently.
December 2025 MISP amendments: The European Commission proposed expanding the DLT Pilot scope and adding a simplified regime for smaller infrastructures. The April 2025 Settlement Finality Directive consultation “explicitly addresses the applicability of both the CSDR and the SFD to DLT-based CSDs.” (NRF, June 2026) The regulatory infrastructure is catching up — SOS is ready now.
Developer Integration
Developer-First eIDAS Integration
Integrate with the SOS eIDAS verification endpoint in minutes. The API accepts OID4VP presentation requests, verifies the EU Digital Identity Wallet credential, and returns a cryptographic SBT attestation.
- ISO/IEC 18013-5 — Mobile Driving Licence (mDL) standard
- OpenID for Verifiable Presentations (OID4VP) — EU wallet protocol
- GDPR Articles 5, 17, 25 — data minimisation by architecture
// OID4VP authorization request — eIDAS wallet redirect
const response = await fetch("/api/sos/verify/eidas", {
method: "POST",
body: JSON.stringify({
presentationDefinition: EU_IDENTITY_SCHEMA,
redirectUri: "https://platform.example.com/callback",
nonce: crypto.randomUUID()
})
})
// Response: { verified: true, sbToken: "0xa9f3...", }
// No PII in response. Zero raw data stored.
eIDAS-Ready for European Markets
Do not let EU identity compliance create a GDPR liability. Verify European citizens with SOS — zero PII, full compliance.
No credit card required.
Free to get started.