ynspc

[worn thunder]

Hi 👋

I'm sorry but your description isn't very clear to me from the standpoint of Stripe objects.

A Connect Webhook endpoint will receive all events for your Connected Accounts that you listen to. Are you asking how you can tell the difference between subscriptions you create and those that are created by the Connected Account themselves?

[mossy obsidian]

ok sorry i will try to my best to explain the scenario

we are planning to build a system which provides services on the basis of different subscription plans. So this is the main account in stirpe

[worn thunder]

Please keep your explanation focused on Stripe records and objects

[mossy obsidian]

yeah

just wondering on point of view from stripe platform and stripe connected account. If both of them have to handle the webhook then, do we need to handle separately or single end point will be suffice?

[worn thunder]

You will need to register two webhook endpoints. One for your account and one for connected accounts

But they can both point to the same URL

[mossy obsidian]

Ohh nice

[worn thunder]

As long as you have sufficient logic built into your integration to differentiate these events and handle them appropriately

For Connected Accounts, the Event object will include the account property https://stripe.com/docs/api/events/object#event_object-account

which will tell you what Account they are coming from

[mossy obsidian]

Yeah thank you. And
Currently I am working on [standard type] connect account onboarding. While onboarding a connected account, numerous web-hooks is triggered where status stayed inactive, which seems to be correct state.
After verifying the email, It seems like status updated to active.
Is this correct ? I believe when we provide the user document then only the status should be active, else before giving user document and verified from stripe, I will have updated the stripe connect status to active.

i've used stripe account link endpoint
POST /v1/account_links