#emil_api
hearty galleonBOT
đ 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/1506268067142041712
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
amber scroll
When is that due?
You can check the account API to get the date of the deadline
https://docs.stripe.com/api/accounts/object#account_object-future_requirements-current_deadline
orchid owl
Do you know if that field in particular will become a currently_due / past_due ?
orchid owl
Ok thanks for the information. I want to postpone the identity information to later when I initiate the external account information. But If that happens after the identity information becomes due, then maye its not a feasable strategy
Could you point me to the correct place in the api where I enter the identity information? If I would like to do it using the API i mean instead of the embedded onboarding
amber scroll
> When is that due?
You can check the account API to get the date of the deadlin...
You should get the path of the field that you need to fill in the API here
Here is a complete guide about handling verification with the API:
https://docs.stripe.com/connect/handling-api-verification
orchid owl
Ok thanks! I get the feeling from the docs that you want developers to provide all currently_due information at one go.
But I only want the connected account to be able to receive payments. Then external_account should not be currently_due since that only controlls the payouts_enabled attribute of an account. Can I do something different when creating an account to only have the currently_due information which allow for receiving payments (charged_enabled?)? For example creating the account with some capabilities at first and then at a later stage when I want the account to be able to receive payout add more capabilities (and subsequently adding more requirements)
amber scroll
I get the feeling from the docs that you want developers to provide all currently_due information at one go
No there is nothing explictly mentioning this. You can provide documents on the fow
Can I do something different when creating an account to only have the currently_due information which allow for receiving payments (charged_enabled?)? For example creating the account with some capabilities at first and then at a later stage when I want the account to be able to receive payout add more capabilities (and subsequently adding more requirements)
I think that's possible
https://docs.stripe.com/api/accounts/update#update_account-capabilities
"Each capability is inactive until you have provided its specific requirements and Stripe has verified them"
orchid owl
ok thanks, Ill try it out
amber scroll
Happy to help!