#Aurétlse

1 messages · Page 1 of 1 (latest)

west lintelBOT
whole citrus
#

Since bubble.io controls your integration with Stripe, we don't know how their integration works. If the account onboarding link is not generated yet, you may pre-fill the account details using Update Account API: https://stripe.com/docs/api/accounts/update

If the account onboarding link is generated, then you won't be able to update the details

woeful flower
#

All the call are manual and we try to using stripe directly via the api connector

#

We dont want to send seller on this screen

stripe_ecran.png
whole citrus
#

You may pre-fill the connected account information in the Create Account API.

From https://stripe.com/docs/connect/standard-accounts#create-account:

If you’ve already collected information for your connected accounts, you can pre-fill that information on the account object for the user. Connect Onboarding won’t ask for the pre-filled information during account onboarding. The account holder confirms the pre-filled information before accepting the Connect service agreement. You can pre-fill any information on the account, including personal and business information, external account information, and more

#

@woeful flower

Hi, we are developing a platform for individual or professional with seller onboarding. In their personal account they have the possibility to add a credit card as their payment method to be able to buy a product if they want. We have already create a customer profile and save the customer ID (ex : cus_NphhozgOFiAgHX)
voici le call
POST
https://api.stripe.com/v1/checkout/sessions
Parameter : mode = setup
With the answer we send the user to the url so they can enter the card information. But when the process is finish and we come back on succes url the card does not appear in the account
Can you help me on this problem ?
Could you share the Checkout Session ID (cs_xxx)?

woeful flower
woeful flower
whole citrus
#

we don't have all the informations on the first onboarding and our customer want the onboading is stressless and very quick. We ask ourselves how to have the best onboarding flow without the stripe connect screen. When the customer is already in we send a demand to finish the stripe onboarding
Our first question is it possible to onboard someone on stripe with our screen or not ?
For Standard connect account, it's not possible to onboard with your own form. You can only onboard with your own UI on Custom connected account

#

cs_test_c1HQ4YumMvfRzycHTzlz6DmedB7MWZwafNve1MxafRqOX464SyOO2uDGIu
In https://dashboard.stripe.com/test/logs/req_C9tLaeKrwybKq4, customer field isn't set. Without setting customer field in the request, Stripe will create a new customer and attach the payment method to the new customer.

woeful flower
woeful flower
whole citrus
#

Ok we can switch to custom if necessary. The user can be able to sell without any onboarding screen on stripe?
What are the call flow to do this ?
You may refer to the Custom onboarding guide here: https://stripe.com/docs/connect/custom-accounts

For the verification handling via API, it can be found here: https://stripe.com/docs/connect/identity-verification-api

Please note that Custom connected account doesn't have Dashboard access and more integration work required. Here is the comparison between different connected account types: https://stripe.com/docs/connect/accounts

woeful flower
woeful flower
whole citrus
#

who is in charge of KYC on custom connected account ?
Stripe will perform KYC

woeful flower
#

ok so with this method (custom) we are not directed to connect onboarding ?

whole citrus
#

Custom connected account support both Stripe hosted onboarding OR collecting the verification data on your own and send them via API

#

You can use either one

woeful flower
#

is there a specific parameter to choose to collecting the verification data on our own application ? in wich call ?

#

Customer on our patform can accept your TOS also ?

whole citrus
#

Have you read the Custom onboarding guides I shared earlier? They list out the steps and the verification/API to make, as well as TOS

woeful flower
#

sorry i've just finish to read them. When the KYC is necessary (because of hight factor risk) stripe ask the user directly ? by email ?

#

and if the verify could not be realized by stripe, our customer (the platform owner)can update documents in their stripe account ?

whole citrus
#

With Custom connected account, user doesn't have Dashboard access, i.e. no access to their account. Custom connected account is for white-labelling.

When additional verification or document is required, Stripe will send the Webhook event to the platform and the platform should collect those information and submit to Stripe.

Custom connected account does not know the existence of Stripe, so every verification/documents will be collected and submitted by the platform. Stripe will not reach out to the Custom connected account directly.

#

There are a lot more engineering works with Custom connected account integration as everything will be handled by platform

woeful flower
#

ok i understand

#

Thank you for your help

whole citrus
#

No problem! Happy to help 😄

west lintelBOT
woeful flower
#

I try to create a account and i have this error message
Raw response for the API
Status code 400
{
"error": {
"message": "Connect platforms based in FR must create Custom accounts via account tokens. For documentation on account tokens, see https://stripe.com/docs/connect/account-tokens.",
"request_log_url": "https://dashboard.stripe.com/test/logs/req_3CuCxsEULYhkLR?t=1683274703",
"type": "invalid_request_error"
}
}

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

upper dragon
#

Sure, seems expected. Did you read the documentation link in the error response?

woeful flower