v0 integration

Stripe Webhook Signature Verification Failing

Your v0-generated Next.js application receives Stripe webhook events but fails to verify their signatures, returning 400 errors or throwing 'Webhook signature verification failed' exceptions. Payments are processed by Stripe but your application never confirms them, leaving orders in a pending state and customers confused.

Stripe signs every webhook event with a signature derived from the raw request body and your webhook signing secret. If the body is modified in any way before verification (such as being parsed as JSON), or if the signing secret is incorrect, verification fails. This is a critical security feature that prevents attackers from sending fake webhook events to your application.

This is one of the most common Stripe integration issues because Next.js API routes automatically parse the request body as JSON, which modifies the raw body that Stripe's verification expects.

Error Messages You Might See

Stripe webhook signature verification failed No signatures found matching the expected signature for payload Webhook Error: Unexpected token in JSON at position 0 stripe.webhooks.constructEvent is not a function 400 Bad Request on /api/webhook
Stripe webhook signature verification failedNo signatures found matching the expected signature for payloadWebhook Error: Unexpected token in JSON at position 0stripe.webhooks.constructEvent is not a function400 Bad Request on /api/webhook

Common Causes

  • Body pre-parsed by Next.js — Next.js API routes parse JSON body automatically, but Stripe verification requires the raw body bytes
  • Wrong webhook secret — using the API secret key (sk_...) instead of the webhook signing secret (whsec_...)
  • Local vs production secret mismatch — Stripe CLI uses a different signing secret than the dashboard webhook endpoint
  • App Router body handling — Next.js App Router route handlers consume the body stream, making it unavailable for Stripe verification
  • Middleware modifying request — authentication or logging middleware reading the request body before the webhook handler

How to Fix It

  1. Disable body parsing — for Pages Router: export const config = { api: { bodyParser: false } }
  2. Read raw body in App Router — use const body = await request.text() to get the raw body string before any JSON parsing
  3. Use correct signing secret — get the webhook signing secret (whsec_...) from Stripe Dashboard > Webhooks > your endpoint > Signing secret
  4. Verify with Stripe SDK — use stripe.webhooks.constructEvent(body, sig, webhookSecret) with the raw body string
  5. Test with Stripe CLI — run stripe listen --forward-to localhost:3000/api/webhook and use the provided signing secret for local testing
  6. Return 200 quickly — process webhook asynchronously and return 200 immediately to avoid Stripe retry storms

Real developers can help you.

Caio Rodrigues Caio Rodrigues I'm a full-stack developer focused on building practical and scalable web applications. My main experience is with **React, TypeScript, and modern frontend architectures**, where I prioritize clean code, component reusability, and maintainable project structures. I have strong experience working with **dynamic forms, state management (Redux / React Hook Form), and complex data-driven interfaces**. I enjoy solving real-world problems by turning ideas into reliable software that companies can actually use in their daily operations. Beyond coding, I care about **software quality and architecture**, following best practices for componentization, code organization, and performance optimization. I'm also comfortable working across the stack when needed, integrating APIs, handling business logic, and helping transform prototypes into production-ready systems. My goal is always to deliver solutions that are **simple, efficient, and genuinely useful for the people using them.** Nam Tran Nam Tran 10 years as fullstack developer Jared Hasson Jared Hasson Full time lead founding dev at a cyber security saas startup, with 10 yoe and a bachelor's in CS. Building & debugging software products is what I've spent my time on for forever Anthony Akpan Anthony Akpan Developer with 8 years of experience building softwares fro startups Sage Fulcher Sage Fulcher Hey I'm Sage! Im a Boston area software engineer who grew up in South Florida. Ive worked at a ton of cool places like a telehealth kidney care startup that took part in a billion dollar merger (Cricket health/Interwell health), a boutique design agency where I got to work on a ton of exciting startups including a photography education app, a collegiate Esports league and more (Philosophie), a data analytics as a service startup in Cambridge (MA) as well as at Phillips and MIT Lincoln Lab where I designed and developed novel network security visualizations and analytics. I've been writing code and furiously devoted to using computers to make people’s lives easier for about 17 years. My degree is in making computers make pretty lights and sounds. Outside of work I love hip hop, the Celtics, professional wrestling, magic the gathering, photography, drumming, and guitars (both making and playing them) Simon A. Simon A. I'm a backend developer building APIs, emulators, and interactive game systems. Professionally, I've developed Java/Spring reporting solutions, managed relational and NoSQL databases, and implemented CI/CD workflows. Victor Denisov Victor Denisov Developer prajwalfullstack prajwalfullstack Hi Im a full stack developer, a vibe coded MVP to Market ready product, I'm here to help Antriksh Narang Antriksh Narang 5 years+ Experienced Dev (Specially in Web Development), can help in python, javascript, react, next.js and full stack web dev technologies. Milan Surelia Milan Surelia Milan Surelia is a Mobile App Developer with 5+ years of experience crafting scalable, cross-platform apps at 7Span and Meticha. At 7Span, he engineers feature-rich Flutter apps with smooth performance and modern UI. As the Co-Founder of Meticha, he builds open-source tools and developer-focused products that solve real-world problems. Expertise: 💡 Developing cross-platform apps using Flutter, Dart, and Jetpack Compose for Android, iOS, and Web. 🖋️ Sharing insights through technical writing, blogging, and open-source contributions. 🤝 Collaborating closely with designers, PMs, and developers to build seamless mobile experiences. Notable Achievements: 🎯 Revamped the Vepaar app into Vepaar Store & CRM with a 2x performance boost and smoother UX. 🚀 Launched Compose101 — a Jetpack Compose starter kit to speed up Android development. 🌟 Open source contributions on Github & StackOverflow for Flutter & Dart 🎖️ Worked on improving app performance and user experience with smart solutions. Milan is always happy to connect, work on new ideas, and explore the latest in technology.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

Why does webhook verification fail even with the correct secret?

Most likely the request body was parsed as JSON before verification. Stripe needs the raw body bytes. Disable body parsing with config = { api: { bodyParser: false } }.

Where do I find my webhook signing secret?

Go to Stripe Dashboard > Developers > Webhooks > click your endpoint > Signing secret. It starts with whsec_. Do not use your API key (sk_...).

How do I test webhooks locally?

Install Stripe CLI, run 'stripe listen --forward-to localhost:3000/api/webhook', and use the signing secret it outputs (whsec_...) for local testing.

Related v0 Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help