#surbhi-cli-dotnet
1 messages · Page 1 of 1 (latest)
what's the CLE tool? You mean Stripe CLI?
yes, stripe CLE for debugging. was fine before i updated all my stripe DLLS
CLI with an I right? You wrote CLE again
I'm sorry, I have no idea what you're asking right now, all you say is you changed a DLL and that's it
Please try to provide a lot more details about the issue and what you're doing. Like which DLL? Do you mean stripe-dotnet?
i am making a trigger event.. in my cmd tool like this.
cd D:\Stripe
stripe login
stripe listen --forward-to http://localhost/Parex.pts.web.PublicServices/Webhooks/StripeParex/StripeHook/aud
that the login, not trigger. i get now
When i use this Trigger event now, i get error.
cd D:\Stripe
stripe trigger payment_intent.succeeded
and ive updated all Stripe packages to newest versions.
Sure but I need more than "I get errors"
Please provide actionable information: exact CLI version, exact stripe-dotnet version, exact Event evt_123
surbhi-cli-dotnet
-CLE version 1.13.12
-Stripe.net 41.10.0
-Run this command in my CMD(cd D:\Stripe
stripe trigger payment_intent.succeeded)
-
then in our code on this line ( Dim stripeevent As [Event] = EventUtility.ConstructEvent(json, sig, "ihaveinsertedcorrectkeyhere")
-
i get this execption.
{"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."}
-all this was working fine before we tried to upgrade to new Stripe packages....
Okay so the signature has nothing to do with the DLLs version at all
usually it's because you have the wrong webhook signing secret
every time you do stripe listen it will change the secret, make sure you use the right one
yes, the secret was same as before, expired 90days, it did not give me a new one.
is there a way to force a new secret
cd D:\Stripe
stripe login
stripe listen --forward-to http://localhost/Parex.pts.web.PublicServices/Webhooks/StripeParex/StripeHook/aud
pause
That did not make a new secret. how do i force it ?
you don't need to force anything, if it's the same secret it's fine
I'm sorry, right now you're still a bit cryptic. Like if you revert to the old DLL does it work? I assume not
when i do my listen, to get my secret... i get this....
D:\Stripe>stripe listen --forward-to http://localhost/Parex.pts.web.PublicServices/Webhooks/StripeParex/StripeHook/aud
Ready! You are using Stripe API Version [2022-08-01]. Your webhook signing secret is whsec_aecc26e00ad57567df210e7c5f41a2e5e9e58e85bf3a293bdfbf15f12c75c1ef (^C to quit)
--- the ERROR IS [2022-08-01]. . THAT IS the old webhook framework, how do i update that ? i am using localhost
i need 2022-10-01 version..
0h, i need to update this on the Dashboard.... - add an listen endpoint ?
Hmmm wait
Sorry I had missed that the API version was the issue. So yeah the CLI defaults to your account's default API version
but you can use https://stripe.com/docs/cli/listen#listen-latest
so when you do stripe listen also add --latest and it should use the newest API version which will match the one in stripe-dotnet
how do i change my version on the Account ? when i add webhook endpoints, it ask me to choose there, but where else do i change this?
So the API version is global for your entire account. If you change it, it will apply to both Test mode and Live mode. If you already have code in production it could break you
yes, we need to update now if we can.
but you upgrade the API version in Live mode under the Developers tab in the Dashboard at https://dashboard.stripe.com/developers (at the bottom)