igrantio-credential-schema-lpidlisted

# Legal Person Identification Data (LPID) credential schema ## When to use Use this skill when you issue or ask for **Legal Person Identification Data**. LPID identifies an organisation, not a natural person. It is the company counterpart of the Person Identification Data (PID) credential, and it is the base identity credential of a European Business Wallet (EUBW). The schema holds two claims: the registered identifier of the organisation and its legal name. The registry publishes this schema in **all three formats**: | Format | Metadata flag | Identifier to send | | --- | --- | --- | | `dc+sd-jwt` | `isSdJwt: true` | `vct` | | `jwt_vc_json` | `isJwt: true` | `type` | | `mso_mdoc` | `isMsoMdoc: true` | `doctype` | This page describes registry version **2025.7.1**, the latest version of the template. ## Prerequisites - An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from [support@igrant.io](mailto:support@igrant.io). Keep it on the server, in an environment variable or a secret manager. The browser never sees it. - The **OWS environment** the key belongs to. The default is **demo** (`https://demo-api.igrant.io`). Use **staging** (`https://staging-api.igrant.io`) only when the integrator asks for it. A key works only in its own environment. ## Ask the integrator first Ask one question at a time. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framework, environment variables, an existing backen