#vova-connect

1 messages · Page 1 of 1 (latest)

vagrant acorn
#

Hi, let's continue in this thread

#

Could you summarize your question?

hazy zodiac
#

Is it possible to implement Stripe Connect for Standard accounts without Connect Onboarding?

#

If yes, then I am confused why someone has recommended me to use Stripe Connect Custom if I need to get rid of Onboarding.
(I collect user bank info in my app, there is a separate tab in User Settings interface)

vagrant acorn
#

Yes there is the OAuth flow which is more legacy than Connect Onboarding, for standard account. Why don't you want the Connect Onbaording btw?

hazy zodiac
#

what is "OAuth flow"?

#

"Why don't you want the Connect Onboarding btw" I want to have a frictionless experience for users, that's a competitive advantage of the platform I am building

vagrant acorn
#

Okie, and you need to use Standard, not Custom?

#

I am asking because Custom indeed doesn't require an Onboarding flow which seems to fit your case, and maybe is the reason someone has told you

hazy zodiac
#

I still struggle to understand how Custom work, that's why asked about Standard. I just have a marketplace and I want my users to get paid with Stripe. With Standard accounts, they just should create their own Stripe account and connect to my marketplace via Standard Connect onboarding.

#

With Custom I would need to prevent users from having a Stripe account? I create Stripe accounts for my users?

#

I had a hypothesis that Stripe Custom has too many features that I don't really need

#

What can you recommend?

vagrant acorn
vagrant acorn
#

Did you read them and still confuse?

hazy zodiac
#

yes yes

#

I integrated Stripe Connect for Standard accounts with Connect onboarding in the past

#

I do have experience with that

vagrant acorn
#

But did you know the different between Custom vs Standard vs Express per the Doc above?

#

With Custom I would need to prevent users from having a Stripe account? I create Stripe accounts for my users?
it should answer this. Basically yes you create and manage account for them

#

A Custom Stripe account is almost completely invisible to the account holder. You—the platform—are responsible for all interactions with your user, including collecting any information Stripe needs.

hazy zodiac
#

@vagrant acorn Also, I have a very important question. I was listening to a podcast yesterday and a guest told me that Stripe rejected them on one of their projects. I remember he was talking about Stripe Custom. The rejection that he mentioned, he said it was strict and that wasn't able to continue using Stripe for that project anymore. Do you know what is that verification and how is it related to Stripe Custom?

vagrant acorn
#

That decision varies on business purpose, the person who is registering. Our Support team is in charge of that process and it's really case by case. We are a Payment Processor and being regulated by law/regulations from countries around the world.

#

In this Discord server we are developers and don't know much about the verification process, sorry. We are happy to help in technical perspective

#

Going back to Standard vs Custom. Yes Custom requires more effort but it doesn't require an Onboarding flow. Standard always requires either an Onboarding flow or an OAuth flow, both has some screens hosted by Stripe. We do our best to make it as frictionless as possible, but we still need to collect certain information, because of law/regulations etc...

#

The thing with Custom is, while it doesn't require Onboarding flow, it will requires you to collect the necessary information instead, and supply to some Stripe API.

#

You can think that there are certain information needed to be collected anyway. Either you choose to let us do (Onboarding flow) or do it yourself (Custom)

#

Sorry that's long. Hope it makes sense!

hazy zodiac
#

"Custom requires more effort" - why?

vagrant acorn
#

Right here!

hazy zodiac
#

Do you have any great use cases where is was a good idea to use Custom instead of Custom?

#

Am I right that with Custom accounts, I just need to cover connect onboarding using simple API requests? Like I just would have a few simple API calls where in body JSON I provide a few important fields/parameters?

vagrant acorn
vagrant acorn
#

Hi, I am stepping down for the day. If you have further question, feel free to ask in the channel!

violet relicBOT
#

This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact

hazy zodiac
#

Platform verification and review are made only on Custom Stripe accounts, right? We can be rejected by Stripe only when trying to use Custom accounts? Express and Standard accounts don't have it, right?

sonic ridge
#

Hi there! Platforms don't have to collect verification information for Express and Standard accounts. Stripe handles verification for Express and Standard accounts

#

Similar to Custom accounts, Express and Standard accounts can be rejected

hazy zodiac
#

Is there any difference between being rejected on Express versus on Custom?

#

As I understand Custom offers exclusive API and you can only use it if you passes the Stripe review

#

It seems that Express offers API from day 1

#

Am I wrong?

#

Requirements for Express accounts are bigger?

sonic ridge
#

I'm not sure I follow. What do you mean by "exclusive API"?

#

All accounts regardless of account type must complete onboarding requirements

hazy zodiac
#

Can you explain how to handle "Fraud and dispute liability" as a Platform on an Express account?

#

Also, is that possible to make payouts when certain triggers occur on the Stripe Standard account? For example, my user claims that the finished the service that he had to do for the client (by tapping a button, request escrow)

sonic ridge
hazy zodiac
#

how about standard accounts?

sonic ridge