Guides · Free check · $9 fix pack

Guides

AI built your Stripe checkout? Run this webhook checklist before the first real charge

You shipped a vibe-coded or AI-built Stripe app and you cannot read the webhook code with confidence. Before the first real card is charged, prove four things: forged events are rejected, the success page cannot unlock access, a live endpoint exists with the live secret, and fulfillment is safe to repeat.

Why this matters

Stripe: "Without verification, an attacker could send fake webhook events to your endpoint to trigger actions like fulfilling orders, granting account access, or modifying records" (Stripe docs: Receive Stripe events). And "You can't rely on triggering fulfillment only from your checkout landing page, because it's not guaranteed customers visit that page" (Stripe docs: Fulfill orders). The checks below take a few minutes and do not require editing code first.

1. Unsigned POST must get a 4xx, not a 200

From a terminal (replace the URL with yours):

curl -i -X POST \
  -H 'content-type: application/json' \
  -d '{}' \
  https://yourdomain.com/api/webhooks/stripe

Expect 400 (or another 4xx). A 200 means the handler accepted an event with no Stripe-Signature header, so anyone who learns the URL can unlock paid plans. Stripe says to verify with the raw body, the Stripe-Signature header, and the endpoint's whsec_ secret, and to reject failures (source). Full background: can someone fake a Stripe payment.

2. The success URL must not unlock access by itself

Open your success page in a private window, and try a made-up ?session_id=cs_test_fake. If a free account becomes paid, the landing page is doing the unlock. Stripe: webhooks are required for fulfillment; the landing page alone is not enough because customers are not guaranteed to visit it (source; Stripe docs: Customize redirect behavior). Fix notes: success page unlocks without payment.

3. Confirm a live-mode endpoint exists and is enabled

In Workbench → Webhooks (live mode, not test), you should see an HTTPS endpoint on your production URL with status enabled, subscribed at least to checkout.session.completed (and the async payment events if you accept bank debits). Stripe requires registered webhook endpoints to be publicly accessible HTTPS URLs (source). List them with the API if you prefer (Stripe API: List webhook endpoints). If deliveries show long stretches of Failed, recover them: failing silently and reconcile missed events.

4. Production uses the Dashboard live secret, not the CLI or test secret

Stripe: "The secret for a CLI-forwarded endpoint is different from the secret for a Dashboard-managed endpoint—don't mix them up" (Stripe docs: Manage webhook endpoints). And "if you use the same endpoint for both test and live API keys, the secret is different for each one" (source). The whsec_ printed by stripe listen only verifies CLI-forwarded events. Production needs the live endpoint's Reveal secret value, stored separately from test (Stripe docs: API keys). Details: test vs live webhook secret.

5. Fulfillment is run-once (and the paid flag is not client-writable)

Stripe's fulfill function "might be called multiple times, possibly concurrently, for the same Checkout Session", so it must only unlock once (source). Key it on the session ID with a unique constraint (duplicate events). If the app uses Supabase, also confirm a free user cannot UPDATE their own is_paid / plan column from the browser (users can set themselves to paid).

Optional hardening

Prompt for your AI builder

Audit this Stripe checkout app before the first live charge. 1) The webhook must verify Stripe-Signature with constructEvent (or the official helper) on the raw request body and the live Dashboard whsec_ secret; reject failures with 400. 2) Never grant access from the success page alone; call the same run-once fulfill(sessionId) the webhook uses, after retrieving the session and checking payment_status. 3) Confirm a live-mode webhook endpoint exists for the production URL; do not use the stripe listen secret or the test whsec_ in production. 4) Fulfillment must be idempotent on Checkout Session ID. 5) If Supabase: move is_paid/plan off any table users can UPDATE. 6) Show me curl to POST {} unsigned to the webhook and what status to expect. Do not weaken signature checks.

Re-test

  1. Unsigned curl → 4xx.
  2. Private-window success URL → no unlock.
  3. Sandbox Checkout with card 4242…4242, then confirm the account upgrades only after the verified webhook (close the tab before redirect once to prove it).
  4. Paste the live webhook URL into the free check below for a second opinion.
Check yours in 10 seconds (free).

Paste your webhook URL. WebhookProof sends 3 harmless test requests and tells you whether Stripe can reach it and whether it rejects unsigned events. If it finds a problem, the $9 fix pack gives you the exact copy-paste fix for your stack (refundable for 14 days).

Run the free check

FAQ

How do I check a Stripe webhook without reading the code?

POST an empty JSON body to the live webhook URL with no Stripe-Signature header. A 400 means unsigned events are rejected; a 200 means anyone can forge a payment-succeeded event. Also open the success page in a private window and confirm it does not unlock access by itself.

Can I use the stripe listen secret in production?

No. Stripe says the CLI-forwarded endpoint secret is different from the Dashboard-managed endpoint secret. Production must use the live endpoint's whsec_ from Workbench.

Is the success page enough to unlock a paid plan?

No. Stripe says you cannot rely on the checkout landing page for fulfillment because customers are not guaranteed to visit it. Unlock from a verified webhook (and optionally re-run the same fulfill function from the success page after retrieving the session).

Sources

More guides

Stripe webhook not working? Check these 7 things in order · A customer paid but didn't get access. What went wrong? · No signatures found matching the expected signature for payload · Stripe webhook failing with a 307 or 308 redirect

Last reviewed 2026-11-11. WebhookProof is an independent tool, not affiliated with Stripe, Inc.. Quotes are from the linked documentation.