← ClaudeAtlas

igrantio-credential-schema-loyalty-cardlisted

Claim path pointer schema for the Loyalty Card credential (credential type LoyaltyCard, mdoc doctype eu.europa.ec.eudi.loyaltycard) from the iGrant.io verifiable data registry. It holds 25 nested claims in five groups: credential, customer, loyalty_card, organization and portfolio, with the card identifier and status, the customer contact data, and the available points, miles and wallet balance. The registry publishes it in all three formats: dc+sd-jwt, jwt_vc_json and mso_mdoc. Use this skill when you create a loyalty card credential definition on the iGrant.io OpenID4VC API.
L3-iGrant/skills · ★ 1 · API & Backend · score 75
Install: claude install-skill L3-iGrant/skills
# Loyalty Card credential schema ## When to use Use this skill when you issue or ask for a **Loyalty Card**. The credential holds the membership of a customer in a loyalty programme: the card identifier and its status, the organisation that runs the programme, the contact data of the customer, and the balance of points, miles and wallet money. The registry publishes this schema in **all three formats**: | Format | Metadata flag | Identifier to send | | --- | --- | --- | | `dc+sd-jwt` | `isSdJwt: true` | `vct` | | `jwt_vc_json` | `isJwt: true` | `type` | | `mso_mdoc` | `isMsoMdoc: true` | `doctype` | This page describes registry version **2025.7.1**, the latest version of the template. ## Prerequisites - An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from [support@igrant.io](mailto:support@igrant.io). Keep it on the server, in an environment variable or a secret manager. The browser never sees it. - The **OWS environment** the key belongs to. The default is **demo** (`https://demo-api.igrant.io`). Use **staging** (`https://staging-api.igrant.io`) only when the integrator asks for it. A key works only in its own environment. ## Ask the integrator first Ask one question at a time. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framework, environment variables, an existing backend) instead of asking for them. Record the answers before you write code. 1. **Environment** - demo or staging? _Defa