​

Scopes and verification tiers

Scopes and verification tiers are the machinery behind Sigil and the Stamped Mandate: the scopes describe what a user has authorised, and the tier describes how hard a verifier has to work to trust that authorisation. A scope is an SRI-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

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: 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 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 — the full scope catalogue with tier mapping
• Verification tiers — the verifier-side handbook
• Purchase Intents — what a scope sits on top of

​

Referenced from

• EIP-712 & Purchase Intents
• Verify a JWT
• Verify a PINT signature