#Vish-Custom-Direct

1 messages · Page 1 of 1 (latest)

worthy nova
#

Hi there, yep, all those function the same with Standard.

cloud stone
#

Ok...can you explain any other changes that I might need to make to switch to Standard Accounts. My reasoning for Custom Accounts was that our clients are not tech friendly and they will find the Stripe platform very intimidating. We wanted them to administer their Stripe profile through our portal but the one thing that we cannot implement is Stripe Tax. That is why we are thinking of switching to Standard Accounts

cloud stone
#

Any insights?

worthy nova
#

Sorry, missed the follow up. Server is busy. Looking!

#

You mostly just need to onboard the accounts as Standard accounts via the onboarding flow.

#

There isn't much that needs to change unless you want to handover more control to your Connected Accounts

cloud stone
#

No worries. Thanks for the response. Regarding the onboarding flow, from what I have seen till now, it seems like they need to first create a Stripe account on their own and then come to our portal and connect it(This will be done through APIs). Am I correct in this understanding? In custom, they could just create the account using our portal.

worthy nova
#

It should be the same flow here for Custom or Standard. Either way you create the account as the platform, then you redirect the user to the Hosted Onboarding Flow.

#

It is up to you for how much info you provide up front about the Connected Account in order to pre-fill the Hosted Onboarding Form.

#

But the flow isn't different — you were still creating the Custom Account

cloud stone
#

This is the page with Standard Account

#

In this case, they have to have a Stripe account beforehand

#

Right?

worthy nova
#

Nope. If they enter an email associated with an account they alreaddy have then we will pre-fill info based on that account. Otherwise, we will create a new account with the email.

cloud stone
#

Got it thanks