Verify a completed purchase receipt
Enter the receipt ID returned by a successful purchase. The server recomputes hashes from durable database state and returns structured pass/fail checks.
Which API this verification uses
This page calls GET https://growthbase-production.up.railway.app/receipts/<receiptId>/verify-bundle (durable state on the API host only — no local database on this page).
On Vercel, https://growthbase-production.up.railway.app defaults to the public live API (https://growthbase-production.up.railway.app) unless you set NEXT_PUBLIC_RECEIPT_VERIFY_API_BASE_URL (or legacy NEXT_PUBLIC_RECEIPT_VERIFY_API_URL).
A receipt exists on one API database. To verify a receipt issued against a different base URL (for example a local dev API), point the verify base at that host using the env vars above.
What this page proves
/verify is for receipt-linked verification after a successful purchase: request, snapshot, artifact, proof, and growth linkage. If you need the canonical historical payment proof with a transaction hash but no successful live receipt, use /evidence.