#peter_webhooks
dry jettyBOT
👋 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/1224818888609628191
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
plush ridgeBOT
lunar tangle
The choice of webhook events depend on your integration really (what information your integration needs in order to do x... y... z...)
Are you using subscriptions?
if so, this is a pretty good doc to understand when certain events are triggered: https://docs.stripe.com/billing/subscriptions/webhooks
dry jettyBOT
tropic plinth
Thx for the link. Yes, subscriptions and payment intents. I think I’ll have to just do a deep dive at some point, between listening to charge.*, customer.subscription.*, customer.*, invoice.*, and checkout.session.* — it’s causing a bit of the overload on the webhook when a new subscription is created
LMK if I need to open a separate question, but I appear to have received a test-mode event on my production-mode webhook from a connect account?
event: evt_1P104pFZCj0yycQh41AxgKdJ
account: acct_1NmarOFZCj0yycQh
request: req_hvNoLRZfg61BRR
It looks like a Stripe Standard Connect account created a test mode charge. Is it possible the events from that came through my production-mode webhook? (I think it’d be this one: we_1GylfQFMpnKnvESqJZi164ia)
gilded stirrup
Hi there, catching up since my teammate needed to step away
This is expected: https://docs.stripe.com/connect/webhooks#connect-webhooks
Live and test events are sent to production webhooks