igrantio-credential-schema-boarding-passlisted

# Boarding Pass credential schema ## When to use Use this skill when you issue or ask for a **Boarding Pass**. The credential holds one travel ticket: who travels, on which vessel, from which port, at which time, and in which seat. The registry models a ferry boarding pass, and the same claims fit any scheduled trip with a departure port and an arrival port. 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 before you write code. 1. **Environment** - demo or staging? _Default demo (`