Compliance Receipt Verifier
Verify any X-Tinplate-Receipt token issued by ?receipt=true or X-Tinplate-Receipt-Request: true in constant time against our gateway signing keys or public JWKS (/.well-known/jwks.json).
Zero-Trust Offline Verification
How Cryptographic Attestations &
How Cryptographic Attestations & body_sha256 Binding Work
- Asymmetric Signing (
EdDSA/ES256): Tokens signed with the gateway Ed25519 key carry header{"alg":"EdDSA","typ":"AAR","kid":"edge-ed-2026-11"}and verify completely offline againstGET /.well-known/jwks.json(supporting zero-downtime key rotation across active & retiredkidentries). - Request-Body Cryptographic Binding: Every receipt commits
action_input.body_sha256over exact request bytes plusprev_hash(linked viaX-Tinplate-Prev-Receipt-Hash) without persisting prompts, PII, or responses on Tinplate servers. - Zero-Dependency SDK Helper (
@tinplate/sdkv1.1.6): Verify locally in Node 18+, Cloudflare Workers, Deno, Bun, or browsers using WebCryptocrypto.subtle:
import { TinplateClient } from "@tinplate/sdk";
const client = new TinplateClient({ apiKey: process.env.TINPLATE_API_KEY! });
const jwks = await client.getJwks(); // caches https://api.tinplate.dev/.well-known/jwks.json
const check = await client.verifyReceiptOffline(receiptToken, { jwks });
console.log(check.valid, check.alg, check.kid, check.payload);
See our Security & Trust Center or inspect Self-Service Portal for key-scoped compliance summaries.