ektalem_api

[scenic orchid]

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

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

[warm basin]

👋 Hi there! Let me take a look

How are you creating these connected accounts? It is possible to specify some information in advance when using the Accounts API

And which form are you sending people to? How do you generate that URL?

[vocal root]

We use the Stripe Accounts API with the following configuration:

Pre-filled information

We currently pre-fill:

• business_profile: URL, MCC (7941), product description
• individual: first name, last name, date of birth, address, email, phone

This data is collected via a form on our platform before redirecting to Stripe.

3. How do you generate the onboarding URL?

We use the Account Links API:

const accountLink = await stripe.accountLinks.create({
  account: accountId,
  refresh_url: `${origin}/sell?refresh=true`,
  return_url: `${origin}/seller/onboarding-complete`,
  type: "account_onboarding",
});

// The user is then redirected to: accountLink.url

1. Can we use collection_options to reduce the number of fields requested?

   collection_options: {
     fields: 'eventually_due',
     future_requirements: 'omit',
   }
   

2. For French individuals selling occasionally (C2C marketplace), are there ways to simplify KYC requirements?

3. Is there a way to skip certain verification steps for low-volume sellers (< €2,000/year)?

[rustic birch]

Hey! Taking over for my colleague. Let me catch up.

You can see all the requirement for a given Connect account following this guide:
https://docs.stripe.com/connect/required-verification-information

You can't remove a required field, otherwise the Connected Account can't use their full capability (accpet payment, payouts...)

[vocal root]

There's no way to simplify the forms.

I don't understand how I can make the customer experience easier when creating an account to receive the money. They don't have a business; they're just individuals.

Is this working for marketplace like this ?

seller -> check for authenticity -> when approuved product is listed -> buyer -> we take fees -> we pay the seller

[rustic birch]

Yes, it's the same for all uses cases

There's no way to simplify the forms.
You can create a Custom Accounts and do the onboarding using your own UIs if you want

but at the end you need to provide all required informations by Stripe.

[rustic birch]

yes

[rustic birch]

This seems good flow yeah. Just the seller needs to have a verified Stripe Connected Account by providing at minimum the required information

[vocal root]

Thanks for confirming the flow works for our use case.
Quick question about optimizing the seller experience:
Since KYC is mandatory, we're thinking of implementing a deferred onboarding approach:

Seller lists their item (just email + name required)
Listing is visible but marked as "pending seller verification"
When a buyer wants to purchase → we notify the seller to complete Stripe onboarding
Once verified → sale is finalized

This way, sellers are more motivated to complete KYC when they have an actual buyer waiting.
Does this flow work with Stripe Connect? Any technical limitations we should be aware of?
Thanks!