A customer completes checkout. Stripe fires a webhook. Your server receives it, verifies the signature, provisions access, and returns 200. That is the happy path. The failure path is silent: the webhook arrives, signature verification fails, your handler returns 400, Stripe retries for 72 hours, the customer opens a support ticket, and you discover the signing secret was rotated three weeks ago.
Why signature verification is non-negotiable
Without signature verification, any POST request to your webhook URL can trigger provisioning. An attacker who discovers your endpoint can forge events, grant themselves premium access, or trigger refund logic. The signing secret proves the event came from Stripe, not from an attacker or a misconfigured test tool.
Common webhook failure patterns
The most frequent failures are: wrong signing secret (test vs live), raw body consumed before verification (middleware parsing JSON too early), endpoint not publicly reachable (firewall, preview URL, localhost tunnel expired), and handler returning 500 due to unhandled database errors. Each of these causes Stripe to retry, which delays provisioning and creates duplicate processing risk.
Preserve the raw body
Stripe signature verification requires the raw request body as a string or buffer. If your framework parses the body into JSON before your handler runs, the signature will never match. In Next.js App Router, export a config that disables body parsing for the webhook route. In Express, use express.raw() on the specific endpoint.
Match the signing secret to the environment
Stripe provides separate signing secrets for test mode and live mode webhooks. A common launch failure is deploying with the test-mode signing secret still in production environment variables. The webhook arrives, verification fails, and the event is silently dropped. PreFlight checks whether your webhook endpoint accepts events with the expected signing behavior before customers start paying.
Handle duplicate events idempotently
Stripe retries on timeout and network errors. Your handler will receive the same event multiple times. Use the event ID as an idempotency key — check if you have already processed it before writing to the database. Without this, customers can receive duplicate credits, subscriptions, or provisioning actions.
Verify the side effect, not just the 200
Returning 200 to Stripe means "I received this." It does not mean the side effect succeeded. If your handler returns 200 before the database write completes, and the write fails, you have lost the event. PreFlight's shadow checkout traces the full path: session created, webhook delivered, side effect written to the database, and verified by reading it back.
Verify continuously, not just at launch
Webhook endpoints break after launch too — when you deploy a new API version, when middleware changes, when a CDN starts buffering POST bodies, or when a signing secret is rotated without updating the environment variable. PreFlight's Sentinel runs these checks continuously so you catch webhook failures before customers report them.
Expanded field note
A webhook is a security and fulfillment boundary: the practical answer
signature errors, raw-body parsing, and duplicate events can grant access incorrectly or deny it after payment. This guide is for developers implementing payment events. Start by naming the failure you want to prevent and the customer or operator who would notice it first.
The useful scope is the full event path: delivery, signature, idempotency, handler, and entitlement. That keeps the work concrete: you can choose a URL, provider, route, release, or data operation, observe it, and decide what to do when the observation does not match the expected contract.
What good looks like
the event identifier, verification result, response status, write, and reconciliation state. A result is stronger when it preserves the input, environment, timestamp, expected behavior, observed behavior, and the next action. This lets a different person reproduce the finding without asking the original operator to reconstruct the entire context from memory.
a 200 response is not the same thing as a correct fulfillment result. Keep the scope visible when sharing the result. A passing outside-in check can prove a reachable behavior at a point in time; it cannot silently become a guarantee about private code, every authenticated role, or every provider failure mode.
Frame the decision before you change anything
developers implementing payment events usually do not need another dashboard full of disconnected warnings. They need a defensible answer to a narrower question: is the behavior that matters to the customer working in the environment that is about to change? Start there. If the answer is unclear, make the ambiguity part of the work instead of translating it into a green score.
The first useful boundary is the full event path: delivery, signature, idempotency, handler, and entitlement. Write it down in the same language the team will use during the fix. Name the route, provider, release, role, data object, or browser action involved. Then write the expected behavior as a sentence that could be checked by another person. This turns a broad topic into a small contract and makes it easier to tell whether a failure is reproducible, transient, out of scope, or genuinely fixed.
A good scope also includes what the check does not attempt. Public observation is different from authenticated authorization testing. Provider reachability is different from a complete fulfillment path. A page that renders in a browser is not necessarily a page a crawler can index. Stating the limit early protects the reader from overconfidence and tells the operator when to add a deeper review.
Questions the result should answer
- What was tested? Identify the canonical URL, route, provider, account role, release, or customer action rather than describing the scope as “the site.”
- What should have happened? State the expected response, permission, side effect, delivery event, page directive, or recovery signal in plain language.
- What actually happened? Keep the observed status, safe error, response detail, timing context, or missing side effect without pasting credentials or customer data into the record.
- Why does it matter? Connect the observation to a customer, crawler, revenue, security, availability, or release decision so severity is not just a color.
- What happens next? Name the smallest reversible fix, the owner, the rerun, and the condition that will close the issue.
These questions are deliberately boring. Boring evidence is easier to compare, easier to hand off, and easier to defend later. It also gives an answer engine or a future teammate enough context to summarize the result without inventing a claim that the original check never made.
A sequence that holds up under pressure
- Keep the raw request body until signature verification completes.
- Use the signing secret for the exact environment and endpoint.
- Make processing idempotent by event identifier.
- Return bounded errors and let the provider retry the right failures.
- Verify the database side effect and customer access after the event.
The important nuance is this: a 200 response is not the same thing as a correct fulfillment result. That distinction matters because fast remediation can create a second problem: a broad header change can break a payment script, a credential rotation can break a cron worker, and a restrictive policy can make a valid customer path look like an outage.
Evidence to keep with the fix
| Record | Why it matters |
|---|---|
| Scope | The URL, role, provider, release, and limitation prevent a result from being reused outside the question it actually answered. |
| Before | The original failing observation, environment, and customer impact make the fix auditable. |
| Change | The code, configuration, provider setting, migration, or credential action that should alter the result. |
| After | A rerun against the same scope proves whether the intended behavior recovered. |
| Owner | A named person or team, an expected next action, and a review date keep the result from becoming an orphaned warning. |
| Follow-up | An owner, cadence, or release rule keeps the same class of failure from returning silently. |
Failure modes worth checking twice
- JSON parsing runs before signature verification.
- Test and live webhook secrets are swapped.
- Retries create duplicate records or duplicate entitlements.
- A handler returns success while a database write has failed.
When one of these appears, avoid making several unrelated changes at once. Preserve the failing evidence, isolate the smallest boundary that can explain it, make one reversible correction, and rerun. That rhythm is slower than guessing for the first five minutes and faster than untangling a release that changed three providers at once.
Know when the first layer is not enough
Automation is valuable because it is repeatable, but repeatability is not the same as depth. If the question involves complex authorization, tenant isolation, injection, business logic, a high-value asset, or an adversarial threat model, use the automated result as a map for a deeper review. Give the reviewer the scope, failed observation, relevant release context, and the boundary you want tested. Do not present a public scan as a certification or a substitute for professional security work.
The same rule applies to operations. A successful provider probe may prove that a credential can reach an API, but it may not prove that a webhook creates the correct entitlement. A healthy uptime response may prove reachability, but it may not prove that a signed-in customer can complete the task. Add the assertion or browser journey that matches the real risk, and keep the cheap signal for early warning.
Questions people ask after reading this
What is the fastest useful first step?
Choose one representative scope and write the expected result before running the tool. For this topic, that means the full event path: delivery, signature, idempotency, handler, and entitlement. A small, explicit baseline is more useful than a large scan whose findings have no owner or decision attached.
What should I do when the result is green?
Keep the scope, timestamp, and limitation, then decide whether the result belongs in a release gate, monitor, report, or follow-up review. Green means the observed contract passed. It does not turn untested behavior into evidence.
What should I do when the result is red?
Read the evidence before changing configuration. Confirm the environment, reproduce the smallest failing behavior, assign the next action, and rerun after the fix. If the issue requires credentials, source access, or adversarial judgment, escalate it rather than hiding the gap behind a retry.
After the fix ships
Run the same check on the canonical production surface, not only on a local or preview environment. If the issue involved a provider, wait for the real callback or scheduled sample. If it involved search, confirm the HTML, canonical, robots, sitemap, and internal links agree. If it involved payments or access, verify the side effect a customer receives rather than stopping at a browser redirect.
PreFlight is designed for this last step: keep the original observation, connect the relevant provider or journey, attach the release context, and let the next run show whether the system stayed healthy. The goal is not a bigger report. It is a shorter path from signal to a verified decision.