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

# Verified checkout

> Reference application for merchants accepting Sumvin-verified purchase intents at checkout.

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 <Tooltip headline="PINT" tip="Purchase Intent — an EIP-712 signed message authorising specific scopes and actions." cta="Glossary →" href="/glossary">PINT</Tooltip> JWT in the `x-sumvin-pint-token` header.
2. You verify the JWT signature against the SIS <Tooltip headline="JWKS" tip="JSON Web Key Set — the public-key document used to validate PINT JWTs." cta="Glossary →" href="/glossary">JWKS</Tooltip> 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](/identity/pint) and [Verify a JWT](/merchant/verify-jwt).
* **PINT signature** — the underlying EIP-712 signature enhanced-tier flows require. See [Verify a PINT signature](/merchant/verify-pint-signature).
* **Scopes** determine which tier applies. See [scopes](/identity/scopes).
* **Revocation** lets you check the status endpoint for tokens that have been invalidated. See [revocation](/merchant/revocation).

## Standard vs enhanced

<Info>
  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](/merchant/verification-tiers) page.
</Info>

## Where to start

| Concern       | Where to go                                                           | When                                             |
| ------------- | --------------------------------------------------------------------- | ------------------------------------------------ |
| Orientation   | [Verifier overview](/merchant/overview)                               | First — what you receive and what to verify      |
| Tier choice   | [Verification tiers](/merchant/verification-tiers)                    | Before writing any verification code             |
| Standard flow | [Verify a standard PINT](/merchant/quickstarts/verify-standard-pint)  | JWT-only — identity, age, KYC attestation        |
| Enhanced flow | [Verify an enhanced PINT](/merchant/quickstarts/verify-enhanced-pint) | JWT plus EIP-712 signature — spend authorisation |

## Related

* [PINT header reference](/merchant/headers)
* [Accept a PINT at checkout](/merchant/quickstarts/accept-pint-checkout)
* [Payment request links](/products/payment-links/payment-request-links) — user-originated, identity-anchored checkout shape
* [SIS error codes](/merchant/errors)