#basieboots_api

1 messages ¡ Page 1 of 1 (latest)

regal basinBOT
#

👋 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/1265248643699572778

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

sleek ledgeBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

glacial narwhal
coral forge
#

look in the dashboard you guys have statuses for the connect accounts, I don't want verification I want to show the status of the account the rest is up to the user

glacial narwhal
#

yes I'm aware there is a status/badge in the Dashboard for this, and I'm aware it's a super common feature request to have such an enum in the public API, and unfortunately that doesn't exist yet.

coral forge
#

now if that doesn't exist and you do things by checking if verifications are required and if not required that's fine BUT you have multiple types of statuses and no explanatins for those

#

it doesn't have to exist, but you should have the logic of how you display those statuses somewhere for reference since thtat is kind of a basic ui thing

glacial narwhal
#

yep totally agree and as I mentioned, super common feedback we're aware of

#

I can't give you a reference for how we compute those badges sorry. What I suggest is checking the fields in the documentation I linked, and the status of the capabilities on the account, so your code can know what the account is able to do and/or what actions it might need to take

coral forge
#

well how about you try to explain how you come to those statuses instead. There should be a cohesiveness between what's shown and what Stripe is showing and so you should be supporting that

glacial narwhal
#

I gave you an answer, sorry. Any other topics I can help with?

coral forge
#

you didn't give me an answer

#

you told me that you wouldn't support

#

that's not ok

glacial narwhal
#

not sure what you mean, I gave a very detailed answer explaining the context and giving a workaround.

coral forge
#

you have a variety of status that you show in the dashboard, you should be able to explain how you get to those statuses so that a developer can display those things

#

you gave me nothing, especially not details

#

actually no you've given kind of a bad attitude

#

that's something you've given

glacial narwhal
coral forge
#

you do have a better answer, you can outline the different statuses and what they coincide to. But what you're choosing to do instead is not support and have a poor attitude about it. The logic exists and instead of finding out the information I'm asking for you're jsut saying oh well we know our customers want this informaiton but I don't care enough to be bothered supporting

glacial narwhal
coral forge
#

that's a lot more helpful, but it still doesn't coincide to the account api call elements. So being a little more specific on which badge coincides to which variable would be more helpful. The last thing I want to do is guess about what stripe might be showing my clients. Enabled and complete seem straightforward where there is nothing under requirements. But that link seems to mostly be referring to items on the dashboard versus the account data brought in by the Api

#

if that makes sense