What problem does it solve? Issuing an EUDI Wallet Payment Account Credential (TS12) requires an exact claim path pointer schema from the verifiable data registry, and hand-writing it risks mismatched claim paths, wrong vct values, or broken selective disclosure. This Skill provides the registry-accurate schema and the iGrant.io API request structure to create the credential definition correctly. ## Core Features & Use Cases - Registry-Accurate Schema: Ships the dc+sd-jwt claim path pointer document for the Payment Account Credential with three mandatory, selectively disclosable claims: iban, bic, and currency. - iGrant.io API Integration: Shows how to create the credential definition via POST /v2/config/digital-wallet/openid/sdjwt/credential-definition, including vct placeholder replacement, label rules, and version requirements. - Claim Path Pointer Guidance: Explains how to read and write claim path pointers across dc+sd-jwt, jwt_vc_json, and mso_mdoc formats. - Use Case: A fintech backend developer needs to issue SCA payment account credentials under PSD2. The Skill walks them through an integrator interview (environment, API key, issuance mode, revocation, signing, trust list) and produces the exact credential definition payload. ## Quick Start Ask your agent to create an iGrant.io credential definition for the Payment Account Credential using the dc+sd-jwt schema with iban, bic, and currency claims.
