#tomer_api

1 messages ¡ Page 1 of 1 (latest)

shy bridgeBOT
#

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

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

gray lynx
#

Hi there. Could you clarify what you meant by "test payments for themselves before actually onboarding them to stripe." ? Also, this account creation call (req_wHeqUnWEaYvVnf) is successful

velvet ivy
#

I am making a website generator, and want to allow users to create web stores. Before they actually onboard to stripe I want their account to be a test account but ideally they shouldn't have to go through any stripe link to create the account. I do want their websites to have an integration with stripe, just with a test account.
The request was successful but the account it created is restricted

gray lynx
#

Okay so I'm understanding that you want a working test connected account. In that case, there verifications that still needs to be "gone through" before the test account is activated.

We do provide test credentials to help our users test Stripe Connect: https://docs.stripe.com/connect/testing

You could consider using the test credentials we provide to create and activate a connected account in your sandbox environment. Using our test credentials means your customer/users does not have to onboard with their personal details

velvet ivy
#

I am using url: 'https://accessible.stripe.com'
line1: 'address_full_match',
phone: '0000000000', in the create account request.
But I seem to be missing ToS acceptance, card details, SSN/ITIN and maybe other info. I couldn't find a way to supply all of it in the create account api, is it possible without user interaction?

gray lynx
shy bridgeBOT
gray lynx
#

It should be possible to create and activate a test connected account without further interaction, by pre-supplying all the needed info for verification. For simplicity sake, you can go to the Stripe Dashboard's Workbench > Blueprint

Under Blueprint, there's an option to Create an account where you can get Stripe to create an enabled connected account for you. You can create one connected account using Blueprints, and then inspect and reference the body of the API request which created the enabled account, to create your own connected account

velvet ivy
#

okay, I'll try it

#

So from the workbench the automated connected account creation works, but the typescript sdk does not have all of the fields, is there a way to get the same thing using the sdk?

glad forum
#

but the typescript sdk does not have all of the fields, is there a way to get the same thing using the sdk?
No I don't think so honestly

#

Probably you can create the account with prefilled data, then you full the fields requested in currently_due and eventually_due

velvet ivy
#

So regarding the ToS, whenever I try to use either type: 'express' or

controller: {
      requirement_collection: "stripe",
      fees: {
        payer: "application",
      },
      losses: {
        payments: "application",
      },
      stripe_dashboard: {
        type: "express",
      }
    },

I get this error if I try to use the ToS acceptance: You cannot accept the Terms of Service on behalf of accounts where controller[requirement_collection]=stripe, which includes Standard and Express accounts.

I haven't tried to use the raw request like in the blueprint yet

#

And using requirement_collection: "application" means the user with the connected account will have a different experience because When controlling requirement collection, the Connect application must also control losses, fees, and specify a dashboard type of none.

glad forum
#

I get this error if I try to use the ToS acceptance: You cannot accept the Terms of Service on behalf of accounts where controller[requirement_collection]=stripe, which includes Standard and Express accounts.
Yeah true you can't do TOS acceptance with API

#

You'll need to use Stripe hosted onboarding

#

So yeah I think Blueprint is the only option here