vinoth-kumar_api

[muted plinth]

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

📝 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.

• vinoth-kumar_api, 6 days ago, 35 messages
• vinoth-kumar_api, 6 days ago, 40 messages

[hasty basalt]

Hello, can you tell me more about what you are trying to make here? And what API calls did you make here exactly? If you retrieve the account and its type is express or custom or if it has a controller.type of application then it is definitely a connected account, but there isn't anything on the object that specifies this for standard accounts. Standard accounts can both be connected to a platform and have other accounts connected to them, so being a connected account or platform account are not mutually exclusive.
https://docs.stripe.com/api/accounts/object#account_object-type
https://docs.stripe.com/api/accounts/object#account_object-controller-type

[tender plaza]

I tried to add the Webhook type through API, the connected accounts throw error as
You are not permitted to configure webhook endpoints on a connected account. Did you mean to create a Connect webhook on your account instead?

So If it is a connected account, I will skip the Webhook type API process

Based on the document, if we add connect in the webhook API, then it will add the endpoints but not sure whether it will work for the webhook endpoints as like as main account.

[hasty basalt]

Can you explain your setup a bit more? How are accounts connecting to your platform in a way where your integration unsure if they are a connected account or not?
Connect webhooks are definitely the way to go for events on connected accounts. It does work pretty much the same as our normal webhook events. You set up one webhook endpoint for connected accounts and then Stripe sends all events from those accounts to that endpoint as well. The event will include an account property that designates which account the event is from
https://docs.stripe.com/connect/webhooks

[tender plaza]

Does all the webhooks available in the main account is also available for the connected account?

[hasty basalt]

All of the same event types? Yes

[tender plaza]

For example
'charge.failed', 'charge.refunded', 'payment_intent.payment_failed', 'payment_intent.succeeded', 'setup_intent.setup_failed', 'setup_intent.succeeded',

@hasty basalt Just to confirm, If I create a webhook with url, and enabled_events with the connect parameter in https://docs.stripe.com/api/webhook_endpoints/create does it update the respective connected site or will it update all the connected sites belongs to the main account?

[hasty basalt]

Can you tell me more about what you mean by "connected site" here?
If you create a connect endpoint on your account, it only effects your account. It basically means that going forward we will send all of the enabled_events from all of your connected accounts to that endpoint. So if you set up https://example.com/connect as a connect endpoint and payment_intent.succeeded was one of your event types in enabled_events then you would get a payment_intent.succeeded event every time one of your connected accounts completed a payment and

[tender plaza]

Ok, thank you so much