Your Stripe webhook endpoint was failing: how to find and recover the events you missed
November 13, 2026
A deploy broke the route, a secret was rotated, a firewall started blocking Stripe, or the handler threw on every request for two days. Stripe kept trying, then stopped. Everything that happened in between never reached your app, and nothing in your app will tell you.
This is the situation behind most silent billing drift: not a clever bug, just a gap in time during which your database stopped hearing about Stripe. The good news is that the events are still on Stripe’s side for a while, so the gap can usually be closed.
What Stripe does when your endpoint fails
- Any non-2xx response, or a timeout, counts as a failed delivery.
- In live mode Stripe retries with exponential backoff for up to about three days. In test mode the retry window is much shorter. After that, the event is not delivered again automatically.
- If an endpoint keeps failing for a long time, Stripe emails the account and can disable the endpoint. Check what your account’s notification and endpoint status show instead of assuming it is still on.
Exact numbers change, so verify them against the Stripe documentation for your account. The important point does not change: there is a finite window, and an outage longer than it leaves permanent holes.
Step 1: find out how big the gap is
In the Dashboard open Developers → Webhooks, pick the endpoint and look at the delivery attempts and their response codes. A run of 4xx or 5xx tells you when it started failing and why. Note the first failure and the moment it was fixed. Everything between those two timestamps is suspect.
Step 2: pull the events from the Events API
Stripe keeps events available through the API for a limited period (around 30 days), so you can list them and run each one through your normal handler:
// List what Stripe sent in a time window, so you can replay it
import Stripe from 'stripe'
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!)
const since = Math.floor(new Date('2026-11-01').getTime() / 1000)
for await (const event of stripe.events.list({
created: { gte: since },
types: [
'checkout.session.completed',
'invoice.paid',
'invoice.payment_failed',
'customer.subscription.updated',
'customer.subscription.deleted',
],
limit: 100,
})) {
await handleEvent(event) // the SAME function your webhook route calls
}Two rules make this safe. Call the same handler your webhook route uses, so replayed events behave exactly like live ones. And keep the idempotency guard from the duplicate events guide in place, so an event you did already process is skipped instead of applied twice. If your handler re-fetches the object before writing, as described in handling out-of-order events, replaying old events is harmless.
Step 3: or resend them one by one
For a handful of events, the Dashboard lets you resend a specific event to an endpoint, and the CLI does the same:
# Resend one event to one endpoint with the Stripe CLI
stripe events resend evt_1Abc... --webhook-endpoint=we_1Xyz...Step 4: do not trust, verify
After replaying, compare reality against your database. A replay can fail on individual events, and events older than the retention window are gone for good. Run the reconciliation script and look for three lists: access without payment, payment without access, and paying customers your database has never heard of. Anything left over has to be fixed by hand, from the current state in Stripe.
Why the endpoint failed in the first place
The most common causes are covered in signature verification failed and, in the opposite case where Stripe sees a 200 but nothing is saved, your Stripe webhook returns 200, but it didn’t work.
Let a machine do the comparing
Venwai compares Stripe with what your app grants access to every day, using a read-only Stripe key, and alerts you in Slack, Discord, Telegram, or email when they stop agreeing, including after a silent webhook outage.
Free while it’s in beta, no card required: venwai.com.
Venwai compares Stripe with who your app actually lets in, once a day, using a read-only key. It alerts you the moment they disagree. Free while in beta, no card required.
Check my Stripe for free