j0e_webhooks

[west flame]

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

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

[modern glacier]

👋 happy to help

[keen minnow]

Sorry for delay, looking into it.

This webhook endpoint (we_1Ov83jESm1Rqnz4xaWfsysAc) belongs to the Platform and is listening to the events on the account itself, not on the Connected accounts' events. And this connected account - acct_1OyVwXIbvskrPvEM - has multiple account.updated events.

That's why the webhook endpoint didn't get the events you're looking for.

[flat hawk]

https://docs.stripe.com/connect/webhooks - Connect webhooks are for activity on any connected account. All events on the connected account are sent to the Connect webhooks. This includes the important account.updated event for any connected account and direct charges.

shouldn't I get notified for account.updated account Allows you to monitor changes to connected account requirements and status changes. Available for Standard, Express, and Custom accounts.

similar to evt_1Oy0ODESm1Rqnz4x7Bni7o7v

[keen minnow]

Yes, and the webhook you shared is not a Connect webhook endpoint.

Just a regular Account webhook endpoint.

[flat hawk]

ah well, that might well be the issue then. let me dig into that

[keen minnow]

You need the one on the right.

[flat hawk]

😳 thanks

[keen minnow]

Happy to help.