#jonathanhayuniverse_connect-account-capabilities

1 messages ยท Page 1 of 1 (latest)

green sailBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1429855598345846784

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

wicked anchor
#

Hello, do you have the request ID from a time you made this call? (req_123)

#

If you have an example of a time the field was there and a time it wasn't that would be perfect but I get that that is unlikely unless it happens enough that you can retry now and get both.

terse stone
#

Sure, I'll see if I can grab one! it seems to be consistent across accounts, this one acct_1NLOe6F5iSyRKs94 is an example of one which does not return this field, give me a moment

green sailBOT
sturdy solar
#

Hi ๐Ÿ‘‹

I'm stepping in as my colleague needs to go. For what it's worth, I have never seen any documented field on the Account object called active_payment_methods. If you can find an API request that returns this field I will be happy to dig deeper.

terse stone
#

Yeah I was having trouble finding the API reference as well, was wondering if it is a composite field in the ruby sdk, will do

sturdy solar
#

One of my colleagues found some documentation implying this was a private feature enabled at one time but has since been deprecated. I've been looking for more information but I haven't been able to find more records of it

terse stone
sturdy solar
#

Okay. But what I am saying is that this was not ever a GA'd feature of our APIs. It was a private feature for a limited number of users and it has since been deprecated. So it is expected that you will not receive this property in API responses.

terse stone
#

Are there any other fields which aren't deprecated which would contain fundamentally the same data?

sturdy solar
#

The capabilities property is pretty close and it actually includes more detail (e.g. active, inactive and pending statuses)

terse stone
#

Alright, we can work with that, thank you!

sturdy solar
#

Sure thing, happy to help!