Skip to main content
Verified checkout is a merchant or service pattern where your storefront accepts a Sumvin-issued credential at the request boundary. The credential proves who the buyer is — and, for spend flows, that they cryptographically authorised this specific purchase.

​
What the flow looks like

  1. A buyer (or their agent) arrives at your checkout endpoint with a JWT in the x-sumvin-pint-token header.
  2. You verify the JWT signature against the SIS and check the aud, exp, and scope claims.
  3. For enhanced-tier actions (spend), you also verify the EIP-712 PINT signature using the X-Pint-Signature and X-Pint-Payload headers.
  4. You optionally check revocation via the SIS status endpoint.
  5. You fulfil the order.

​
Which primitives back it

  • PINT JWT — the SIS-issued token that carries the buyer’s identity, scopes, and purchase context. See PINT and Verify a JWT.
  • PINT signature — the underlying EIP-712 signature enhanced-tier flows require. See Verify a PINT signature.
  • Scopes determine which tier applies. See scopes.
  • Revocation lets you check the status endpoint for tokens that have been invalidated. See revocation.

​
Standard vs enhanced

Identity-only flows (e.g. age gates, proof of personhood, KYC attestation) are Standard tier — JWT verification alone is sufficient. Spend authorisation requires Enhanced tier — JWT plus EIP-712 PINT signature verification. The full decision matrix lives on the verification tiers page.

​
Where to start

ConcernWhere to goWhen
OrientationVerifier overviewFirst — what you receive and what to verify
Tier choiceVerification tiersBefore writing any verification code
Standard flowVerify a standard PINTJWT-only — identity, age, KYC attestation
Enhanced flowVerify an enhanced PINTJWT plus EIP-712 signature — spend authorisation