#Baris-Connect
1 messages · Page 1 of 1 (latest)
Hi there, details_submitted=true indicates that the account has completed the onboarding process, charges_enabled=true means the account is ready to accept payment.
I don't understand what I should be rendering to the user. Currently, if details_submitted is false on the user, I call createAccountLink with the saved account id. But if charges_enabled is false (I assume if it was true, details_submitted had to be true?), I keep calling account retrieval to check charges_enabled
But it doesn't become true at all
When details_submitted is true, does that mean it is a matter of time before charges_enabled becomes true?
OK, let me walk you through with an example.
Would be great thank you
Like say your user is using the Connect Onboarding link to for onboarding, and they has provided some information that is enough to get charges_enabled=true, but they haven't provided information (i.e., external_account) to enable payout.
In this case the details_submitted=false, charges_enabled=true and payouts_enabled=false
I wasn't aware this set of values could occur. Also wasn't aware of the importance of the payouts_enabled variable at all
So now your user can start collecting payments, but it doesn't means that the onboarding process is completed. You should always check the requirements.currently_due (https://stripe.com/docs/api/accounts/object?lang=curl#account_object-requirements-currently_due) hash of the account object to see what information are needed, once these information are provided, the account is fully onboarded and details_submitted flag will become true.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Well i get that details_submitted is true but charges_enabled is false
Where should i direct in this situation?
Can you share with me the account ID?
acct_1LQji4PgjdeT4XgQ
So, which one is the most important field? Like which one should i use to say you are good to go
To let the seller add products
I'd say the requirements.currently_due is the most important field, it tells you what information you need to provide
Right now this account is restricted, and you need to provide the owner's address
sorry i am just getting more confused right now
what is the user sequence logic here
- use /account API to create an account
- use/accountLink API to create an account link for onboarding
- Once your user has completed the onboarding process, it will be redirected to your page
- Listen to account.updated events and check the
charges_enabledflag, if it's true then it means your user is able to accept payments. You can also check thepayouts_enabledflag, if it's false it means your user can't receive payout. Now you can decide whether to do upfront onboarding (e.g., collect all info) or incremental onboarding (collect the info piece by pice). https://stripe.com/docs/connect/identity-verification#onboarding-flows
If the main objective is to allow your user to sell products (e.g., accept payments), you just need to make sure the charges_enabled flag is true. You can always ask your user to complete the onboarding for payout enablement later.
Yes I understand it better now
For the user with the above account_id, I supplied an address but still giving charges_enabled false and the onboarding registration doesn't mention any lacking fields
Could you look into this?
How did you add the address?
Another question I have is about the payout process. Basically, I am coding a marketplace app for people to buy a product locally. So, I need a confirmation from the buyer to know that the transaction successfully happened in a span of one week. What structure could enable this model?
By the onboarding process on stripe
It started working now, maybe it just needed some time?
You can use manual payout so that you can create a payout to a connected account when you feel comfortable.
Okay i see thanks for your help a lot