#devik
1 messages · Page 1 of 1 (latest)
Those statuses don't map directly to fields on the API object. This doc lays out what each of them mean:
https://stripe.com/docs/connect/dashboard#status-badges
And our API ref has info on what each of those fields are named on the customer object
https://stripe.com/docs/api/accounts/object
Great, thanks! Can I somehow force Stripe to collect all requirements in onboading to skip Enabled and go straight to Complete?
And how can I infer if the status is Pending?
When you create the onboarding link, you can tell it to collect eventually_due requirements. That will tell Stripe to collect all of the requirements info that we are are currently aware of https://stripe.com/docs/api/account_links/create#create_account_link-collect
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Details submitted is how you can check if the initial onboarding submission has happened. So If that is true but the account doesn't meet the requirements for other statuses like complete you can infer it is pending https://stripe.com/docs/api/accounts/object#account_object-details_submitted
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.