> ## 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.

# Scopes and verification tiers

> How the scopes on a PINT decide how deeply a verifier has to validate it.

# Scopes and verification tiers

Scopes and verification tiers are the machinery behind <Tooltip headline="Sigil" tip="Sumvin's portable, KYC-verified identity — Proof of Personhood." cta="Glossary →" href="/glossary">Sigil</Tooltip> and the <Tooltip headline="Stamped Mandate" tip="A signed authorisation a user grants for specific scoped actions — delivered on the wire as a PINT." cta="Glossary →" href="/glossary">Stamped Mandate</Tooltip>: the scopes describe what a user has authorised, and the tier describes how hard a verifier has to work to trust that authorisation.

<Snippet file="product-term-disambiguation.mdx" />

A **scope** is an <Tooltip headline="SRI" tip="Sumvin Resource Identifier — URI-style identifier for users and capabilities." cta="Glossary →" href="/glossary">SRI</Tooltip>-format capability string carried on a signed Stamped Mandate. A **verification tier** is how much work the verifier has to do to trust the resulting credential. The scopes on the mandate drive the tier.

A Stamped Mandate is delivered on the wire as a `PINT` (header `x-sumvin-pint-token`); the scope and tier vocabulary below is the same whether you read it as a Stamped Mandate or as its underlying PINT.

## Two tiers, one rule

| Tier         | What the verifier checks                                                   | When                                          |
| ------------ | -------------------------------------------------------------------------- | --------------------------------------------- |
| **Standard** | SIS-issued JWT only — signature, audience, expiry                          | The mandate carries only Standard-tier scopes |
| **Enhanced** | JWT **plus** the original PINT's EIP-712 signature against the user's Safe | Any Enhanced-tier scope is present            |

The rule: if any scope on the mandate is Enhanced, the entire JWT is issued at Enhanced tier. Mixed-tier mandates are not downgraded.

## What triggers Enhanced

Enhanced is reserved for the `spend` scopes that move value on the user's behalf:

| Scope                            | Authorises                                                   |
| -------------------------------- | ------------------------------------------------------------ |
| `sr:us:pint:spend:execute`       | On-chain spend via Safe, IPA auto-execute, or a strategy run |
| `sr:us:pint:spend:visa_checkout` | Card checkout on the Visa Intelligent Commerce rail          |
| `sr:us:pint:spend:card`          | Pinning a card checkout to a specific enrolled card          |

The tier exists so that a merchant accepting a spend-authorising mandate can verify it without trusting SIS as a single point of failure.

Every other scope — identity attestations, account and transaction reads, card reads, Errands, ramp, and the personal-finance read/manage scopes — is Standard. The `Tier` column of the [scopes reference](/identity/scopes#scope-catalog) is the authoritative list.

## Why a verifier should care

* **Standard is a one-call check.** Fetch JWKS once, cache it, verify JWTs locally. No per-request call to Sumvin.
* **Enhanced is a two-piece check.** You additionally fetch the original PINT payload from `X-Pint-Payload`, the signature from `X-Pint-Signature`, and verify the EIP-712 hash against the user's Safe via EIP-1271. The JWT alone is not sufficient for an Enhanced credential.

## See also

* [Scopes reference](/identity/scopes) — the full scope catalogue with tier mapping
* [Verification tiers](/merchant/verification-tiers) — the verifier-side handbook
* [Purchase Intents](/identity/pint) — what a scope sits on top of

## Referenced from

* [EIP-712 & Purchase Intents](/identity/pint)
* [Verify a JWT](/merchant/verify-jwt)
* [Verify a PINT signature](/merchant/verify-pint-signature)