#Reed - Test account
1 messages · Page 1 of 1 (latest)
Is this test account a test platform or a test user that you are connecting to the platform?
You should be able to create multiple accounts for an email, the dashboard will basically let you chose between them when logged in. Have you checked the dropdown in the upper left of your dashboard to see if the accounts you are created are being added there?
They are appearing there, the problem is with the onboarding link flow
When I enter the email address into the onboarding flow it asks for my password, and if I enter a new one it tells me to reset
When I do the password reset it logs me into the dashboard from that account
What I want is to run through the onboarding flow as a new account
Whenever I start the flow, it creates a stub with an acct_{id} account name in the connected accounts table on my testing dashboard
I've even tried one of our other testing emails, and it's doing the same thing
So the key problem is that it asks for a password, and expects a correct one, instead of running me through creating a new account
👋 stepping in as Pompey had to step away.
What type of Connected account are you attempting to create?
A standard account
I'm using stripe.accountLinks.create({
type: 'account_onboarding',
account: await stripe.account.create({
type: 'standard'
}).then(({id}) => id)
})
This has worked fine until I cleared all of my testing data, and tried to use our testing email for a fresh onboarding flow
It's creating the account under the Connect(test) dashboard, and providing a setup/s/acct_{id} redirect url
But when I put in our testing email it expects the password for an existing account
That shouldn't be an issue though? We associate accounts with the same email together and we pre-fill onboarding information based on other accounts that person has to make it easier. So this is all expected
It will still create a new account
If you want a completely fresh onboarding then you need a different email
What you can do is use test+1@gmail.com instead of test@gmail.com
That will still use the "same" email (in terms of where emails are sent) but we will see it as a new one
Oh, that's very interesting, thank you!
What I found confusing is that it was behaving for an existing account, since the testing email has only ever been used for this connect integration,
I thought that deleting all of the test data would clear that out and give a fresh onboarding experience
I'm still also having the issue where it won't clear the test data for those account stubs that were created during this process
It says I don't have any test data
Is there a significant period after the creation of some test data (like a connect account) before it will be recognized by the deletion feature?
I assume you are trying to clear out the test data via your platform?