#oops365
1 messages · Page 1 of 1 (latest)
If you print all the headers, do you see Stripe-Signature at all?
I have the logs printing what I believe is the correct header, judging from the docs:
t=1701247401,v1=4509...4ff,v0=e40...a92
(printout of the signatureHeader variable from the code above)
actual log looks like this
2023-11-29 02:43:21.412 CST
Stripe Error: The expected signature was not found in the Stripe-Signature header. Make sure you're using the correct webhook secret (whsec_) and confirm the incoming request came from Stripe.
2023-11-29 02:43:21.412 CST
whsec_dm8...Yx
2023-11-29 02:43:21.412 CST
2023-11-29 02:43:21.412 CST
SigSecret: t=1701247401,v1=4509..84ff,v0=e40b..7a92 End Sig
Ellipses added by me
Stripe.net nuget version 43.4.0 btw, if that helps
Hi! I'm taking over this thread.
First, can you triple check that you are using the correct whsec_xxx?
Also, can you share your account ID (acct_xxx)? It's at the top of this page: https://dashboard.stripe.com/settings/account
You cna do this here, however if you prefere a private conversation you should directly talk to Stripe support: https://support.stripe.com/contact
Ah, if it's not a security issue here is fine
acct_1LuRtRLFVWaHr9FE
And yeah I have the right secret printing out
It's quite a bit shorter than the CLI secret I noticed
but the printout matches the text when I click Reveal under Signing secret
Are you using the CLI for testing? Then are you using the whsec_xxx that is printed in the CLI (and not the one in your dashboard)?
We'd previously used the CLI for testing, but that's a different secret
the dashboard secret, which we're using, and which shows up on the logs is ~38chars long, while the CLI secret was ~70 chars long, if that helps
yes, all of that sounds correct.
can you try using the code that's on this page, and see if you have the same issue? https://stripe.com/docs/webhooks/quickstart