#jack_connect-webhooks

1 messages ¡ Page 1 of 1 (latest)

tawny flareBOT
#

👋 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/1278826143025205279

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

odd quest
cyan tiger
#

jack_connect-webhooks

#

@odd quest I'm assuming you are a Connect platform and this specific WebhookEndpoint is a Connect WebhookEndpoint made to listen to Events on your connected account (which your screenshot confirmed)
In that case it's entirely expected. See our docs at https://docs.stripe.com/connect/webhooks where we say

For Connect webhooks, only test webhooks are sent to your development webhook URLs, but both live and test webhooks are sent to your production webhook URLs. This is because you can perform both live and test transactions under a production application. For this reason, we recommend that you check the livemode value when receiving an event webhook to know what action, if any, users should take.

odd quest
#

Ahhhh I see, thanks!