raytiley

[warped wigeon]

Well you'd configure a regular, non-Connect webhook on your platform account which will only receive events that occur on your platform account

Otherwise you'd have a separate Connect webhook for events that fire on your connected accounts

If you're using the same URL/endpoint, then yes you'd need to filter those events accordingly. Your non-Connect events won't have the account field

https://stripe.com/docs/connect/webhooks

[marble sandal]

Right , I guess what I’m asking is with standard connect accounts, they are full regular stripe accounts. There could be products , payments , activity that has nothing todo with my platform

[warped wigeon]

Then only listen for the event types you need (i.e. checkout.session.completed)

[marble sandal]

What if they are using stripe with some Wordpress plugin as well that would fire those events.

Sorry if I’m being thick.

I just couldn’t really figure this out from the docs.

[warped wigeon]

You can configure which event types you want your webhook to recieve when you create it. Any other events will be ignored

Regardless of whether they fire on the account because of payments unrelated to your platform

You would still receive checkout.session.completed events, for example, from Checkout Sessions unrelated to your platform. You'd need to maybe apply metadata when creating the session to confirm it was created by your platform, and then filter on that in the webhook

[marble sandal]

That’s the piece I’m missing. The ability to add some session metadata

Is there anyway to add some extra metadata when using a PaymentLink?

[warped wigeon]

Should be supported? https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-metadata

https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-metadata