v0 Stripe integration not working — add payments to your v0 app

Quick fix for v0 Stripe integration not working —

import Stripe from "stripe";

const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!);

export async function POST(req: Request) {
  const session = await stripe.checkout.sessions.create({
    mode: "payment",
    line_items: [
      { price: "price_xxx", quantity: 1 },
    ],
    success_url: `${req.headers.get("origin")}/success`,
    cancel_url: `${req.headers.get("origin")}/cancel`,
  });
  return Response.json({ url: session.url });
}

Deeper fixes when the quick fix fails

1. 02

   Step 2 — Create the webhook handler

   Create app/api/stripe/webhook/route.ts. This route must read the raw body (not JSON) for Stripe to verify the signature:

   import Stripe from "stripe";
   
   const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!);
   
   export async function POST(req: Request) {
     const sig = req.headers.get("stripe-signature")!;
     const raw = await req.text();
     const event = stripe.webhooks.constructEvent(
       raw,
       sig,
       process.env.STRIPE_WEBHOOK_SECRET!
     );
   
     // Handle the four events that actually matter
     switch (event.type) {
       case "checkout.session.completed":
       case "invoice.paid":
       case "customer.subscription.updated":
       case "customer.subscription.deleted":
         // Update subscription state in your DB
         break;
     }
   
     return Response.json({ received: true });
   }

   In the App Router, route handlers already receive the raw body via req.text()— no special config needed.

2. 03

   Step 3 — Add Stripe keys to environment

   Add to .env.local:

   STRIPE_SECRET_KEY=sk_test_...
   STRIPE_WEBHOOK_SECRET=whsec_...
   NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_test_...

   For local webhook testing, install the Stripe CLI: npm install -g stripe, then run stripe listen --forward-to localhost:3000/api/stripe/webhook. Copy the webhook secret printed by the CLI into your env file.

3. 04

   Step 4 — Store subscription state

   When checkout.session.completed fires, write to your database: user ID, Stripe customer ID, subscription status, plan tier. Use this row to gate features.

   INSERT INTO subscriptions
     (user_id, stripe_customer_id, status, plan)
   VALUES ($1, $2, $3, $4)
   ON CONFLICT (user_id) DO UPDATE
     SET status = EXCLUDED.status,
         plan   = EXCLUDED.plan;

   On every protected route, check this row before granting access. Without it, a cancellation event never revokes access.

Why AI-built apps hit v0 Stripe integration not working —

Diagnose v0 Stripe integration not working — by failure mode

Follow these four steps in order — each one builds on the previous.

Related errors we fix

• Stripe webhook not firing (tool-agnostic deep dive)
  read the fix →
• Webhook signature verification failed
  read the fix →
• Stripe checkout session expired
  read the fix →
• Stripe test mode stuck in production
  read the fix →

Still stuck with v0 Stripe integration not working —?

v0 Stripe integration not working — questions

v0 Stripe integration not working — experts

If this problem keeps coming back, you probably need ongoing expertise in the underlying stack.

• Stripe specialist →
  Checkout, webhooks, subscription state, and feature gating wired into v0 / Next.js apps.
• Supabase expert →
  Subscription tables, RLS, and typed queries to back your Stripe integration.