#Matias Rodriguez - Standard Connect

1 messages ยท Page 1 of 1 (latest)

woeful relic
#

Hi ๐Ÿ‘‹
Just so we're on the same page I want to share some terminology.

The "main" account is what we call the Platform. The "secondary" account is what we call the Connected Account.

So in this case, since they are both Standard accounts each is pretty independent. In order to update the Connected Account you will need to log into the Stripe Dashboard as them to make the changes.

Can you share some of the request IDs for your direct charge attempts where this error was triggered?

Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

fresh fox
#

Thank you for the terminology!
Let me share something from your answer.

[In order to update the Connected Account you will need to log into the Stripe Dashboard as them to make the changes.]

Yes, when I do that, I can't change the name of that connected Account.

Since I've made multiple requests and tried with many different accounts, I only have this last one at hand:

ID: req_UFNpXHyIsqmidJ

But I get stuck in this same thing for all the requests, so all are the same.

Thank you again!

next shale
#

๐Ÿ‘‹ Just hopping in since @woeful relic has to head out soon - when you say you've logged in as the connected account, do you mean you're logged in as the Platform and clicked "View dashboard as ..."? Or have you actually logged out of the platform account and logged in to the standard account?

fresh fox
#

I'm logged in as the Platform and clicked "View dashboard as..
See the image:

next shale
#

Yeah that won't work - you need to actually be logged in as the standard account to do this

fresh fox
#

That's the thing, the Standard account itself has a name. I can change it, rename, create a ''New Business" (not necessary), but it doesn't reflect when it's connected to the Platform account (at least in test mode)

next shale
#

What is the account ID for the account from the screenshot?

fresh fox
#

This one: acct_1KiM1uHrvoRi8lnQ

next shale
#

When you're logged in as the connect account, what happens if you click the down arrow next to "Connected Company"? Do you see other accounts listed there?

fresh fox
#

The 'Connected Company' isn't called 'Connected Company' it is now 'New Business'. It never was Connected Company though.
The 'Testing' one is the Platform one, the 'Business A' was another test.

Also as you can see, this connected account and the 'Connected Company' Standard one, doesn't share the same account ID. Not sure if this should happen, but I thought it would be the same

next shale
#

Let's back up for a second - are you currently logged in as "New Business" (account acct_1KigzdEkq9Q4R9xF)? And how was acct_1KigzdEkq9Q4R9xF created?

fresh fox
#

I'm seeing the dashboard as the connected account account acct_1KigzdEkq9Q4R9xF, and it's showing me that its name is New Business. This "New Business" should be the 'Connected Company', because it was created when the oauth flow link has been given from the Platform Account (Testing). All in test mode.
Does it make sense?

next shale
#

When you created this account through the Oauth flow did you happen to click "Skip this form"? and are you sure you were logged in as "Connected Company" when you went through the Oauth flow?

fresh fox
#

I'm sure I was using the same email for that 'Connected Company' (it's jplusbridge@gmail.com) when I went though the Oauth flow. Yes, I clicked 'Skip this form' and then it takes me to a page saying: Congrats.. blablabla

May I have something wrong in my code? I've just cloned the sample and changed my credentials in order for it to work.

next shale
#

I don't believe it's an issue with your code - I believe the problem here is that you shouldn't be clicking the "Skip this form" button. Doing so creates a new "test-mode only" fake account instead of connecting the existing account acct_1KiM1uHrvoRi8lnQ. You should go through the oauth flow again, but don't press the "skip this form" button

fresh fox
#

Alright, that should be it. Anyways, It doesn't allow me to enter fake account details, such as 0000000000 for the mobile number, and will not let me put also, fake information about my account details during the Oauth flow.
Is not a different way to do that?

next shale
#

That's expected if you want to be connecting to an existing account - since the account already exists we expect it to have valid values, not just test data

fresh fox
#

I understand that, but it seems like I cannot test this scenario before going to production then.
Would you recommend a different way in order to test what I wanna test? Would an express account represent almost the same thing as a standard account would in a real scenario? (I know that for express accounts we have a table with different testing data in order to test it).
Could you give me your insights about it? (sorry, I'm super new at this)

next shale
#

You'd test this scenario by completing the Oauth connection with real account information - that would allow you to test the whole flow end to end. Are you running into specific issues getting this to work?

fresh fox
#

There is no way I can fill those fields because I'm in Argentina and this country isn't listed.
I was trying to fill out all that info with some fake info, but as you said, It's designed for real information, so I cannot go through the whole steps

next shale
#

Even if you're in argentina, since you're using Stripe I assume you must have a business in a country we support - if you have no business address in a supported country there isn't really a way for you to test this out and I'd suggest you contact support (https://support.stripe.com/contact) for more help

fresh fox
#

Yes, that is correct! But since I just wanna test how the platform works connecting an already created Standard account to mine, I wouldn't put the real information of my business just for testing (and anyways I don't have access to it).
I might be wrong, but it sounds logic for me that a developer shouldn't use real information of the business for testing things out.

Just in case I'm misunderstood, I'm not mad with you nor anyone, I super appreciate your help on this! I'll see if there is something else we could do.

next shale
#

Yeah the reason this is so hard is because you're specifically trying to test out connecting to an already existing standard account. If you were just trying to test out the connect flow in general with a new account, that would be easy (you'd use the "Skip this form" button), but as I mentioned earlier, connecting to an existing account means you can't skip the form and you have to input real account information.

#

I need to head out, but if you have any follow up questions @austere dirge can help you out