igrantio-credential-schema-pda1

Provides claim path pointer schemas for issuing PDA1 social security credentials via OpenID4VC.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a Portable Document A1 (PDA1) credential definition requires the exact claim path pointers for every field of the six-section EU social security form, and hand-writing them across three credential formats is error-prone. This Skill supplies the registry-verified schema documents so an agent can configure PDA1 issuance or verification on the iGrant.io OpenID4VC API without guessing claim paths. ## Core Features & Use Cases - Registry-verified claim path documents: Ready-to-copy JSON claim definitions for the dc+sd-jwt, jwt_vc_json, and mso_mdoc formats, covering all six PDA1 sections (personal data, applicable legislation, status confirmation, employer activity, work places, issuing institution). - Format-specific guidance: Correct vct, type, doctype, namespace, validationPath, and claim carrier values for each format, including the mdoc namespace distinction between org.iso.18013.5.1 and org.iso.18013.5.1.pda1. - Structured integrator interview: A step-by-step questionnaire covering environment, format, issuance mode, revocation, signing, and trust list registration before any code is written. - Use Case: An issuer backend needs to offer PDA1 credentials to posted workers. The agent uses this Skill to build the credential definition with the exact SD-JWT VC claim paths, then hands off to the iGrant.io issuer API. ## Quick Start Ask your agent to build a PDA1 credential definition for the iGrant.io OpenID4VC API using the dc+sd-jwt format from this schema skill.

Frequently Asked Questions about igrantio-credential-schema-pda1

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

FAQPage Schema
How do I create a PDA1 credential definition for OpenID4VCI issuance?▼

Copy the claim path pointer JSON document for your chosen format from this schema and send it as the claims or credentialDefinition payload to the iGrant.io OpenID4VC API. The credentialType is PortableDocumentA1 and every claim in the schema is mandatory.

Which credential format should I use for PDA1: SD-JWT VC, jwt_vc_json, or mdoc?▼

The registry publishes all three formats for PDA1. The recommended default is dc+sd-jwt, which supports selective disclosure per claim and per section. Use mso_mdoc only when the rule book requires mdoc, which also needs X.509 signing.

What is the difference between the mdoc namespace and doctype for PDA1?▼

The doctype sent in the request is org.iso.18013.5.1.pda1, while the first element of every claim path is the mDoc namespace org.iso.18013.5.1. These are different strings and must be used exactly as the registry defines them.

Does jwt_vc_json support selective disclosure for PDA1 claims?▼

No. The jwt_vc_json document has no section-level pointers and no limitDisclosure field because the format does not support selective disclosure. Only dc+sd-jwt and mso_mdoc include limitDisclosure flags.

Why do wallets show my PDA1 credential as unverified?▼

Wallets mark credentials as unverified until the issuer certificate (the trust anchor) is registered in the trust list. Contact support@igrant.io and follow the trust-relying-party registration process to resolve this.