#koidestroyer
1 messages ยท Page 1 of 1 (latest)
What kind of Connect account are you creating? Express, Standard, Custom?
custom
Are you using the Custom Account Onboarding portal? Or a custom onboarding portal?
In other words do you have an in-house solution or are you using the Stripe hosted solution?
I'm using the Stripe solution.
I enter all the information using the Stripe hosted pages.
Ah okay. And are you setting collect: eventually_due or collect: currently_due when you create the Account Link: https://stripe.com/docs/connect/connect-onboarding#info-to-collect
currently
that means that I'll only be able to enter the bank account after I've sent some payments to that account?
You will need to specify eventually_due in order to request bank account right from the start.
That asks for all information that will be due on the account in the future as well as the present time, thus satisfying all the requirements (including bank account)
okay, and when is the bank account due?
(to know when would I be able to enter it using currently_due)
You can enter it at any point after onboarding, but it will only shift to currently_due after either (a) the account's processing threshold is reached (usually around $5,000 USD or equivalent) or (b) the account has been open for a certain period of time. When bank account becomes currently_due you will see it show up in requirements.currently_due (see here: https://stripe.com/docs/api/accounts/object#account_object-requirements-currently_due) on the Account object and it will have a corresponding requirements.current_deadline (see here: https://stripe.com/docs/api/accounts/object#account_object-requirements-current_deadline) that you can check to see when it is due.
Unfortunately those 2 things are variable, so there isn't a way to check when something that is eventually_due will become currently_due
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
๐