#abdullah-yousuf_webhooks

1 messages ¡ Page 1 of 1 (latest)

whole ospreyBOT
#

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

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

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.

waxen igloo
#

i get account updated on normal webhooks while onboarding to stripe connect which is the only time we are listening to stripe connect webhooks
so my question is why use different webhooks
we can handle account.updated from normal webhook since it is also triggered. and while transfering to connected account. transfer.created event from normal webhook

autumn echo
#

Hello

#

account.updated will only be triggered to your Connect endpoint when it fires on Connected Accounts.

#

If you want, you can use the same endpoint here.

#

Connect Webhooks will contain an account ID in the response body.

#

As for why this is the case, it is how things were built mostly.

#

Connect and Direct Webhooks flow through different infra mostly.

waxen igloo
#

same event account.updated

autumn echo
#

If it is the Standard Connected Account, then yes.

#

But mostly it depends on the situation.

#

As a platform you should use a Connect endpoint to listen for Events on your Connected Accounts.

waxen igloo
autumn echo
#

Can you provide the Event ID you are referring to here?

waxen igloo
#

or is it because i am listening and connected to local webhook ??
there is no option for only stripe connect local webhook. the normal local webhook is for both ig??

autumn echo
#

Not really sure what you mean, sorry.

#

Direct Webhook endpoints are for Events created on your own account.

#

Connect Webhook endpoints are for Events created on the Connected Account.

waxen igloo
#

event id : evt_1QmGSNQmE7QrJiipw9tj0LGi

autumn echo
#

That Event was only sent to Connect endpoints.

waxen igloo
#

while locally adding an endpoint for webhook it gives you a webhook secret..
for local listening of events
is it also for stripe connect?

autumn echo
#

Ah are you using the CLI here to forward Events?

waxen igloo
#

yes i am forwarding it to local host.
but not triggering the events manually from cli.

autumn echo
#

Yeah okay that's why -- the CLI will receive both types of Events.

#

This is supposed to make it easier for you to do development, but I can understand that this is confusing here.

#

When not using the CLI you won't receive Connect Events on your Direct endpoint.

waxen igloo
autumn echo
#

Yeah sorry I didn't understand what you meant by that.