igrantio-credential-schema-payment-wallet-attestation

Defines the Payment Wallet Attestation claim path schema for iGrant.io OpenID4VC credential issuance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issuing or requesting a Payment Wallet Attestation requires knowing the exact claim structure, mandatory fields, and credential definition format expected by the iGrant.io OpenID4VC API, and getting any of these wrong produces invalid credentials. ## Core Features & Use Cases - Claim Path Schema: Provides the full claim path pointer document for the Payment Authenticator (v2) credential, covering the eight fundingSource claims (aliasId, currency, icon, iin, panLastFour, parLastFour, scheme, type) in dc+sd-jwt format. - Credential Definition Setup: Shows how to create a credential definition via POST /v2/config/digital-wallet/openid/sdjwt/credential-definition with the correct vct, validationPath, and revocation settings. - Transaction Data Validation: Explains how to submit the attestation to the transaction-data endpoint for Strong Customer Authentication and payment flows. - Use Case: A developer building a PSD2 payment flow uses this skill to configure an issuer backend that issues payment wallet attestations and validates transaction data carrying a paymentWalletAttestation. ## Quick Start Use the payment wallet attestation schema skill to create a credential definition for the PaymentWalletAttestation type on the iGrant.io demo environment.

Frequently Asked Questions about igrantio-credential-schema-payment-wallet-attestation

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

FAQPage Schema
How do I create a Payment Wallet Attestation credential definition on iGrant.io?▼

Send a POST request to /v2/config/digital-wallet/openid/sdjwt/credential-definition with credentialFormat set to dc+sd-jwt, vct set to PaymentWalletAttestation, validationPath set to $, and the schema's claims array copied into claims.claims.

What claims does the Payment Wallet Attestation schema contain?▼

The schema holds eight mandatory claims nested inside a fundingSource object: aliasId, currency, icon, iin, panLastFour, parLastFour, scheme, and type. All claims have limitDisclosure set to true, so holders can reveal them selectively.

Which credential formats does the Payment Wallet Attestation support?▼

The registry publishes this schema only in dc+sd-jwt (SD-JWT VC) format. The metadata sets isSdJwt to true and isJwt and isMsoMdoc to false, so there is no JWT or mdoc form of this schema.

How do I validate transaction data with a paymentWalletAttestation?▼

Send the attestation to POST /v2/config/digital-wallet/openid/sdjwt/transaction-data in the paymentWalletAttestation field, with transactionDataHashesAlg set to ["sha-256"]. This checks a transaction that the holder approved.

Does the Payment Wallet Attestation contain the full card number?▼

No, the credential never carries the full card number. It only holds truncated identifiers such as panLastFour and parLastFour, plus the aliasId token that names the payment instrument.

What prerequisites are needed to issue this credential?▼

You need an iGrant.io Organisation Wallet Suite API key for the demo or staging environment, obtained from support@igrant.io. For trust list recognition, your issuer certificate must also be registered following the iGrant.io trust list documentation.