#michael_error
candid idolBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1408487652872818751
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
coral mason
do you have a Webhook endpoint ID I can review? An account ID would help as well. Also for clarification where are you seeing these additional events? Our Dashboard will show event logs for all events, they just won't be emitted to the Webhook endpoint unless the endpoint is configured for those events.
glossy mirage
Yes I do One second
Endpoint URL
https://stripe-backend-wj3v.onrender.com/webhook
API version
2025-05-28.basil
Listening to
1 events
checkout.session.completed
coral mason
Do you have the ID? This usually starts with we_ If you have the account ID I can also look up the endpoint on your account that matches the URL
glossy mirage
Destination ID : we_1RyevgLIZP46JbFXRlamqNC4
coral mason
Perfect, taking a look
glossy mirage
Do you need the signing secret too or no ?
coral mason
Nope 🙂
https://dashboard.stripe.com/acct_1RbaUxLIZP46JbFX/test/webhooks/we_1RyevgLIZP46JbFXRlamqNC4
Looks like the only events being sent to that endpoint are checkout.session.completed
Can you also confirm is your server running live or test mode keys?
glossy mirage
My server is running on Test Mode
This means the charge.succeeded and payment_intent.succeeded events I am seeing in the logs are not being sent by that webhook endpoint.
The only remaining logical explanation is that these events are being sent from a different source.
The most likely culprit is a separate local process, like the Stripe CLI, that I may have started in the past and forgot to shut down. It can forward all events from the test account to a specific URL, which would explain why I am receiving multiple events on my Render server.
coral mason
To clarify if your seeing these on your server logs and not in Stripes dashboard then forwarding from Stripes local listener would be a likely culprit.
glossy mirage
How do I Stop the Stripe CLI ?
coral mason
Ctrl+C in the terminal it's running from. I'm guessing maybe it's on your local development device?
coral mason
A reboot would also do the trick if for whatever reason you can find the terminal it's running in.
or the process was sent to the background
glossy mirage
got it
let me try that and I will get back to you
thank you so much again for helping me with this
coral mason
Any time!
glossy mirage
So I deleted the Stripe CLI and tried going through a test payment and it went through I was able to receive the email confirmation without a problem
I am guessing it works now ?
how can I make sure the signature verification is passing? or the fact that I was able to receive the email prove that
coral mason
if the email confirmation is being triggered by a webhook event that's promising
checking on my end
glossy mirage
okay
coral mason
looks like your server is responding to the events we emitted with a 200 so that is also promising.
You could have your server route that responds to webhook events try and print out the event object to confirm it's working properly as well.
candid idolBOT