#mebezac-testing-connect
ruby lily
Hey there, I actually just went through this recently in one of my test accounts. The easiest way I found to set it up was to create a new test Stripe account, and then use our OAuth approach for linking to my main test account.
As noted in this doc we don't recommend OAuth as being your production flow for adding accounts, but it's useful for testing purposes.
stable yew
so like make a new Stripe account with real details (bank account, DOB, etc.)?
ruby lily
Let me double check, I think you can enter test data for, or omit, a large portion of those fields.
stable yew
I get to this point
ruby lily
Apologies, you're right about that error. We do a little more validation on Standard accounts since they could become real accounts someday. I hit that error as well, let me backtrack through my notes and try to remember how I got around it.
stable yew
🙏 Thanks!
ruby lily
Sorry, that took longer than intended. So it's a bit of effort but below is the flow that I was able to use:
- Navigate to dashbaord.stripe.com and create a new account.
Use a valid:
email address
phone number
address
Provided fake:
DOB: 01/01/1901
SSN last 4: 5555 - Set up the OAuth flow for your primary test account
- Open an incognito window and log into the account created in step 1. Set an account name for this account while you're here.
- Still in that incognito window, navigate to the OAuth registration link created in step 2.
- Use the 'Skip this form' button (already being logged in changes this functionality a little)
- Catch the authorization code that is provided when you're redirected back to your
redirect_url - Use the authorization code to finish the linking mentioned in section 4 of this doc:
https://stripe.com/docs/connect/oauth-standard-accounts
Incognito windows will be a life-saver to keep you from constantly getting kicked out of your session while you bounce between accounts.