Legal Person Identification Data
This workflow implements European Wallet Consortium (EWC) RFC005 and employs the OpenID4VCI Issue Credential (In-Time) or OpenID4VCI Issue Credential (Deferred) protocol to issue Legal Person Identification Data (LPID). The steps below outline the process using OpenID for Verifiable Credentials Issuance (OpenID4VCI). This process adheres to the OpenID4VCI specification and is illustrated in the diagram below:
Step 1: Get the API Key (Issuer Admin)
To obtain your API key, please contact [email protected]. Once you have received your API key, enter it in the field below and click the Set API Key button to save it for future use.
Step 2: Create Credential Definition (LPID Issuer Admin)
Copy the code block below to create a credential definition as per EWC RFC005. Execute the API available here. From the API response, copy the credentialDefinitionId for use in Step 3.
Request
Response
Step 3: Request and Issue Credential (LPID Issuer: E.g. Bolagsverket or similar)
Before the issuance validation takes place, the legal person submits a request for the issuance of an LPID. In this step, the legal person provides the Organisation Wallet Suite endpoint where the LPID should be issued. If the holder wallet does not expose a <credentialOfferEndpoint>, issuance can still proceed by sharing the credential offer manually (e.g., via QR code). When a <credentialOfferEndpoint> is configured, the issuer can push the offer directly to the holder wallet, enabling issuer-initiated credential issuance.
After completing the required validations, the Issuer proceeds to issue the Legal Person Identification Data (LPID) in deferred mode. Replace <credentialDefinitionId> with the actual ID obtained in the previous steps. You can run the JSON code block below using the Run button. Alternatively, use the JSON code block below to structure your request and execute it via the API available here. From the API response, copy the credential.id for use in Step 5. This ID is referred to as the <credentialConfigurationId>. Note that this id is not returned or required for the DRAFT_11 credential format.
Request
Response
Step 4: Receive Credential Offer (Legal Person/Holder)
The holder's wallet receives the credential at the configured Organisation Wallet Suite endpoint.
Step 5: Update Credential Offer (Issuer)
Use the code block below to update the credential offer. In the request payload, set the credential.id to the <credentialConfigurationId> value obtained from the response in Step 3. This ensures the correct Legal PID credential configuration is updated. From the response, use the credentialExchangeId as the path parameter and execute the API available here.
Path Parameter
Request
Response
Try It Yourself (With Demo Video)
Legal Person Identification Data Demo: Learn how to issue Legal Person Identification Data (LPID) using OpenID4VCI protocol with iGrant.io Digital Wallets.