#Klauz-capabilities

1 messages · Page 1 of 1 (latest)

fickle flame
#

@fleet zinc hi! do you have an example of an account(the acct_xxx ID) where that's the case? if I can have a look there's probably a reason(my guess is maybe it's legacy/old account or something related).

fleet zinc
#

acct_1KEyihRTcJC5oOm8 for instance

#

I could compile a list of all of them so far if needed

fickle flame
#

thanks, will take a look

fleet zinc
#

Thanks

fickle flame
#

hmm, seems normal enough. Can you share the exact code you're using and how you inspect the dictionary returned? I tried creating a similar account on my side and can see those capabilities, and nothing unusual about that account jumps out at me so maybe it's just something about how you look at it

fleet zinc
#

account.capabilities.card_payments

#

using the python lib

#

account being the account object ofc

#

the problem does not happen everytime

fickle flame
#

you should technically always be using https://stripe.com/docs/api/capabilities/list instead of the embedded list.
My guess is (because I see the same thing on my testing) that there's an API version change or something I'm missing that means that field is not returned(we have been trying to stop including embedded lists in objects like this), checking something...

#

oh right

#

account.capabilities only includes active capabilities on that account. If you want to see all possible capabilities for the account and their status, you'd use the API I mentioned

#

so that's why. So the cases where you're not seeing it is just accounts that don't have the capability active(haven't finished onboarding or have been disabled pending more information required, etc).