#srgt-slinky_code
sour lotusBOT
👋 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/1286319447010705481
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
halcyon skiff
Or maybe with account links? https://docs.stripe.com/api/account_links/create
I was chatting about that with ChatGPT and it just made up that you can pass in a Person ID :lol: But that got me thinking if it might know about a beta / private feature …
These were the docs I've looked at: https://docs.stripe.com/connect/supported-embedded-components/account-onboarding
tropic snow
Hello
I don't really understand what you mean here.
Can you explain more about what you are trying to accomplish?
halcyon skiff
Ah, sorry
A common "problem" when onboarding connected accounts of larger companies is that there is rarely a person that can provide all the information
e.g. the Finance guy setting up the account, can provide details about the CTO / CEO
I was wondering if there is a way to tell the embedded component to only collect information for a specific person
If that was possible, we could implement a logic that allows to send out personalized links to each individual that has to provide their details
We could build that out on our own with the Persons API, but that would require more engineering resources
as suggested here: https://docs.stripe.com/connect/handling-api-verification#person-information
I hope that makes more sense now 😅
tropic snow
Ah no you can't control that part of the flow at all