#akkusomer1
1 messages · Page 1 of 1 (latest)
Hello! 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.
- akkusomer1, 17 hours ago, 10 messages
- akkusomer1, 4 days ago, 13 messages
- akkusomer-email-testmode, 5 days ago, 11 messages
- akkusomer1, 5 days ago, 17 messages
Are you asking if you endpoint will receive events in test mode? If this endpoint is configured for test mode, then yes
I added a webhook but I'm getting a 403 forbidden error.
No, I did not add the web hook endpoint as a local listener. Because I deployed my application and it is now in real life.
What I mean is, can I trigger this webhook if my application is in real life while the stripe is in test mode on the dashboard? Or do I need to switch to a stripe active account for this?
I hope I was able to explain. I'm trying to detect the 403 forbidden error.
Where do you see the 403 error?
I make a payment with a stripe test card, then the web hook endpoint should be triggered, but I see that I get a 403 error in stripe > developers > webhook. I also see the same error in the logs of my server.
I allowed the IPs of the strip, but this problem still persists.
Ok, it's your server that responded 403. Have you checked your server log?
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403 The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.
Yes, it returns 403 in the server log.
What is the answer to this question ? "What I mean is, can I trigger this webhook if my application is in real life while the stripe is in test mode on the dashboard? Or do I need to switch to a stripe active account for this?"
The answer is yes, but your server is responding 403 instead of 200, you should check your server and figure out why it's not returning 200.