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

# I'm a merchant or verifier

> Routing page for merchants and service providers accepting Sumvin credentials.

You're receiving Sumvin credentials at your request boundary — a <Tooltip headline="PINT" tip="Purchase Intent — an EIP-712 signed message authorising specific scopes and actions." cta="Glossary →" href="/glossary">PINT</Tooltip> JWT, sometimes with an accompanying EIP-712 signature — and you need to verify them. The **[Verifier Guide](/merchant/overview)** is your primary surface.

## Which tier applies to you?

Two tiers cover every verification case:

* **Standard tier** — JWT verification alone. Use this for identity-only flows: age gates, proof of personhood, KYC attestation.
* **Enhanced tier** — JWT plus EIP-712 PINT signature verification. Use this for spend authorisation and any flow carrying `sr:us:pint:spend:execute`.

The [verification tiers](/merchant/verification-tiers) page is the authoritative decision doc — read it before writing any verification code.

## Start here

Read in this order:

1. **[Verifier overview](/merchant/overview)** — what you receive and what to verify.
2. The quickstart that matches your tier:
   * [Verify a standard PINT](/merchant/quickstarts/verify-standard-pint)
   * [Verify an enhanced PINT](/merchant/quickstarts/verify-enhanced-pint)
3. If you're accepting PINTs at a checkout endpoint specifically, also run [Accept a PINT at checkout](/merchant/quickstarts/accept-pint-checkout).

## Reference material you'll come back to

* [Verify a JWT](/merchant/verify-jwt) — step-by-step JWT validation.
* [Verify a PINT signature](/merchant/verify-pint-signature) — EIP-712 signature verification for enhanced tier.
* [JWKS endpoint](/merchant/jwks) — public key set for JWT verification.
* [Revocation](/merchant/revocation) — checking token status against SIS.
* [Error reference](/merchant/errors) — SIS error codes and handling.
* [Scopes reference](/identity/scopes) — how scopes map to tiers.

## What to skip for now

* The **[Platform API](/introduction)** is for partners creating users and wallets, not for verifiers. You do not need a Platform API account to verify JWTs.
* The **JWKS endpoint is public** — you do not need a SIS API key to verify signatures. An API key is only needed if you intend to call the revocation endpoint.

## Next up

<ol className="counter-style">
  <li>**[Verifier overview](/merchant/overview)** — what you receive and what to verify.</li>
  <li>**[Verification tiers](/merchant/verification-tiers)** — pick the right tier for your endpoint.</li>
  <li>**[Verify a standard PINT](/merchant/quickstarts/verify-standard-pint)** — JWT-only verification quickstart.</li>
  <li>**[JWKS endpoint](/merchant/jwks)** — where to fetch SIS public keys.</li>
</ol>

## Related

* [Platform map](/overview/platform-map)
* [Verified checkout use case](/overview/use-cases/verified-checkout)
* [Payment request links](/products/payment-links/payment-request-links) — PINT-backed checkout shape you may receive at settlement