#john_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1338896350435213462
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Yep, that is a good basic overview of our onboarding process. Bank account can definitely be collected as part of the initial onboarding. If you aren't seeing it by default, it should definitely show up if you specify to collect eventually_due data for when creating your onboarding link.
thanks @proven kiln
possible to get link to the documentation?
also, if we want to separate out the linking of bank account - what information do we need to pass?
This code snippet shows how to set eventually due. I don't think there is a way to separate out specifici fields like that but will double check
https://docs.stripe.com/connect/custom/hosted-onboarding#info-to-collect
Yeah it looks like the only options are currently_due and eventually_due as in the info needed right now to activate the eaccount vs that + the info that has a deadline a bit further out
https://docs.stripe.com/api/account_links/create#create_account_link-collection_options-fields
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
@proven kiln
can you please elaborate the use of currently_due & eventually_due, in terms of onboarding?
also, how what is the best way to know whether the user provided all the information during onboarding and that the onboarding is complete
What kind of info are you looking for on currently vs eventually due? Happy to look in to it
And yes there is a property on the account object that you can check. Finding that
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I meant do we know what additional information is gathered for eventually_due?
Ah gotcha, account objects have a requirements property that has two sub-properties currently_due and eventually_due that list out the details that need to be collected. Eventually due includes everything that is currently due and then any details that need to be collected because of their current capabilities, but that don't need to be connected right now
https://docs.stripe.com/api/accounts/object#account_object-requirements
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
thanks @proven kiln
is there a webbook that delivers notification that a Connect account is completely setup and that is ready for payouts?
Good question. You would want to listen to the account.updated event and check the payouts_enabled property on the account. To check if the updated event was triggered by that specifically, you can check the previous_attributes property on the event to see if it contains payouts_enabled. If it does, that means that that property was changed for this event
https://docs.stripe.com/api/accounts/object#account_object-payouts_enabled
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.