> ## Documentation Index > Fetch the complete documentation index at: https://docs.sumvin.com/llms.txt > Use this file to discover all available pages before exploring further. # Glossary > Grouped index of Sumvin terms, each linking to its canonical reference. Terms used across the Sumvin docs, grouped by domain. Each entry links to the canonical reference where the term is defined in full. ## Products The names Sumvin is described by. Each maps to a technical primitive on the wire — the API, headers, scopes, and error codes are unchanged. * **Sigil** — Sumvin's portable, KYC-verified identity: "Proof of Personhood" a user carries across products. On the wire, Sigil is the `SRI` identity system — identity tokens, scopes, and verification. [Identity overview](/identity/overview) * **Stamped Mandate** — A signed authorisation a user grants for specific scoped actions. Delivered over the API as a PINT (header `x-sumvin-pint-token`). [Purchase Intents](/identity/pint) * **Errand** — An agent's scope-bound tasking run: Intent → Authorization → Vigilance. On the wire, an Errand is driven by the `IPA` (Intelligent Purchase Authorisation) routes and lifecycle. [Errand overview](/products/errand/overview) * **Envoy** — The money agent that acts on a user's behalf, executing Errands against their Stamped Mandates. [Agent flows](/overview/personas/agent-flows) * **Atomic Money** — Sumvin's payments umbrella: ramps, card issuing, x402, and payment links. [Ramps & banking](/products/atomic-money/overview) ## Identity & users * **Applicant** — The KYC applicant record created when a user starts identity verification. [KYC guide](/guides/kyc) * **KYC** — Know Your Customer. The identity-verification process that feeds attestation claims onto a PINT JWT. [KYC and attestation](/concepts/kyc-and-attestation) * **Onboarding step** — A single stage in the user onboarding state machine (for example, `kyc_verification`, `card_setup`). [Onboarding state machine](/concepts/onboarding-state-machine) * **Partner** — An integrator using Sumvin, addressed via their SIS API key and their SIS Dashboard organisation. * **SRI** — Sumvin Resource Identifier. URI-style identifier for users, resources, and capabilities. The wire identity system behind **Sigil**. [SRI reference](/identity/sri) ## Signing, keys & wallets * **EIP-712** — The Ethereum typed-data signing standard used for Purchase Intents. [EIP-712 & Purchase Intents](/identity/pint) * **EIP-1271** — The contract-based signature verification standard used by Safe smart accounts. [Safes and identity](/concepts/safes-and-identity) * **EOA** — Externally owned account. A single-keypair Ethereum address, distinct from a Safe smart account. [Wallets guide](/guides/wallets) * **Safe** — The user's smart-account wallet, deployed per chain, acting as the on-chain identity anchor. [Safes and identity](/concepts/safes-and-identity) * **Sei** — The L1 blockchain Sumvin defaults to (chain ID `1329`). [Wallets guide](/guides/wallets) ## Purchase intents & authorisation * **IPA** — Intelligent Purchase Authorisation. An ongoing, scope-bound authorisation for an agent to execute purchases across a time window. The wire primitive that powers an **Errand**. [IPA guide](/guides/ipa) * **Nonce** — The monotonically increasing per-wallet counter on a PINT, used for replay prevention. [Nonces](/identity/nonces) * **PINT** — Purchase Intent. An EIP-712 signed message authorising specific scopes and actions. The wire artifact a **Stamped Mandate** is delivered as (header `x-sumvin-pint-token`). [Purchase Intents](/identity/pint) * **Revocation** — Invalidating a PINT and every JWT issued against it before their natural expiry. [Revocation](/concepts/revocation) * **Scope** — An SRI-format capability string carried on a signed PINT. [Scopes reference](/identity/scopes) * **x402** — The HTTP 402 Payment Required pattern for machine-to-machine PINT settlement. [Payment Links and x402](/concepts/payment-links-x402) ## JWTs & verification * **Audience** — The `aud` JWT claim identifying the intended verifier. A verifier must match its registered identifier against this claim. [Verify a JWT](/merchant/verify-jwt) * **Claim** — A named field on a JWT payload (for example, `kyc_status`, `age_over_18`, `scopes`). [JWT reference](/identity/jwt) * **Enhanced Tier** — A verification tier requiring both JWT validation and verification of the original PINT's EIP-712 signature. Triggered by the value-moving `spend` scopes. [Verification tiers](/merchant/verification-tiers) * **JWKS** — JSON Web Key Set. The public-key document a verifier uses to validate PINT JWTs. [JWKS](/merchant/jwks) * **JWT** — JSON Web Token. The SIS-issued credential a verifier receives on inbound requests. [JWT reference](/identity/jwt) * **KID** — The `kid` identifier on a JWK or JWT header. Tells the verifier which JWKS key signed a given JWT. [JWKS](/merchant/jwks) * **Standard Tier** — A verification tier requiring only JWT validation. Applies to every scope outside the value-moving `spend` set. [Verification tiers](/merchant/verification-tiers) * **Subject** — The `sub` JWT claim. Carries the user's SRI. [JWT reference](/identity/jwt) * **Verification tier** — The level of verification a verifier must perform on a PINT credential. Either Standard or Enhanced. [Scopes and verification tiers](/concepts/scopes-and-tiers) * **Verifier** — Any service receiving a Sumvin PINT JWT on an inbound request. [Verifier Guide overview](/merchant/overview) ## Platform & SIS dashboard * **CORS origin** — The browser origin allow-list tying an environment to the domains that may present credentials to SIS. [CORS origins](/dashboard/cors-origins) * **Environment** — An isolated namespace inside an organisation, with its own auth provider and SDK credentials. [Environments](/dashboard/environments) * **Organisation** — A partner tenant in the SIS Dashboard, containing one or more environments. [Organisations](/dashboard/organisations) * **SIS** — Sumvin Identity Service. The B2B API surface that exchanges signed PINTs for JWTs and exposes user data by SRI. [Platform API vs SIS](/concepts/platform-vs-sis) ## Cards, ramps & banking * **Funding wallet** — The Safe on a card's chain that the card draws balance from. [Funding wallets](/products/card-issuing/funding-wallets) * **Meld** — On/off-ramp partner handling buy, sell, and bank linking flows through a hosted widget. Part of **Atomic Money**. [Ramps & banking](/products/ramps/overview) * **PAN** — Primary account number. The card's full number, never exposed through standard card management endpoints. [Card management API](/products/card-issuing/card-management-api) * **Processor token** — A short-lived token produced during bank linking and used to initiate movement through a downstream processor. * **Ramp session** — A Meld-backed session moving value between fiat and crypto. [Ramp sessions](/concepts/ramp-sessions) ## API conventions * **HAL** — Hypermedia Application Language. The link format (`_links`) Sumvin uses on every response. [API conventions](/api-conventions) * **RFC 7807** — The Problem Details spec Sumvin uses for every error response. [Error handling](/error-handling) * **Webhook** — An inbound HTTP callback. Sumvin consumes KYC and Meld webhooks internally; partner-facing webhooks are roadmap.