#Alain
1 messages ยท Page 1 of 1 (latest)
Hi ๐
The only difference is that in Live mode we interact with issuing banks. If you are seeing 500 errors can you provide the ID for an API request where you see this error?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Yes here the req id :
req_als9hUIh6S8Yjj
This request returned a 200
But it required 3DS authentication
That's the webhook
That 500 is from your webhook endpoint
Yeah my question was about the webhook
in test mode the webhook is working perfectly
that's why I was asking if there is any difference between the events we receive in test and live mode
on a webhook
in order to try to understand why it's working in test mode but not in live mode
Can you share that webhook event ID?
"id": "evt_3MZxRxFkgdhsoVd90hYo7cKG"
I see three delivery attempts with this event. One of them is successful but returns {"status":"fail to verify signature : No signatures found matching the expected signature for payload"}
The other 2 fail on your server with 500 response
Yes, it's what I'm trying to figure out
because on test mode I have this response
the only thing that I change in the configuration are the api keys
between test and live mode
The webhook secret is different between the two. Is that what you mean by the API key?
Can you include logging in the live endpoint to ensure the Webhook secret is being loaded into the runtime.
One of the most common issues encountered when going for a test environment to live is the webhook secret isn't being loaded into runtime so the signature verification fails
Yup I would log both the sig_header and stripe_endpoint_secret before the try block
you mean even before the first try with the load ?
Yes, since both should exist at that point
Yeah ok I'm going to add those logs
well I'll keep you updated then because to see the result I need an other real payment
Right. Since this is the Live mode webhook endpoint. We'll be here to answer your questions as they come up