#hayate-details_submitted
1 messages · Page 1 of 1 (latest)
heya @novel steeple! can you share what connected account type are you using? i.e. custom/express/standard?
Hi Alex, I am using express.
Sorry Alex here are some more details and the cause of my confusion:
This paragraph:
A user that’s redirected to your return_url might not have completed the onboarding process. Retrieve the user’s account and check for charges_enabled. If the account isn’t fully onboarded, provide UI prompts to allow the user to continue onboarding later. The user can complete their account activation through a new account link (generated by your integration). You can check the state of the details_submitted parameter on their account to see if they’ve completed the onboarding process.
Found at the bottom of this page: https://stripe.com/docs/connect/express-accounts
It is not clear to me.
For example: A user that’s redirected to your return_url might not have completed the onboarding process. This is super clear and very understandable.
But then it says: "retrieve the user account and check for charges_enabled", but this parameter does not tell me if onboarding is completed or not. charges_enabled could be false even when the onboarding is completed.
So is the details_submitted the definite parameter that tells me that onboarding is completed and I can stop using stripe.AccountLink.create and start using *stripe.Account.create_login_link ?
hmmm, give me a while to look into this, i'm not too sure if details_submitted will ever move back to false
OK, thank you so much, Alex.
In short, I would like to know what parameter should I look for (in the connected account object) that will tell me if I should use stripe.AccountLink.create or stripe.Account.create_login_link.
If details_submitted never goes back to false, then I don't need to worry. So the first time details_submitted turns true, I will start using stripe.Account.create_login_link.
But if it does turn back to false, does it mean I will have to revert to using stripe.AccountLink.create again?
once details_submitted=true, it does not get flipped back to false.
You would want to use webhooks to listen to account.updated events and pay attention to the requirements hash and respond appropriately (send their account an account_link or message to login and update) when an account does have outstanding or upcoming requirements.
Thank you for your time and help, Alex.
If you have a way I can buy you a cup of coffee, please let me know!