#att89-connect-custom

1 messages · Page 1 of 1 (latest)

alpine torrent
#

@royal glacier do you have a bit more context about what you do? You mention VerificationSession but that's related to Identity as a product which is entirely from Connect

royal glacier
#

I am trying to create connected stripe accounts for customers on our platform because of payouts. Therefore i would use the custom mode to be able to handle account creations on our platform via the stripe connect API.

alpine torrent
#

sure but that has nothing to do with VerificationSession

royal glacier
#

I have read this documentation, but obviously i am missing/forgot something. I try to explain the situation more precisely: After a user creates an account on our platform, a custom account (for an individual, not a company) will be automatically created in the back-end. Now the created account needs a bunch of information before it can be activated for payouts. So we proof the requirements stripe needs for the account depending on the country and request the user to fill the required fields with data (for example: birthday, external account, address etc.). After this step there are two last requirements needed (in the country, we do the testing): individual.verification.document an individual.verification.additional_document. And this is the point, where I actually can't go on. According to the stripe docs, i thought:

  1. I must create a VerificationSession on the server-side and send the secret to the client.
  2. On the client-side the user can open up a verification modal and safe upload the 2 documents needed for the verification.
  3. then, if the verification succeeds, the account requirements should be empty and the account ready to use.
alpine torrent
alpine torrent
#

@royal glacier did that make sense?

royal glacier
#

Thank you for your response. The process of collecting information for the account is already implemented on our platform and combined with Stripe's custom account creation flow. The only two things I am missing right now are the documents for verification. I thought I could handle this with a VerificationSession, but now I realize: that won't work. I will instead try to do the document upload from our platform itself (as per https://stripe.com/docs/connect/identity-verification-api)

alpine torrent
#

yeah don't use Identity for this, it's a completely separate product

#

I strongly encourage you to just move to Connect Onboarding though

royal glacier
#

Thank you, i appreciate your advice a lot and if it's up to me, i would immediately use the Connect Onboarding, because it saves a whole lot of time and nerves. But i must first discuss this with my team mates. Thank you very much for your help and have a nice time!

alpine torrent
#

sure thing, glad you're unblocked 🙂

austere bloom