#kemal_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/1364541219132145696
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- kemal_api, 20 hours ago, 14 messages
- kemal_connect-account-payout-delays, 1 day ago, 16 messages
- kemal_api, 1 day ago, 2 messages
- kemal_api, 5 days ago, 8 messages
hi there!
you should listen to the account.updated event, and check the payload to see if the account is fully verified or not
this is covered in details here: https://docs.stripe.com/connect/handling-api-verification#determine-if-verification-is-needed
how can i understand to say if account is fully verified ?
Which fields should i be checking. ?
That's answered in the doc my colleague linked:
The Account object’s charges_enabled and payouts_enabled attributes indicate whether the account can create charges and accept payouts.
and
The Account object has a requirements hash, representing the requirements needed to verify the account.
will it be eventually_due list ultimate list to be cleared to be verified ?
Well they may become due, depends on account activity. It depends on your use case whethere you want to collect those requirements now, or risk waiting until they become due
we want to customer to clear all requirement to get payout
we
we ve disabled payouts until KYC done completely
Then sure, ensure there are no requirements at all. You can configure onboarding UIs to collect all requirements if you're using them
we use stripe onboarding, we still want to accept payment but to keep payouts disable untill KYC done and get notified when KYC done
basicly our problem is now gettting notified when KYC done for connected account
Well that is explained in the link above – we wouldn't payout funds until accounts were verified anyway
account. requirements map is very complicated. which field should i check if KYC done 100%
I already answered this. There's no one field
If you're using hosted onboarding, you can configure which verification info we should collect: https://docs.stripe.com/api/account_links/create#create_account_link-collection_options
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.