← ClaudeAtlas

igrantio-credential-schema-e-receiptlisted

Claim path pointer schema for the eReceipt credential (credential type VerifiablevReceiptSDJWT, namespace eu.europa.ec.eudi.verifiablereceipt) from the iGrant.io verifiable data registry. It holds 33 nested claims of a digital purchase receipt: seller address and party name, purchase_receipt lines and items, monetary_total, tax_total and tax_subtotal, payment and card account data, and delivery date and time. Use this skill when you create an eReceipt credential definition on the iGrant.io OpenID4VC API, or when you need the exact nested claim paths of a verifiable purchase receipt.
L3-iGrant/skills · ★ 1 · API & Backend · score 75
Install: claude install-skill L3-iGrant/skills
# eReceipt credential schema ## When to use Use this skill when you issue or ask for an **eReceipt**. The credential is a digital purchase receipt: what the customer bought, from which seller, for which amount, with which tax, by which payment means, and when the goods arrived. The claim names follow the business document vocabulary of an electronic invoice, so a receipt line is a `purchase_receipt_line` and a total is a `monetary_total`. The registry publishes this schema in **one format only: `dc+sd-jwt`** (SD-JWT VC). The metadata sets `isSdJwt` to `true`, and `isJwt` and `isMsoMdoc` to `false`. There is no JWT form and no mdoc form of this schema in the registry. 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