#maxtendr_best-practices
mental gulchBOT
đ 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/1273651696517648484
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
copper vine
Is it sufficient to just check the requirements hash on the account object, or should I also be checking it on each of the capabilities?
Generally sufficient to look at account requirements. You can read more about requesting capabilities here: https://docs.stripe.com/connect/account-capabilities. If requesting new capabilities it can be helpful to check their requirements ahead of time.
Not automatically, no. You need to tell it to collect future requirements if you want that: https://docs.stripe.com/api/account_links/create#create_account_link-collection_options-future_requirements
celest crypt
Thank you for the information.
So just to confirm, if the account has multiple capabilities with each having status 'active', is not disabled (no 'disabled_reason'), and has no requirements/future_requirements on the account object, it's safe to assume that the account will be able to use those capabilities now and in the future without needing to check the capabilities object at all?
Noted regarding the the account link parameter, thanks
copper vine
it's safe to assume that the account will be able to use those capabilities now and in the future without needing to check the capabilities object at all?
You should listen for account.updated events to monitor requirements and future requirements