igrantio-credential-schema-sca-payment-user

Defines the Payment User Credential (TS12) schema for iGrant.io OpenID4VCI credential definitions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issuing an SCA Payment User Credential (TS12) through the iGrant.io OpenID4VC API requires the exact claim path pointer schema published in the verifiable data registry, and this Skill supplies that schema so the credential definition matches the registry. ## Core Features & Use Cases - Registry-accurate schema: Provides the official dc+sd-jwt claim path pointer document for the Payment User Credential, which holds an empty claims array by design. - Credential definition request: Shows the exact JSON body for POST /v2/config/digital-wallet/openid/sdjwt/credential-definition, including vct, validationPath, and label rules. - Integration interview: Walks through environment, API key, format, issuance mode, revocation, signing, and trust list decisions before any code is written. - Use Case: A PSD2 payment service provider builds an issuer backend that issues SCA payment user credentials to EUDI wallets and needs the registry-compliant credential definition. ## Quick Start Ask your agent to create an iGrant.io credential definition for the Payment User Credential (TS12) using the dc+sd-jwt format with an empty claims array.

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

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

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

Send POST /v2/config/digital-wallet/openid/sdjwt/credential-definition with credentialFormat dc+sd-jwt, the vct set to the credential type URL with {baseUrl} replaced, validationPath "$", and an empty claims array. Always include version "version_01" and a non-reserved label.

Why does the Payment User Credential schema have an empty claims array?▼

The registry intentionally defines no claim path pointers for this credential because the binding to the payment service user comes from the credential itself, not from individual claims. Do not invent claim paths; request a schema extension from the registry maintainers if claims are needed.

Which credential formats does the Payment User Credential support?▼

The registry publishes this schema only in the dc+sd-jwt (SD-JWT VC) format. The jwt_vc_json and mso_mdoc formats are not available for this credential type.

What labels are reserved when creating an iGrant.io credential definition?▼

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

Do I need trust list registration to issue SCA payment credentials?▼

Yes, your issuer certificate must be registered in the iGrant.io trust list via support@igrant.io, otherwise wallets display the issued credentials as unverified. X.509 signing is required for trust list participation.