#karen_code
idle yarrowBOT
đ 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/1276129531794817115
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
graceful rose
hi! what's the request ID req_xxx of a working example?
finite bane
I'll search it for you. Give me one minute.
graceful rose
to me anyway I'm surprised this works, Connect and Identity are different products. For Connect you're supposed to just collect the document scan yourself, call the FileUpload endpoint, and then pass that file ID, and then Connect does the verification.(or really, you're supposed to use our hosted onboarding or embedded components and they do it, and those components internally use Identity)
You could probably still do the same thing; i..e download that raw image from Identity(if you can), then re-upload it with the FileUpload API and use that ID.
maybe one of your accounts is in the beta for https://docs.stripe.com/connect/additional-verifications and the other isn't.
finite bane
So, In short, we shouldnt try to upload files generated by Stripe Identity directly to the connected account?
graceful rose
it doesn't sound like a flow I've heard of us documenting but Stripe has many different products and ways to integrate(and there's that beta feature linked above too) so maybe it's just something I'm not aware of and you have more context on where you heard about doing this
finite bane
Alright, thank you so much for your help!