josh_unexpected

[violet arch]

👋 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/1346340197675040789

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[uncut whale]

hello! So whether the identity document is required can depend on a variety of factors - https://docs.stripe.com/connect/required-verification-information. It's not necessarily always required upfront. I think you'll want to do is to write in to Stripe Support - https://support.stripe.com/contact, and check in if it's possible for you to request to collect an identity document upfront for your connected account.

[covert dust]

Hey Alex, When I create the account I've set its type to "Standard", I'm going to try set it to "Express" instead as it mentions that it will handle identity verification, however the section on standard accounts does not: https://docs.stripe.com/connect/accounts

[uncut whale]

For Standard accounts, requirement collection is done by Stripe

[covert dust]

I don't nessessarily need the identity documentation upfront, I just need the embedded onbording component to allow and alert the user they need to verify their identity, at the moment it is doing neither

[covert dust]

That's what I thought too, I must be missing some parameter when creating the account

I'd like to keep all the onboarding done on the platform I'm building, limiting the amount of times the user needs to go outside of the platform, at the moment a user would need to login to the stripe account they created via the embedded onboarding component and go into thier stripe settings and upload the documents that way

[uncut whale]

okay, maybe let's take a step back, it sounds like you do want Stripe to be responsible for collecting the necessary information. Now, Stripe will also notify the connected accounts in these cases. If there are additional requirements, the Standard connected account would do it via their own Dashboard.

Is there a reason why you are concerned about the verification updates from a Standard account in this case?

[covert dust]

Yeah I'd like stripe to handle all of the requirement collection to limit my KYC requirements. That makes a lot more sense as to why it isn't showing up on the embedded component.

Does the Express account type also collect identity requirements in the same manner as a Standard account?

[uncut whale]

yep, it's the same as a Standard account

[covert dust]

Okay and with an express account, I understand the platform is liable for refunds and disputes, does this also mean the platform is also liable for negative balances?

[gloomy roost]

Hi! I'm taking over and just catching up!

[covert dust]

No worries

[gloomy roost]

Okay and with an express account, I understand the platform is liable for refunds and disputes, does this also mean the platform is also liable for negative balances?

The platform is liable for refunds and disputes as long as destination charge / separate charges and transfers are being used to create a charge. The platform is definitely liable for negative balances of an Express connected account.

[covert dust]

Okay no worries. I'm attempting to create a seamless for platform users. I'd like to limit the amount of stripe branding as much as possible and keep as much of the onboarding and other stripe features within the platform using embedded components if possible, however also offloading as much of the liabity as possible to stripe. What it looks like at the moment is that a standard account is not really what I'm looking for, while it handles a lot of the liability, it takes the user out of the platform in order to perform identity verification, etc.

An express account still collects requirements and identiy verification outside of the application however it is more seamless such that it will redirect the user back to the platform, the downside is that all of the liability is now on the platform

is that understanding correct?