NEW
Report & API Now Live! Data insights report and open data API endpoints live as of September 23, 2025

EWC RFC005: Issue Legal Person Identification Data (LPID)

type
Standard
Documentation

Description

Description
Source

Legal Person Identification Data (LPID) is a standardized digital credential format for representing organizational identities within the European Wallet Ecosystem. This specification implements the OpenID4VCI workflow for issuing LPID credentials by government-approved identity providers, ensuring high assurance and interoperability across the ecosystem.

The standard enables organizations to obtain verified digital identities that can be stored in digital wallets and used for secure authentication and identification purposes. LPID credentials contain essential organizational information like legal entity identifiers and official names, issued by authorized government bodies.

Key differentiating features include:

  • Mandatory authentication at LoA High level for natural persons requesting LPID
  • Verification of representative rights and legal person status
  • Support for both wallet-initiated and provider-initiated issuance flows
  • Integration with national business registries as authentic data sources
  • Standardized credential format based on vc+sd-jwt

Purpose and Scope:

  • Enable standardized issuance of verified organizational identities
  • Establish interoperable processes across EU Member States
  • Define security and trust requirements for LPID issuance
  • Support eIDAS2 compliance for organizational wallets

Technical Specifications:

  • Uses OpenID Connect and OAuth 2.0 protocols
  • Implements OID4VCI credential issuance flow
  • Supports both authorization code and pre-authorized code flows
  • Defines standard LPID schema with mandatory attributes:
    • legal_person_id (EUID format)
    • legal_person_name
    • Required metadata fields

Implementation Requirements:

  1. PID Provider must:

    • Authenticate users at LoA High
    • Verify representative rights
    • Access authentic business registry data
    • Implement revocation capabilities
  2. Wallet must:

    • Support vc+sd-jwt credential format
    • Implement OpenID4VP protocol
    • Maintain Wallet Instance Attestation
    • Handle credential storage securely

Security Considerations:

  • Mandatory high assurance authentication
  • Trust anchor verification for issuers
  • Wallet conformity validation
  • Credential status verification
  • Secure credential storage requirements

Interoperability Features:

  • Standardized LPID schema
  • Common credential format
  • Unified issuance protocols
  • Cross-border recognition
  • Integration with EUDI Wallet Architecture

Current Adoption Status:

In pilot phase with multiple EU Member States implementing the specification through their business registries and identity providers.

Statistics

Projects Following
Source
0

Under Management at

Projects Following or working on this Standard

If you are featured in the Web of Trust Map and wish to exercise your GDPR rights, including the right to be forgotten, visit the privacy policy page