#fuzzbear_dev
cinder spade
buoyant crown
hey there, happy to help with this 🙂
gaunt bluff
great
buoyant crown
In what scenario are you experiencing this? Delivery directly from stripe, or are you using the CLI to forward in test mode?
gaunt bluff
In what scenario are you experiencing this? Delivery directly from stripe, or ar...
delivery from stripe
live mode
buoyant crown
And was this working for you previously? Or is this newly deployed?
gaunt bluff
worked before
well,
this bit is new develop tho
as its a new checkout session
but the webhooks.js always worked
no issue
buoyant crown
And you've already been checking signatures in live mode?
gaunt bluff
idk what they rlly are
buoyant crown
What do you mean?
gaunt bluff
what do i need to check about them
buoyant crown
They are for verifying delivery from Stripe. But, this leads me to wonder whether you;d been checking this before, or did you add this when you added handling for checkout events?
It sounds like you were not using them before
buoyant crown
Can you share an example event ID from that list, or the webhook endpoint id? evt_123 or we_1234 say
gaunt bluff
evt_1NugDDL6k3oFrmnnJIAGy7Lb
buoyant crown
Ok, it looks like you don't use webhooks for anything else, i see no other registered event types on your endpoints
buoyant crown
worked before
So I am not sure what you were referring to here
gaunt bluff
Ok, it looks like you don't use webhooks for anything else, i see no other regis...
ah then just that
buoyant crown
I would suggest logging all the parameters to constructEvent to ensure they contain the values you expect
buoyant crown
Assuming the signature value is populated and the webhookSecret matches the value from your dashboard, then the most common issue is some part of your request handling stack mutating the request body
gaunt bluff
kk