#moonboots - test mode 2fa
kind path
Hey there, can you explain more about what you mean here?
Oh, onboarding. In test mode you would use the test phone number and test 2FA code, a real code shouldn't be necessary.
There is a shortcut button for this
golden crown
Oh wait, in Connect, in test mode you should have the test phone number button.
If you don't, you may be in production mode !
hard cave
Hey thank you. We have an online platform fully integrated with stripe. We use connect onboarding. We are giving all of our beta users our test log in and password to make the stripe portion of set up seamless. In that process users are prompted to enter in the Text Code that goes directly to my phone. I would love to disable the 2FA requirement for this
golden crown
Are you using the Standard flow or the Express one ?
hard cave
golden crown
Just use this button 😉
hard cave
yes, when I do it presents an issue in our platform.
golden crown
May I ask you to share the issue ? 😄
kind path
@hard cave That's using Standard accounts, which does currently use a real phone number when going through the flwo for 2FA. But yes, to skip the flow entirely you should use that skip button to simluate the onboarding process being completed.
hard cave
Ok our Dev says we are using express
kind path
Can you share an example test connected account id that you've created?
golden crown
Ok our Dev says we are using express
May you verify that your queries to Stripe API contains type: express ? You are currently using Standard flow...
hard cave
Ok I am relaying all of this in real time thank you for the help one sec while he verifies.
Also yes I can send an account. One that is successfully connected by authenticating with the test account and its 2FA I am assuming,
kind path
(I deleted the message that looked like it had private info in it - an email)
Can you just share the account ID like acct_1234 please
hard cave
Oh. It is all fake data for the most part. Possibly one of my emails. I don't mind
yes
acct_1KnOQgLJwtOOWbbo
We need to clean up out test data I apologize. I think the account we are officially using is this
acct_1IjQ3JCz7BnyEo9a
another: acct_1IvSUgJKvza8Kq5S
and then we have our tenant accounts that come with platform IDs if you want those.
that is all test data. We also have a few real connected accounts
When speaking with my developer he is saying that using this skip button may require additional development because on our end we require a stripe account present to trigger the next sequence of events so in that case we may need to hard code a stripe account for test purposes.
golden crown
Express onboarding shouldn't require you to have additional development.
Even in full test flow, data present is the same.
kind path
@hard cave These are not express accounts. You should have your developers review your integration and ensure they are creating the type of account you expect/intend to use. Note you need to specify type=express:
https://stripe.com/docs/connect/express-accounts#create-account
hard cave
ok thank you I will relay.
kind path
👍
hard cave
Ok he just looked and says that we are in fact using standard
does that change anything with this process?
kind path
Yes, very much. It also changes you're integration structure, so you should make sure this is what you intend to be using.
hard cave
I believe it is working great for our intended purpose. I mean specifically just for this test mode
kind path
Yes, test mode standard accounts require a real phone number when going through the onboarding flow.
All other info fields support the test data
hard cave
ok can I just diable 2FA and resort to the back up code by chance? All i need to do is not have to personally send text codes to every single beta tester
kind path
No, that's not supported
hard cave
Ok sounds good. Do you have any ideas on how I get 50 people signed up through test stripe tomorrow morning?
kind path
I'm no sure I'd suggest doing this with users outside your organization, but if any using onboarding entering their own phone numbers you wouldn't need to send anything to right?
hard cave
yeah but wouldnt they need to sign up for a stripe account and provide business info and everything?
I just looked and its asking for social security number and everything just like the real thing and we really don't want to make testers sign up for stripe
yeah and now it wants full banking info. not happening for the test.
kind path
All the test info is there, and you should use the "use test account" buttons
this is meant for internal testing by your and your dev team, not your users
test mode won't work with real account details anyways
hard cave
I guess I don't know how platforms and apps in our position test the onbording flow without having the billing be part of it.
kind path
What are you trying to do/test?
hard cave
our entire app. The sign up process, the onboarding flow and set up of their own platform which has a checklist that includes signing in or up for stripe. Once they do that they define how much they want to charge for their subscription. Once complete they get to invite users to their platform. Stripe is a big part of the app but can be simulated with some extra work we just figured stripe allowed for this
our platform is built to give users their own platform to invite subscribers to so they 1. pay for us to our stripe with a demo card(that part is good to go) Then they connect stripe to be able to accept payments. we don't consider their platform launched or open for business until everything is connected.
if i could bypass the 2fa on the demo account I am providing them even to the back up code that would solve 100% of the issues
lone ginkgo
catching up here one sec
lone ginkgo
I don't think there is a way to bypass the 2FA
but coming back to this point: #963083967114924052 message
I think that is an issue with your integration on why it thinks the Standard account was not connected, that "skip form" button should give you a Standard account just fine so I would debug that part of your integration
hard cave
Ok I really appreciate you taking the time to read through this. We are working internally to solve this.