igrantio-credential-schema-pid-v2

Provides claim path pointer schemas for issuing ARF 2.8.0 PID credentials via the iGrant.io OpenID4VC API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building an EU ARF 2.8.0 Person Identification Data (PID) credential definition requires exact claim path pointers, mandatory flags, and format-specific claim names for SD-JWT VC and mso_mdoc, and getting any of these wrong breaks issuance or wallet interoperability. ## Core Features & Use Cases - Registry-verified schemas: Ships the exact claim path pointer documents for dc+sd-jwt (urn:eudi:pid:1) and mso_mdoc (eu.europa.ec.eudi.pid.1), including which claims are mandatory. - API integration guidance: Shows how to create a credential definition with POST /v2/config/digital-wallet/openid/sdjwt/credential-definition, including reserved labels, versioning, and multi-format entries. - Use Case: An integrator building an EUDI Wallet issuer backend uses this skill to configure a PID credential definition with the correct claims, then issues credentials that wallets recognize as verified under eIDAS 2.0. ## Quick Start Ask your agent to create an iGrant.io credential definition for the ARF 2.8.0 PID credential in dc+sd-jwt format using this schema.

Frequently Asked Questions about igrantio-credential-schema-pid-v2

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

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

Send a POST request to /v2/config/digital-wallet/openid/sdjwt/credential-definition with the claims array from the registry document, setting vct to urn:eudi:pid:1 for dc+sd-jwt or doctype to eu.europa.ec.eudi.pid.1 for mso_mdoc. Always include version set to version_01.

What claims are mandatory in the ARF 2.8.0 PID credential?▼

Mandatory claims include given_name, family_name, birthdate, place_of_birth with country, locality and region, nationalities, issuing_authority, issuing_country, and the expiry date. Claim names differ slightly between dc+sd-jwt and mso_mdoc formats.

What is the difference between dc+sd-jwt and mso_mdoc for PID credentials?▼

dc+sd-jwt uses credential type urn:eudi:pid:1 with nested address claims, while mso_mdoc uses doctype eu.europa.ec.eudi.pid.1 as the first path element with flat resident_* claims. Both formats support selective disclosure via limitDisclosure.

Does this PID schema support the jwt_vc_json format?▼

No, the registry publishes this ARF 2.8.0 PID schema only in dc+sd-jwt and mso_mdoc formats. The jwt_vc_json format is not part of this template and lacks selective disclosure support.

Why does my wallet show issued credentials as unverified?▼

Wallets show credentials as unverified when the issuer certificate is not registered in the trust list. Contact support@igrant.io and follow the trust-relying-party registration process before issuing production credentials.