#Xavier

1 messages · Page 1 of 1 (latest)

velvet axleBOT
topaz plaza
#

so really you can just remove --stripe-account, it's not needed.

haughty root
#

well I'm trying to see what the typical response of an actual account.updated webhook would look like

#

I'm not really interested in the platform account.updated

topaz plaza
#

it's not a platform account.updated

#

it creates a connected account, updates that connected account, so it will generate an account.updated event on that connected account which is sent to your Connect endpoints, which seems like what you're looking for!

haughty root
#

oh I see, so account.updated is creating a connect account and triggers?

topaz plaza
#

yep, that's what I said!

haughty root
#

haha yeah i realize that, I was rephrasing to make sure I understood 😄

#

Side question. If an account is not managed, I understand that we do not have access to the settings key, but I'm a little bit baffled that we do not have access to the payouts_enabled. I gather that's kind of what wraps up stripe's verification process.
What would you recommend otherwise to make sure this non managed connect account is legit

#

(apart from charges_enabled)

topaz plaza
#

but I'm a little bit baffled that we do not have access to the payouts_enabled.
not sure what you mean by that, can you elaborate/give some examples? I created a type:standard account just now(if that's what you mean by 'not managed') and payouts_enabled is returned in the JSON response

haughty root
#

hum I just triggered the webhook as you mentioned and payouts_enabled is not part of the response

#

request id req_EsTmE0SolmTTta

topaz plaza
#

you're on a 2015 API version from when the API was very different

haughty root
#

oh wow, I didn't realize I was