#kevalmandalik

1 messages · Page 1 of 1 (latest)

wraith creekBOT
#

Hello kevalmandalik, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
https://discord.com/channels/841573134531821608/1164471108658020384, 0 days ago, 9 messages

dapper cedar
#

Hi, my colleague had to step away. Could you please provide some context?

#

Could you please share a complete code snippet?

neon snow
#

yeah sure Heres code snippet of frontend and backend

#

due to this entire app is stopped working all api just return 400 code and not any error message

#

@dapper cedar

dapper cedar
#

Oh, are you using Stripe Apps?

#

What console.log() do you get?

neon snow
#

in console.log() i am getting
** {}**

quasi pawn
#

Hi! I'm taking over this thread.

#

What's the exact error you see in your backend logs?

#

And what do you see when you console.log the payload, signature, and appSecret?

#

Is your goal to listen to webhook events on your Stripe account?

#

Because your appSecret seems wrong, it should start with whsec_xxx

neon snow
#

Hey!!

#

As i told ealier I am not getting any error message in console.log which is added in chatch block

neon snow
#

@quasi pawn

quasi pawn
#

It depends. How are you testing this? With a real webhook endpoint set in your Stripe dashboard, or with the Stripe CLI?

neon snow
#

i am tesing with real endpoint

quasi pawn
#

Then check that endpoint in your Stripe dashboard, and there you can find the whsec_xxx.

neon snow
#

can you eloborate where exactly i can get this in stripe dashboard

#

@quasi pawn

quasi pawn
#

Open the webhook endpoint in your dashboard, and click on "reveal" at the top of the page