#milan_api
dawn crystalBOT
đź‘‹ 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. Thank you for your patience!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.
đź”— 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/1214655299458306138
đź“ť Have more to share? You can add more detail below, including code, screenshots, videos, etc.
placid shaleBOT
celest rapids
Hello. Also - I used to be able to post a question directly in dev-help. Did something change?
warm mist
Hello! To clarify, this is for Custom accounts and you're trying to provide the bank account information directly via the API?
celest rapids
Yes. And it works great for US, but I'm struggling with Canada.
warm mist
Also, yep, we have a new question asking flow that starts in #help now and uses forms like the one you just used.
celest rapids
I see. I think the confusion I had was that the .NET library doesn't support this by default. I'll have to manually create the JSON payload which is fine. At least I have the answer.
warm mist
Ah, gotcha. I don't think you'll need to create the JSON manually though.
Instead you need to know how to combine the transit and institution numbers to make a routing number, which the .NET library should support.
This part, specifically.
placid shaleBOT
celest rapids
That works great. So in the onboarding flow for Canada, it looks like the user will have to go through an extra verification step where they validate their information on Stripe's onboarding form even though we are doing custom onboarding.
Is there a way around that so we can do the full verification ourselves?
frail mural
👋 give me a second to catch up here 🙂
So in the onboarding flow for Canada, it looks like the user will have to go through an extra verification step where they validate their information on Stripe's onboarding form even though we are doing custom onboarding.
What part of the onboarding flow are you referring to here?
celest rapids
I created a Canadian account and in the Stripe dashboard, it required more information. I clicked a button to generate a link which is to be sent to the merchant for identity verification. I can do another and send a screenshot if that's helpful.
frail mural
Yeah please share a screenshot
celest rapids
frail mural
As far as I know with custom accounts, you can perform verification using just the APIs
https://docs.stripe.com/connect/handling-api-verification
For identity verification: https://docs.stripe.com/connect/handling-api-verification#handle-identity-verification
Ah hmm, let me see if there's a specific callout for liveness verification
Individuals that Stripe can’t verify must provide proof of liveness, which entails taking a selfie and uploading an ID document using Stripe Identity. Your platform needs to integrate with Connect Onboarding to allow such individuals to complete this requirement.
Alternatively, your platform can collect scans of an individual’s ID and address documents and upload them to Stripe. After uploading, submit the individual’s ID document with the individual.verification.document.front and individual.verification.document.back arguments and the address document with the individual.verification.additional_document.front and individual.verification.additional_document.back arguments.
So if you don't want to integrate connect onboarding, you could collect other docs and send those instead
celest rapids
Ah ok. So if I collect the docs and send via API that should make the errors go away?
frail mural
I believe so, yes
celest rapids
That's a crude way of stating it from my side, of course. I'm just trying to understand the flow.
Ok. Thank you. I'll give it a go.