igrantio-credential-schema-photo-id

Provides claim path pointer schemas for issuing EUDI Wallet Photo ID credentials.

1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/L3-iGrant/skills --skill igrantio-credential-schema-photo-id-l3-igrant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: igrantio-credential-schema-photo-id
Source: https://github.com/L3-iGrant/skills/tree/main/credential-schemas/igrantio-credential-schema-photo-id
Command: npx skills add https://github.com/L3-iGrant/skills --skill igrantio-credential-schema-photo-id-l3-igrant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a Photo ID credential definition for the iGrant.io OpenID4VC API requires the exact claim paths from the verifiable data registry, and hand-writing them across three credential formats is error-prone. This Skill supplies the registry-accurate claim path pointer documents so the credential definition matches the ISO/IEC 23220 Photo ID specification. ## Core Features & Use Cases - Registry claim path documents: Ready-to-copy claims arrays for the dc+sd-jwt, jwt_vc_json, and mso_mdoc formats of credential type eu.europa.ec.eudi.photoid.1, covering the iso23220, photoid, and dtc claim groups. - Format-specific configuration facts: The vct, type, doctype, validationPath, and claim carrier values each format requires when calling the iGrant.io credential-definition endpoint. - Guided setup interview: A one-question-at-a-time flow that locks the environment, format, issuance mode, revocation, signing, and trust-list registration before any code is written. - Use Case: An integrator building an OpenID4VCI issuer asks the agent to create a Photo ID credential definition; the agent copies the registry claims array into the POST /v2/config/digital-wallet/openid/sdjwt/credential-definition request with the correct format fields. ## Quick Start Ask your agent to create a Photo ID credential definition on the iGrant.io demo environment using the dc+sd-jwt format from this skill.

Frequently Asked Questions about igrantio-credential-schema-photo-id

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Photo ID credential definition with the iGrant.io API?▼

Call POST /v2/config/digital-wallet/openid/sdjwt/credential-definition with a credentialDefinitions entry whose credentialFormat, vct or doctype, and validationPath match the format table, and paste the registry claims array into the claims field. Always send version as version_01 and keep the returned id for the issue operation.

What claims does the EUDI Photo ID credential contain?▼

The schema groups claims into iso23220 core person data such as names, birth date, portrait, and residence, photoid extras like person_id and travel_document_number, and dtc digital travel credential data groups dg1 through dg16. Every claim in this schema is mandatory.

Which credential formats does the Photo ID schema support?▼

The registry publishes the Photo ID schema in three formats: dc+sd-jwt (SD-JWT VC), jwt_vc_json (W3C VC), and mso_mdoc (mdoc). The recommended default is dc+sd-jwt unless the rule book requires mdoc, which needs X.509 signing.

How do claim path pointers differ between SD-JWT VC and mso_mdoc?▼

For mso_mdoc the first path element is the mDoc namespace eu.europa.ec.eudi and every path has at least two elements, while dc+sd-jwt paths start directly with the claim group. The jwt_vc_json format prefixes every path with credentialSubject and has no limitDisclosure field.

Why does my wallet show Photo ID credentials as unverified?▼

Wallets mark credentials unverified when the issuer certificate is not registered in the trust list. Register the trust anchor by contacting support@igrant.io and following the trust-list registration guide before issuing credentials.