I keep seeing the same handful of Stripe integration bugs show up in code review: webhook signatures checked against the wrong header casing, no timestamp-tolerance handling so replayed test events get accepted, fulfillment wired to the redirect instead of the webhook, raw body getting parsed by a body-parser before Stripe's SDK sees it.
Instead of writing yet another "top 10 Stripe mistakes" listicle, I put the two resources I actually use into one page:
- A free-to-read production checklist (paid CSV export, $9) covering webhook verification, idempotency, the Charges vs PaymentIntents split, and Checkout session edge cases.
- An auditor kit ($29) — the same checks as an executable rules report you run against your own repo instead of eyeballing a list.
If you've hit a Stripe bug that isn't on the list, I'd genuinely like to hear it — replying here or opening an issue against your own repo and comparing notes is more useful to me than another pageview.
Top comments (0)