Skip to main content
Sumvin ID is a portable, verifiable digital identity anchored to -verified users. It enables users — and their AI agents — to prove who they are across third-party services without repeatedly sharing personal data. The identity is not a record you look up. It’s a credential the user carries, cryptographically. The system is built on three pillars:
  1. Non-custodial smart account wallets — each user gets a Safe multisig wallet that serves as their on-chain identity anchor
  2. Purchase Intents (PINTs) — EIP-712 signed messages that authorise specific actions and scopes
  3. The Sumvin Identity Service (SIS) — exchanges signed PINTs for verifiable JWTs that third parties can independently validate

​
How It Works

A typical identity flow looks like this:
  1. The user (or their agent) signs a Purchase Intent — a structured EIP-712 message declaring what they want to do, which scopes they authorise, and how long the authorisation is valid
  2. Your app exchanges the signed PINT with the SIS token service, which validates the signature, checks KYC status, and returns a SIS-signed JWT
  3. The JWT travels with requests to third-party services, which verify it against the SIS public keys (JWKS) and optionally check revocation status

​
Key Concepts

ConceptDescription
SRISumvin Resource Identifier — a URI-style identifier for users and resources (sr:us:person:safe:0x...)
PINTPurchase Intent — an EIP-712 signed message authorising specific scopes and actions
SISSumvin Identity Service — the API that validates PINTs and issues JWTs
Safe WalletThe user’s on-chain identity anchor (Gnosis Safe multisig)
ScopesPermission grants included in a PINT (e.g., sr:us:pint:identity:proof_of_personhood)
Verification TierStandard (JWT only) or Enhanced (JWT + PINT signature) — determined by scopes requested

​
Who Uses What

You are…You need…
An app developer building on SumvinThe Platform API to create users and wallets, then this Identity tab to create PINTs and exchange them for JWTs
A merchant or service provider receiving Sumvin credentialsThe Verifier Guide to validate incoming JWTs and PINT signatures

​
Next Steps

  1. SRI format — the URI family that identifies users, resources, and scopes.
  2. EIP-712 and PINTs — the signed message spec you’ll mint against.
  3. Token exchange — trade a signed PINT for a SIS-issued JWT.
  4. Scopes reference — the capability envelope each PINT carries.