#jean-baptiste-r_unexpected

1 messages ยท Page 1 of 1 (latest)

zinc boneBOT
#

๐Ÿ‘‹ 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/1365327962991231108

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

rough spade
#

Some information is not immediately required and can be provided later. Uner certain conditions this can become required.

#

How are you creating/onboarding accounts?

reef basalt
#

I create connected accounts when users create their account on our website
Then, they can access to their stripe information on their profile
But for some users, we need to do transfers to them, so we need them to give you required information like their IDs, bank account etc

rough spade
#

Sure i mean, are you using the /accounts API to create accounts, and account links to generate URLs to redirect them to for collecting info? Or something else?

reef basalt
#

Yes that's it

zinc boneBOT
reef basalt
#

I can provide you some code if you need something

vestal relic
#

Hello there

reef basalt
#

Hey, welcome

vestal relic
#

Stepping in as synthrider needs to step away

reef basalt
#

Alright thank you, wish him a great day ๐Ÿ™‚

vestal relic
reef basalt
#

Here is:

collection_options: {
  fields: 'eventually_due',
  future_requirements: 'include',
}
vestal relic
#

Okay can you provide me an Account ID as an example where information was not collected?

reef basalt
#

Euh, can recreate an account yes

vestal relic
#

Yeah would need to look at an example since if you are passing eventually_due and include then all fields should be collected.

#

To be clear, that doesn't necessarily mean all fields will be verified -- as some verification happens async.

#

Not sure if that is what you are referring to here or if you are literally saying information was not collected.

reef basalt
#

I'm not sure we understand each other :x

vestal relic
#

Feel free to provide more details, but an example would be best.

reef basalt
#

I'm gonna do this and provide you screenshots

#

Okay let's go !

So I'm gonna use an account with this stripe id: acct_1OhSpeCBAcAOFpN1 in my test env
I go to my profile on our website (sorry, it's french but I'll try to be as understandable as I can)
I click on the blue button to get redirected to my stripe account update page

#

Such a beautiful page, but I see there's missing information (red things)

#

In these information, we can see that Stripe misses personnal information (IDs, date of birth etc) and bank account.

vestal relic
#

That account never went through hosted onboarding though.

reef basalt
#

That's true

vestal relic
#

It looks like you are using Embedded Components here?

reef basalt
vestal relic
#

Where you see the missing information (the info for the Connected Account).

#

There is of course going to be info missing if the user doesn't go through onboarding yet.

reef basalt
#

Yes it's not a problem

#

My problem is that users can click on "Confirmer" (the blue button down the page) without providing missing information

#

And some users don't see these red things, so they just click on confirm then come to us saying "We did everything and it doesn't work"

vestal relic
#

Try that and I believe it will require that information to be input and the user won't be able to continue otherwise

reef basalt
#

Wait, I guess there's something I don't understand
What's the difference between account_update and account_onboarding ?
I though account_onboarding was used to create a Stripe account (and in our case, the stripe account already exists but has empty data) and account_update was used to update an existing account (so this is our casse)

vestal relic
#

No there are two steps here

#

Step 1 is you create the Account with whatever data you have already collected from the user ahead of time

#

Step 2 is you send them through onboarding which is when you create the Account Link with type: 'account_onboarding'

#

If you weren't to collect everything up front then in the future other requirements might arise for a user. Then, you could create another Account Link but with type: 'account_update' to collect newly due requirements from your users.

reef basalt
#

Mh ๐Ÿค”
If I'm right, account_onboarding should be processed right after user's registration then ?
Or maybe it could fit with our process

vestal relic
#

Yes it should be immediately after you create the Connected Account

reef basalt
#

Well, so I can't use account_onboarding then
As I told you, this happens after the registration process
We're trying to simplify the account creation process... and here I'd have to add an extra step.
What if I just generate only account_onboarding links instead of account_update links ?

vestal relic
#

That's what I'm saying...

reef basalt
#

Oh

vestal relic
#

You should change from using account_update to account_onboarding

#

There is no reason to be using account_update before you have onboarded the account

reef basalt
#

Oh well, I see
Thank you for your help then ! ๐Ÿ™‚

vestal relic
#

Sure!

reef basalt
#

Have a great day