#harsh_account-requirements
blazing stormBOT
👋 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/1281383465559916594
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
analog fractal
@digital sphinx I would recommend reading https://docs.stripe.com/connect/required-verification-information carefully
Overall Test mode and Live mode work similarly. If everything is provided then nothing else will be asked, otherwise it'd show something in eventually_due
harsh_account-requirements
digital sphinx
Will it be shown in eventually_due straight away or after Stripe reviews/validates the account information ?
analog fractal
straight away
digital sphinx
Greats thanks for confirming 😃 Also can you please help with few more questions on account api if we use the connected account for giving payouts to the accounts then what capabilities do we need to request for account ?
Our customers use card payments and we then pay to connected via bank transfer, do we need both these capabilities or just transfer ?
"capabilities"": {
""card_payments"": ""active"",
""transfers"": ""active""
}
analog fractal
It depends who is the "settlement merchant" or "merchant of record".
digital sphinx
thanks will check this and get back for any further questions .
I came across few more properties in accounts api get call and have few questions
- requirements.disabled_reason
If for example with an account if Stripe finds issue with verifications etc then will it always show up as a reason here along with eventual_due on what's needed ?
For example its a fraudulent account or with incomplete verifications etc then will we know the reason along with any pending requirements ?
- charges_enabledboolean
Can you please explain what does this value indicate ?
analog fractal
for disabled_reason it's documented in details here: https://docs.stripe.com/connect/handling-api-verification#determine-if-verification-is-needed
For charges_enabled it's also mentioned there but it's basically an easy way to know if this account can even accept payments or if it's currently blocked (either because of a rejection or more information needed)
digital sphinx
thanks 😃 One final question for now
If we are submitting incorrect data by mistake lets say bad user input for BSB number(routing number) field for Australian bank accounts . In test account we are restricted with what we can pass as data and get error as per found in request id - req_YSMO3sEgzpO91j which indicates to use testing data from link
"message": "The routing number 123243 does not correspond with a recognized bank. A valid routing number is required in test mode. Consider using a test number from https://stripe.com/docs/connect/testing#account-numbers",
But in production what sort of an error can we expect as we are planning to identify this specific error and show routing number error to user in our system and need to know if there will be any specific error code thrown for invalid BSB , will it be an error from https://docs.stripe.com/error-codes and if yes is there any specific error we can look into as it has multiple error codes that are related to account ?
analog fractal
the error would be the same, just no mention of the test doc. You'd get the same error shape and see the same param: "external_account[routing_number]" telling you the value in that parameter is invalid
digital sphinx
perfect thanks for your help .
But is there any conditions in which these error codes are returned https://docs.stripe.com/error-codes ?
analog fractal
Those error codes happen for specific errors. So there are a lot of reasons you could get those, depends on what you are doing, which API(s) you use, etc. But there's no error code for that specific error you mentioned