igrantio-credential-schema-sca-payment-card

Defines the SD-JWT VC claim path pointer schema for the EUDI Wallet Payment Card Credential (TS12).

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a Payment Card Credential (TS12) definition for the iGrant.io OpenID4VC API requires the exact claim path pointer structure from the verifiable data registry, and hand-writing it risks schema mismatches that break issuance or wallet display. ## Core Features & Use Cases - Registry-Accurate Schema: Provides the exact dc+sd-jwt claim path pointer document for the Payment Card Credential with three mandatory, selectively disclosable claims: pan_last_four, scheme, and scheme_logo. - API Integration Guidance: Shows how to create a credential definition via POST /v2/config/digital-wallet/openid/sdjwt/credential-definition, including the vct placeholder replacement and reserved-label rules. - Use Case: An integrator building an SCA payment credential issuer asks the agent to create a Payment Card credential definition; the skill supplies the registry claims array, walks through environment, format, revocation, and trust-list questions, and produces a valid API request. ## Quick Start Ask your agent to create a Payment Card Credential (TS12) definition for the iGrant.io OpenID4VC API using the registry claim path pointer schema.

Frequently Asked Questions about igrantio-credential-schema-sca-payment-card

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

FAQPage Schema
How do I create a Payment Card Credential definition with the iGrant.io API?▼

Create a credential definition with POST /v2/config/digital-wallet/openid/sdjwt/credential-definition, placing the registry claims array into the configuration entry and setting vct to the credential type with {baseUrl} replaced. Send version as version_01 and keep the returned id for the issue operation.

What claims does the Payment Card Credential (TS12) contain?▼

The schema defines three mandatory claims: pan_last_four (last four digits of the primary account number), scheme (the card scheme), and scheme_logo (the scheme logo for the wallet card view). All three set limitDisclosure to true for selective disclosure.

Which credential formats does the Payment Card Credential schema support?▼

The registry publishes this schema in one format: dc+sd-jwt (SD-JWT VC), version 2025.7.1. The metadata sets isScaCredential to true, marking it as a strong customer authentication credential.

Can I store the full card number in the Payment Card Credential?▼

No. The schema intentionally holds only pan_last_four for identification, so the credential shows the card without the data a payment needs. Never put the full primary account number in this credential.

Why does my credential definition label get rejected by the iGrant.io API?▼

The platform reserves the labels Payment Card Credential, Payment User Credential, Payment Account Credential, PID Issuance, and Photo ID Issuance. Pick another label of at least 3 characters, such as Issue Payment Card.