#five-point-palm_api
gleaming horizonBOT
đ 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/1433932963766075564
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
long dagger
Hi there!
long dagger
Let me dig into this a bit
this might be related to the order of operations - we say in a couple of places things like
A platform cannot access a person for an account where account.controller.requirement_collection is stripe, which includes Standard and Express accounts, after creating an Account Link or Account Session to start Connect onboarding.
and the account link is created a couple of minutes before the person
timber kite
I am definitely creating the person before the account link
although these things happen in rapid succession
I think I gave the wrong request ID
req_ZcrkcXs9LRafz1
long dagger
Seems like probably, yes
let me look at that one. I've been testing this but unfortunately testing account onboarding is slow
Okay, got it to work
It is either that you need to pass relationship.representative.true when creating the Person to get the information you've put on the person to be prefilled, or updating the account with company.owners_provided / company.directors_provided. Let me run through that again and see which
I think its the former based on the entry for relationship.representative in the API reference
Yes, that's correct
so when you create the person, as in this request, you want to pass representative: true in the relationship parameter
timber kite
ahhh thank you!