#rstupek-connect-webhook
1 messages · Page 1 of 1 (latest)
If you make the endpoints list call as that account it should list their endpoints
https://stripe.com/docs/api/connected_accounts
https://stripe.com/docs/api/webhook_endpoints/list
thanks... also I was trying to get the list of paymentmethods enabled on the connect account
Also I did try that and I am getting an error oauth_not_supported
Can you send me the ID for that request (req_123)?
And I assume you are retrieving the account object and looking at its capabilities?
req_wLRbhSNHdSeMbR
Ah gotcha, apologies, I did not realize there was a connect restriciton on that endpoint. It looks like it isn't currently possible to list a connect account's endpoints via the API
rstupek-connect-webhook
Can you tell me a bit about your usecase here and what you are trying to do?
@swift loom as a platform, there's no reason for you to look at the webhook endpoint(s) configured on a connected account
As for the "list of payment methods enabled" we don't have that feature yet. We do have a beta that is ongoing though. See https://stripe.com/docs/connect/payment-method-configurations
I'm trying to correctly configure the webhooks for a connect account programmatically as the application developer so I can handle the web hooks for payments
so knowing if I've already configured the webhook was my first to do
But as a platform you're not allowed to do that at all on a connected account
You're supposed to use this: https://stripe.com/docs/connect/webhooks
You have a specific type of webhook endpoint (Connect) on your own platform account that receives Events for all your connected accounts
so to clarify, if I want to know if an afterpay payment, for example, is succesful on a connect account I am required to handle that through one webhook for all connect accounts?
yes
ok little janky
It's a lot cleaner this way, each Event will have a clear property account indicating which Account it's coming from, it'll use your own platform's API version by default and any custom settings or features you might have, etc.
not sure I see that as cleaner than directing the Event (payment success and failure) for an account to a webhook on their own site
I guess I an instruct them to setup the webhook for their account themselves, just not as low friction
they would do this in the Dashboard, which would use their account's default API version, so your code would need to basically handle any API version we ever made (and will make) which wouldn't really work
I created their account for them, wouldn't that be based on the api version I used to create the account?
no it would not. The defautl API version of an account is always the latest API version at the time of their first API request
ok thanks for the direction