sushkin

[royal marsh]

For destination charges, all of the payment intent events would happen on the platform account itself. The connected account would only see transfer related events I believe

To answer your question more generally, the connect webhook will receive every event for every connected account that is on your platform. Stripe doesn't offer a way to filter out the events we send by account, so your webhook endpoint code would need to choose what accounts to listen to events for

[ripe minnow]

Thank you for swift reply!

[ripe minnow]

Actually I might have asked the question inaccurately.. What I meant is that for connected accounts we are receiving webhooks related to direct charges made through other platform accounts

@royal marsh

Is that normal behaviour?

[tender aurora]

Hello 👋 It is expected.
As direct charges objects are owned by the connected accounts themselves.
Any platform with a connection to that account will be able to receive the events for these objects.

We call it out in our docs too

https://stripe.com/docs/connect/oauth-standard-accounts#:~:text=As a platform%2C remember that data you create for a Standard account (for example%2C charges%2C customers%2C invoices%2C and so on) will be visible on their Stripe account. It also means that if they connect other platforms%2C those platforms can access this data too.

[ripe minnow]

I see. So, as Pompey suggested a way to filter those unwanted must be implemented in our code or is there another way to approach that?

[tender aurora]

It must be implemented in your code, yes.

[ripe minnow]

Alright, thanks for your help!

[tender aurora]

NP! 🙂 Good luck