#-mark-simpson-_api

1 messages · Page 1 of 1 (latest)

nocturne turretBOT
#

👋 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/1346569335937958019

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

sacred parcel
#

As a related question: will the account.updated event be fired when a connected account has new or unmet requirements?

true urchin
#

Which part is not human readable exactly?

sacred parcel
#

For example for one account the requirements member is: "requirements": {"alternatives":[],"current_deadline":null,"currently_due":["business_profile.url","tos_acceptance.date","tos_acceptance.ip"],"disabled_reason":"requirements.past_due","errors":[],"eventually_due":["business_profile.url","individual.id_number","tos_acceptance.date","tos_acceptance.ip"],"past_due":["business_profile.url","tos_acceptance.date","tos_acceptance.ip"],"pending_verification":[]}, Note that errors is []. I can see that currently due are business_profiel.url, tos_acceptance.date, tos_acceptance.ip.

#

the documentation i was looking at led me to believe that errors woul have some information with a reason that seems to be human readable... but here i have none.

#

For an account in test mode - i do see an errors with human readable reason. But in my live-mode accounts i am looking at i don't see any errors with value other than []

#

Another example is an other account with "currently_due":["interv_1QXoRFAL6g6NLf5j1CQE8SZS.url_inquiry.form"] in the requirements, again with no details in errors. Is there a way for me to translate that requirement into something to show to a human?

#

I am looking into these things because we want to help our clients with connected accounts to ensure they have their accounts set up properly. While they are getting notifications from Stripe about their accounts we think that by having some information about the status of their on-boarding ourselves we may be able to assist them complete the needed steps.

true urchin
#

Can you share the examples you're referring to here both in test and live mode so I can further look?

sacred parcel
#

For the item above with the interv_ requirement the account id is "acct_1QXnc5AL6g6NLf5j" (live-mode) and for test-mode "acct_1Qr4LqEfazvJxstg" (note that this example i have in test mode actually does show some data in errors)

#

Do you need to know other info like my stripe api key or similar?

true urchin
#

No, you should not share your secret api keys ever

#

Can you share the specefic event ids with me?

sacred parcel
#

Sorry if i my add-on event question is causing confusion. The primary question is about data i am seeing when i call Stripe::Account.retrieve with the account id of a connected account

true urchin
#

We don't log responses on GET calls so I can look at that on my end. We document what these requirements mean here: https://docs.stripe.com/connect/required-verification-information

I have not personally seen something like '"currently_due":["interv_1QXoRFAL6g6NLf5j1CQE8SZS.url_inquiry.form"]' before. Can you share the response on thid GET call?

sacred parcel
#

this is the data i get from Stripe::Account.retrieve("acct_1QXnc5AL6g6NLf5j") where you can see the interv_... requirement in currently_due

📎 response.txt
true urchin
#

Taking a further look