Skip to content
VC.00EU Digital Identity Wallet

eIDAS 2.0 alignment, Wallet-ready by mandate.

EU Regulation 2024/1183 mandates Member-State Digital Identity Wallets in production by 2026. Identra is positioned as a conformant relying party + verifiable-credentials issuer, with W3C VC 2.0 data model, decentralised identifiers and the OID4VCI / OID4VP presentation protocols underpinning the rollout.

VC.CBCapability board · six surfaces

Six capabilities, one trust framework.

  • VC.01Preview

    W3C Verifiable Credentials issuance

    Identra issues verifiable credentials in the W3C VC 2.0 data model with JWS / SD-JWT proofs. Subject DIDs, issuer DIDs, status-list 2021 revocation list — all spec-conformant.

    Target · Q2 2026
  • VC.02Roadmap

    EUDI Wallet relying-party

    Identra acts as a relying party against any conformant EU Digital Identity Wallet implementation. OID4VP presentation request flow, SD-JWT verification, trust-list anchored issuer validation.

    Target · Q3 2026
  • VC.03Preview

    Decentralised Identifiers (DIDs)

    did:web and did:key supported across Identra subject and issuer roles. Resolution via the conventional /.well-known/did.json endpoint plus universal resolver fallback.

    Target · Q2 2026
  • VC.04Live

    Qualified electronic signatures

    eIDAS LoA-substantial flows (live) extending to qualified electronic signatures (QES) for natural persons and qualified electronic seals (QESeal) for organisations.

  • VC.05Roadmap

    Cross-border attribute exchange

    eIDAS-aligned cross-border attribute exchange via the eIDAS Network and via OID4VP presentations across EU member-state Wallet implementations.

    Target · Q3 2026
  • VC.06Live

    Qualified Trust Service Provider

    QTSP partnership lineage on file under MNDA. Identra qualified-flows execute under the partner QTSP’s trust-list anchoring; Identra’s own QTSP designation is in flight.

VC.RGRegulatory anchor table

Tracked against every layer of the spec stack.

CodeFrameworkPurposeDeadline / status
VC.RG.01EU Regulation 2024/1183eIDAS 2.0 framework: EU Digital Identity Wallet mandate.Member-state Wallets in production by 2026
VC.RG.02EU Implementing Acts (ARF)Architecture Reference Framework for the EU Digital Identity Wallet — interoperability profiles.Conformance baseline · 2025-2026
VC.RG.03OpenID for Verifiable CredentialsOID4VCI (issuance) + OID4VP (presentation) protocols underpinning EUDI Wallet.Final 1.0 spec · 2025
VC.RG.04W3C VC Data Model 2.0Verifiable Credentials data model; underpins issuance and verification semantics.Recommendation · 2024
VC.RG.05ETSI EN 319 411-2Policy and security requirements for QTSPs issuing qualified certificates.Anchored via partner QTSP
VC.PTPresentation pattern

How a relying party asks the citizen to prove something.

Civitas service templates issue presentation requests through Identra. The citizen receives the request inside their EU Digital Identity Wallet, picks the credentials to present, and the verifier returns a signed presentation under audit envelope.

  • OID4VP authorization request
  • Selective disclosure (SD-JWT)
  • Trust-list anchored issuer validation
  • Presentation receipt returned to the relying party
OID4VP · presentation request
# 1. Relying party (Civitas) opens an authorization request.
POST https://identra.flyttgo.tech/v1/oid4vp/request
{
  "presentation_definition": {
    "input_descriptors": [
      {
        "id": "qualified_id",
        "format": { "vc+sd-jwt": {} },
        "constraints": {
          "fields": [
            { "path": ["$.vct"],         "filter": { "const": "EuPidCredential" } },
            { "path": ["$.given_name"],  "intent_to_retain": false }
          ]
        }
      }
    ]
  }
}

# 2. Citizen Wallet returns a signed VP token.
{
  "vp_token": "eyJhbGc...",
  "presentation_submission": { ... },
  "state": "civitas_app_82..."
}

# 3. Identra verifies + writes the presentation receipt
#    into the audit envelope. Civitas template proceeds.