---
title: "Comment by Paul Hartness on \"Why isn’t my Stripe webhook updating Supabase?\" | Hashnode"
description: "Good list. The 30 October grants change is going to catch a lot of people with a 42501 they can't explain. One I'd add next to the invoice.paid point is the fai"
url: "https://hashnode.com/posts/why-isn-t-my-stripe-webhook-updating-supabase/6ae9d43fde20b4f15aa70ce8/comment/6aeaf8440eabac1451004c02"
---

[Discussion](https://hashnode.com/posts/why-isn-t-my-stripe-webhook-updating-supabase/6ae9d43fde20b4f15aa70ce8)

Comment [Why isn’t my Stripe webhook updating Supabase?](https://hashnode.com/posts/why-isn-t-my-stripe-webhook-updating-supabase/6ae9d43fde20b4f15aa70ce8)

[Paul Hartness](https://hashnode.com/@retryfix)

[5d ago](https://hashnode.com/posts/why-isn-t-my-stripe-webhook-updating-supabase/6ae9d43fde20b4f15aa70ce8/comment/6aeaf8440eabac1451004c02)

Good list. The 30 October grants change is going to catch a lot of people with a 42501 they can't explain. One I'd add next to the invoice.paid point is the failure side of a renewal. If the handler only listens for paid events, a failed renewal never reaches Supabase, so the user stays active in your table while Stripe has the subscription past\_due. Handling customer.subscription.updated and reading the current status covers both directions.