How to Fix Stripe Webhooks Not Firing in Lovable Apps

What is actually happening

Lovable scaffolds a Stripe webhook handler that runs as a Supabase Edge Function. The handler verifies the request signature against a STRIPE_WEBHOOK_SECRET environment variable. When something breaks between Stripe and your app, the webhook is almost always the failure point because every other piece of the flow is synchronous and visible.

The fix, in order

Try these in sequence. Most apps are fixed by the first or second step.

1. 1

   Confirm the webhook signing secret is set in production

   In the Supabase dashboard, go to Edge Functions then your Stripe webhook function then Secrets. Make sure STRIPE_WEBHOOK_SECRET is set and matches the signing secret from your Stripe webhook endpoint (not the API key). The secret starts with whsec_. If it is missing or wrong, the handler returns 400 and Stripe stops retrying after 3 days.

2. 2

   Verify the webhook endpoint URL in Stripe matches your deploy

   In Stripe Dashboard go to Developers then Webhooks. The endpoint URL should be your production Supabase function URL, not localhost or a stale staging URL. Format: https://[your-project].supabase.co/functions/v1/stripe-webhook. If the URL is wrong, no events ever reach your app.

3. 3

   Check that the right events are subscribed

   On the same Stripe webhook detail page, click 'Listening to'. Make sure you are subscribed to the events your app actually needs: checkout.session.completed for one-time payments, customer.subscription.created and customer.subscription.updated and customer.subscription.deleted for subscriptions, invoice.payment_succeeded and invoice.payment_failed for billing. If your app handles an event that is not subscribed, it will never fire.

4. 4

   Look at the recent deliveries log in Stripe

   Stripe shows the last 30 days of webhook deliveries with HTTP response codes. If you see 200s, the webhook is firing fine and your bug is downstream. If you see 4xxs, the problem is signing or endpoint. If you see 5xxs, your function is crashing. Click into a failed delivery to see the actual response body, which usually has the error.

5. 5

   Test with the Stripe CLI before going live

   Install the Stripe CLI and run: stripe listen --forward-to https://[your-project].supabase.co/functions/v1/stripe-webhook --events checkout.session.completed. This sends a test event and shows you the exact response from your handler. Faster than waiting for real events.

Related fixes

• How to Fix Lovable Supabase Connection Timeout Errors

  Lovable apps timing out when connecting to Supabase. The actual causes, the fixes that work, and when to stop debugging and switch.

• How to Fix Lovable Deployment Failures and Build Errors

  Your Lovable app builds fine in the editor but fails to deploy. The four most common causes and exactly how to fix each one.

• How to Fix Lovable Authentication Breaking in Production

  Auth works locally in your Lovable app but breaks the moment users hit the deployed site. Why this happens and how to fix it.

• How to Fix an AI-Built App Where the Database Keeps Resetting

  Your data disappears every time the app redeploys or the dev environment restarts. The actual cause and the fix.