#harshthakkar_api
swift fableBOT
đ 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/1283593462448390257
đ 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.
- harshthakkar_api, 5 days ago, 9 messages
- harsh_account-requirements, 6 days ago, 16 messages
native needle
Hi there, there's no API to return the requirement summary.
plucky prism
thanks for confirming . Also, a question on information submitted with accounts API for an account we are trying to onboard if we are trying to create a external account for Australian bank account and submit account number and BSB (routing number) then for BSB validation issue it returns an error immediately on a external account api creation call from my previous discussion with a discord team member but for account number, when is it validated ? Is it validated when a payout is attempted to be made to a connected account ?
native needle
Hi! Can you share the request ID (req_xxx)? Here's how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
plucky prism
sure, for a BSB number issue this is a request -req_YSMO3sEgzpO91j , a team member previously confirmed that in production its same error without the link for test data for BSB , but not sure how will it behave in production Environment for account number and what error to expect and when ?
native needle
This request failed because the routing number isn't valid.
You need to use a valid routing number, in test mode or live mode.
plucky prism
sure thanks but my question is what will happen in production when routing number is valid but bank account number is invalid, does stripe validate this Information straightaway with the bank ? Or is it something we find out during payout when attempting to pay to connected account ?
native needle
No, Stripe doesn't validate the bank account number. If you are based in US, you can use finanacial connection to collect a bank account, and Stripe will validate the bank account during financial connection establishment https://docs.stripe.com/financial-connections/connect-payouts?locale=en-GB
plucky prism
sure, thanks for confirming so then what happens in a scenario where bank account information is entered wrongly due to user input error, I assume payout will fail with some specific error?
native needle
Yes you are right, the payout will fail
plucky prism
will there be a specific failure message you can suggest that we can rely on so that we can let end user know to correct this ?
else it may be block their payment and we hence have to inform this to them for them to correct this
native needle
You can listen to payout.updated event and check the payout object's failure_code to understand why the payout fails. More details in https://docs.stripe.com/payouts#payout-failures
plucky prism
perfect thanks for confirming
native needle
Happy to help!
plucky prism
A couple of more questions related to accounts API
1- Will the requirements property in account object https://docs.stripe.com/api/accounts/object#account_object-requirements have everything that can be found in individual capabilities in the account with capabilities API - https://docs.stripe.com/api/capabilities/object#capability_object-requirements?
2- What is the difference between future requirements https://docs.stripe.com/api/accounts/object#account_object-future_requirements for account API and collection requirements.eventually_due in accounts API https://docs.stripe.com/api/accounts/object#account_object-requirements-eventually_due
It says below
On the enforcement date for an account (future_requirements.current_deadline), the contents of the future_requirements hash move to the requirements hash and Stripe generates an account.updated event. Because this enforcement can cause more accounts to require review, use the enforcement date as a reminder to check the Accounts to review tab in your Connect Dashboard.
is the collection requirements.eventually_due in requirements object https://docs.stripe.com/api/accounts/object#account_object-requirements same as future requirements ? Just trying to understand what to expect so we can iterate through the required collections accordingly and show collection requirements to the end user
native needle
eventually_due contains requirements that are not due currently, but will be due in the future. This is different from the future_requirements hash.
And yes, the requirements hash will change if you request more capabilties on the account.
plucky prism
since eventually_due contains requirements that are not due currently, but will be due in the future then can you please give me an example of how is it different to future requirements. Its a bit confuing since both the collections have eventual_due , currently_due and past_due
"future_requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": null,
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": []
},
"requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [
"business_profile.mcc",
"business_profile.url",
"business_type",
"external_account",
"representative.first_name",
"representative.last_name",
"tos_acceptance.date",
"tos_acceptance.ip"
],
"disabled_reason": "requirements.past_due",
"errors": [],
"eventually_due": [
"business_profile.mcc",
"business_profile.url",
"business_type",
"external_account",
"representative.first_name",
"representative.last_name",
"tos_acceptance.date",
"tos_acceptance.ip"
],
"past_due": [
"business_profile.mcc",
"business_profile.url",
"business_type",
"external_account",
"representative.first_name",
"representative.last_name",
"tos_acceptance.date",
"tos_acceptance.ip"
],
"pending_verification": []
},
native needle
Sure, let me give you an example.
plucky prism
Since both collections have same name fields so not sure how to show and interpret them for the end user . Any more details that can help us understand this will be helpfull
native needle
let's say you have an account that have already provided all the information that the local regulation requires, so at this moment both requirements and future_requirements are empty.
Now, you decide to request more capabilities on this account, its requirements will contains currently_due for information that needs to be collected immediately and/or eventually_due for information that can be collected later.
A week later, the local government release a new law that requires all account to submit an additional doc by a certain date, and this new requirement will be reflected in the future_requirements hash.
plucky prism
oh okay got it but then since it is in future requirement hash and it has a field called currently_due having current_deadline and then if no values are provided by that date and then will it move to requirement hash - past due collection directly or will it move to requirement hash currently_due having current_deadline ? Will the deadlines be different while it is in future requirement hash vs requirement hash ?
native needle
Yes the deadlines are different
plucky prism
perfect thanks so future requirement hash is more proactive while user will still have time to submit it in requirement hash as well right?
native needle
Yes you are right. Also on the enforcement date for an account (future_requirements.current_deadline), the contents of the future_requirements hash move to the requirements hash and Stripe generates an account.updated event. https://docs.stripe.com/connect/handle-verification-updates#prepare-for-enforcement
plucky prism
perfect thanks
native needle
No problem!