#jakel-fr-custom-connect-account-onboarding

1 messages ยท Page 1 of 1 (latest)

runic brook
#

Hello ๐Ÿ‘‹
Give me a moment to look into it

tame wagon
#

thank you

runic brook
#

Thanks for your patience
Unfortunately, account tokens are not handled automatically.

tame wagon
#

Ah got it. Can you please provide some additional information on how we should incorporate the account_tokens?

runic brook
tame wagon
#

So to clarify, we cannot use the Stripe Hosted Onboarding form to onboard custom connected accounts to a FR Platform?

runic brook
tame wagon
#

Yes - we currently use this in order to onboard our connected accounts to our US Platform

runic brook
#

Great. so once you create an account using the token, you can create account links and send it to your users in FR for onboarding

tame wagon
#

Ah very cool!

#

So rather than just immediately sending the user to the Stripe Hosted Onboarding form, we will need to create a form that collects specific information, and then pass that to Stripe to get a token, and then once we have the token, we can send the user to the Stripe Hosted form using the account_links API?

runic brook
#

yup
due to regulations

French platforms must use account tokens, which are an alternative to the agent model for platform PSD2 compliance. The key benefit of tokens for French platforms is that information is transferred from the user directly to Stripe. Not having to store PII data is still a benefit, but not necessarily a requirement. For platforms in other countries, account tokens are optional but recommended.

tame wagon
#

got it - where am I able to find the information we need to collect? does this vary by country?

runic brook
tame wagon
#

Ok got it.

#

And if not, what are the necessary fields that must be sent in that account token api?

runic brook
#

I'm not super familiar with what information we gather while onboarding vs when an account token is created
Let me scout the docs and see what I can find

tame wagon
#

thank you very much.

Our goal is to collect only the smallest amount of info from the user needed to generate the account token and then direct the user to the hosted onboarding form to collect the remainder

runic brook
#

apologies for the delay
Juggling between multiple threads

#

still looking

tame wagon
#

no worries, thanks!

runic brook
#

it says that while creating an Account Token you need to include everything that's required for that user's country

tame wagon
#

so why would we need to send the user to the stripe hosted onboarding form if we need to collect everything up front oursleves?

lofty halo
#

๐Ÿ‘‹

#

I'm hopping in - just give me a minute

tame wagon
#

thanks !

lofty halo
#

I believe you wouldn't necessarily have to collect everything - you could just collect the minimum amount of information and then redirect them to the account link for the rest

#

But I'd try this whole flow out and see if it works - I'm not the most familiar with the french regulations (which is why we need account tokens)

tame wagon
#

Do you know where we can find the min requirements?

dense yew
tame wagon
#

right, that looks like a lot of information to collect upfront though before sending them to the stripe hosted form.

For example what if just send the business_type and tos_shown_and_accepted fields in the account token api? Would that be sufficient enough to return the account_token and bring the user to the hosted form?

young abyss
#

I don't think you even need those 2 to send them to the form

tame wagon
#

oh even better

#

so maybe just an account name and email?

young abyss
#

Have you tried giving nothing over than the country and then creating an Account Link?

tame wagon
young abyss
#

I don't think you need an account token for the country. Account tokens are for collecting PIIs client-side because France has different regulations

#

your plan is to not do that, you get an account with just a country and then you send them to Stripe and we collect everything safely client-side, meeting regulations

tame wagon
#

But we receive this error when attempting to send the user to the hosted onboarding form. It sounds like we need to use account_tokens since we have a FR Platform

young abyss
#

ah so try the account token with just those 3 params

tame wagon
#

okay, thank you

young abyss
#

I'm sorry I thought country was allowed server-side, I'm surprised it's not, but we likely just blocked everything to make it easier to detect