igrantio-credential-schema-passport

Provides claim path pointers for issuing Passport credentials in SD-JWT, JWT VC, and mdoc formats.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers integrating with the iGrant.io OpenID4VC API need the exact claim path pointers for the Passport credential schema across three credential formats, and manually constructing these paths risks mismatches with the verifiable data registry. ## Core Features & Use Cases - Claim Path Pointer Documents: Ready-to-use claims arrays for dc+sd-jwt, jwt_vc_json, and mso_mdoc formats covering serialNumber, firstName, lastName, birthDate, nationality, personalNumber, image, signature, and more. - Credential Definition Guidance: Shows how to POST a credential definition to the iGrant.io API with correct vct, type, doctype, validationPath, and revocation settings per format. - Use Case: Build an issuer backend that issues digital passports for a border check or hotel check-in flow, with selective disclosure so holders can reveal nationality while keeping their personal number hidden. ## Quick Start Ask your agent to create a Passport credential definition on the iGrant.io OpenID4VC API using the dc+sd-jwt claim paths from this schema.

Frequently Asked Questions about igrantio-credential-schema-passport

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

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

Send a POST request to /v2/config/digital-wallet/openid/sdjwt/credential-definition with one entry per format in credentialDefinitions. Copy the claims array from the matching schema document, set vct to Passport for dc+sd-jwt or doctype to org.iso.18013.5.1.passport for mso_mdoc.

What claims does the Passport credential schema contain?▼

The schema holds serialNumber, firstName, lastName, birthDate, gender, nationality, personalNumber, expiryDate, issuerAuthority, image, and signature. The jwt_vc_json and mso_mdoc documents add an id claim for the credential subject identifier, giving 12 claims instead of 11.

Which credential format should I use for a digital passport?▼

The registry publishes dc+sd-jwt, jwt_vc_json, and mso_mdoc versions of the same schema. The recommended default is dc+sd-jwt unless the applicable rule book requires mdoc, which uses doctype org.iso.18013.5.1.passport.

Does the Passport credential support selective disclosure?▼

Yes, every claim sets limitDisclosure to true, so holders can reveal individual claims like nationality while hiding others. This takes effect for dc+sd-jwt and mso_mdoc; jwt_vc_json carries the field but has no selective disclosure capability.

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

The mdoc namespace is org.iso.18013.5.1 and prefixes every claim path, while the doctype is org.iso.18013.5.1.passport and identifies the credential type. Every path in an mso_mdoc configuration must start with the same namespace element.