#hernando-webhook-connect
still swan
@broken widget hello! You get those because your connected accounts have activity.
You can configure your endpoint to only listen to some events, but it's expected that you get events from all the connected accounts
broken widget
Ok, I think it may be ok, but can we filter them out?
still swan
what do you call "filter them out"? Can you be specific about what the issue is?
broken widget
Let me share what we do, once a payment is done, we check the webhooks for those payments that has been made and once we receive that the user has correctly placed the payment, we give them credits to do stuff, but because we are receiving that events even for our connected accounts, we are having a lot of errors from our servers because these accounts aren't on our systems, so ideally, I would like to manage webhooks that come from our main accounts, and not third parties
still swan
hmmm
There are 2 types of webhook enpoints:
- Account webhooks are listening to events on your own Stripe account
- Connect webhooks are listening to events on all your connected accounts
If you create the former, you only get events from your own Stripe account. If you create the latter you will get all events from all your connected accounts
It's not possible for you to create the latter and also only get activity that your own platform is responsible for. If the connected account has multiple platforms, that also create activity, you get all events
That was a bit confusing so we changed the flow last year and we describe it in details in: https://stripe.com/docs/connect/oauth-changes-for-standard-platforms
This allows platforms like yours to get a new account for your own activity, not mixed with other platforms
you likely want to chat further with our support team: https://support.stripe.com/contact