mathieupi42_code

[clear patio]

👋 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/1479032751213776966

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[keen dirge]

👋
You can check the required information by Stripe following this guide:
https://docs.stripe.com/connect/required-verification-information

[river gust]

Thanks. How should I adapt the payload we send to make sure only individual information is requested and not company information?

[keen dirge]

No you can't send just some information, you need to send all the required informations by Stripe

[river gust]

Even company information when my final user is a third party individual (with no company then)? They do not understand why they need to fill in business information while they are just individuals... it is very disturbing in my account creation process.

[keen dirge]

I agree on this, but even if they are individuals they need to have a structure in order to receive payout

for example auto-entrepreneur

[river gust]

My users are here only to sell their bib for running events so it is a bit of a non-sense, they have no structure. I am very surprised that there are no means to adapt this part?

[keen dirge]

Yeah I understand this, but the customer who is selling goods and willing to receive funds/money they need to provide all the required information.

[river gust]

Do you think it will evolve in the future coz it is a big pain point for me and I guess I am not the only one in that case? Any recommendation to make my users understand the situation?

[celest axle]

Specifically what field(s) are problematic here? As stated, these are onboarding requirements for all users which are required for KYC/regulatory reasons. The requirements vary per country, but unfortunately are non-neogtiable – if not provided then the account(s) will never be able to accept payments

[river gust]

The 2 attached sections are problematic. They are filled in by default with my company information but my final users do not understand why they see this and what they need to do

[celest axle]

Sorry I don't read/speak French

[river gust]

Type d'entreprise = Company type, Informations professionnelles = Business information

[celest axle]

Yep, they're required I'm afraid as per the link my colleague shared. In any case, this is not an integration/code question – there's no way around this requirement outside of building your own custom onboarding flow which we generally do not recommend

[river gust]

ok I understand. It's really a pity as the process is very efficient otherwise!

[celest axle]

This is what I'm referring to: https://docs.stripe.com/connect/api-onboarding

Way more overhead for you to manage, but you'd be able to 'hide' those fields from the end user and jsut send the stock details you're pre-filling

[river gust]

Interesting. Why you do not generally recommend this API onboarding process?

[celest axle]

The top section on that page generally covers it:

With API onboarding, your custom flow must meet all legal and regulatory requirements in the regions where you do business. You must also commit resources to track changes to those requirements and collect updated information on an ongoing basis, at least once every six months. If you want to implement a customised onboarding flow, Stripe strongly recommends that you use embedded onboarding.

[river gust]

many thanks for your help in any case. I will discuss with my colleagues and see if this API onboarding is a good option for us ot not