#LukasBimba
mighty girder
Hi, it should be on the Account object id. You can retrieve the account. https://stripe.com/docs/api/accounts/retrieve and look at business_profile.
odd nexus
Yes I am capable to pull the accounts data with stripe.accounts.retrieve
mighty girder
If you're looking to update this for the Connected Account, you can use the update account API: https://stripe.com/docs/api/accounts/update#update_account-business_profile-support_address
odd nexus
yet I am curious as to where the data the user enters during on-boarding since it is not present when retrieving the account
Well I am looking to streamline my on-boarding process for my mobile app. When a user signs up with stripe I want to pull the info they provided to stripe to help aid in the completion of their account on my mobile app to help reduce time and pain walls
mighty girder
If the connected account provided these details, it should be under "business_profile". Can you confirm that this data is provided when creating the Connected account?
odd nexus
I have tested this multiple times and the data under "business_profile" which is "support_address", "support_email" all is null
This is a swift mobile app using Node.js with Firebase Functions
Does these connected account being test accounts create any barriers here?
Even when I went into the dashboard as the test account and added an email, it then appeared in "email" but not under "support_email"
I am curious to understand how a user would even go about adding "support" information?
My real problem I am looking to solve is having the ability to pull the data the user enters during on-boarding to then pass it to my app so the user doesn't have to repeat the information which takes more time and increases the chance of abandonment
Also, during the verification phase with connected account the "verifiying" at the end should be red and not the same color as the rest of the fields because even to my eye I just want to press the bright green "submit" which then causes the profile to be incomplete and causing the user to relog into stripe to complete the information which causes more pain walls
mighty girder
Can you share the request id where you see this behavior? Are you passing in tehse details via the API when creating these accounts?
odd burrowBOT
desert silo
👋 hopping in here since pgskc needs to head out
odd nexus
I can imagine since pgskc is responding to all the messages 😅
desert silo
Your issue just boils down to wondering how to even set support_email for a connected account? Do I have that right?
odd nexus
Thats a part because even with the "email" field before I went into the dashboard to add it it was null. Fields like "support_address" are null even though the user has to enter it during the on-boarding. So where is the data that the user entered during on-boarding?
desert silo
We only collect fields that are required during onboarding - for a lot of countries/areas support_address isn't strictly required so we may not collect it
If it's somethign you definitely want to collect/set, then you'd want to set it through the API
odd nexus
I am using Express accounts (test accounts) in the United States. I assume what you are implying is the I should go with Custom Connect Accounts? Becuase that will solve my question as to where the data the user enters is stored during on-boarding, like, the address?
desert silo
Even with Express accounts you can still set things like support_address through the API
odd nexus
Do you have a link on how I could achieve this? Again, why do I not have access to the credentials entered during on-boarding like the entered address?
Also, how would a user go in and add a "support_address"? From what I see on dashboard with my test accounts this is not visible
desert silo
For an express account at least there isn't a way for them to add a support address through the express dashboard - and I don't believe it's someting you can set on their behalf through the dashboard either
As for the credentials given during onboarding - can you give me an example account I can take a look at?
odd nexus
"acct_1NUoTQPuuXAubEKO"
desert silo
You're not geting back the address information that was set during onboarding is because it's tied to the person/individual, and we don't return individual for Express accounts through the API (you can see in the API ref that it says custom only https://stripe.com/docs/api/accounts/object#account_object-individual)
odd nexus
Understandable now