#benk

1 messages ยท Page 1 of 1 (latest)

willow fieldBOT
sharp cargo
#

Hello! If it's a technical/developer question I'd be happy to help

signal quest
#

hi karbi

#

I already had a round of discussion today with vanya, toby and the others

#

it's somewhat a technical issue in regards to Connect Stripe and how the connected account has got a different AccountId compared to what we receive from your API

#

I have created 2 Stripe Test Accounts: one as a Connect Platform account and I created a new Stripe Test Account to connect to the platform

#

when the connection occur using the "https://connect.stripe.com/oauth/authorize" endpoint we get back the successful callback with the authorization_code and the token looks fine with a relevant stripe_user_id but its value is not the same as the "acct_" value of the connected account

sharp cargo
#

Can you share both values that you get back?

signal quest
#

sure

#

the callback details are:
authorization_code: ac_NrbWeMGkKvdOHoo3BsA0XdsbIf0nIOur
OAuth token: {
"livemode": false,
"scope": "read_write",
"stripe_user_id": "acct_1N5sIxCG4ZVGtkI5"
}

#

and the connected account Dashboard shows the AccountId as: acct_1N5r66HE46Ih6ki5

sharp cargo
#

๐Ÿ‘ give me a few minutes to take a look

signal quest
#

cool thanks

sharp cargo
signal quest
#

but I think this advice was wrong from the previous discusson

#

a newly created Stripe Test Account will have an "acct..." in the Dashboard

#

after this when I complete the Stripe Connect connection of this newly created Stripe account get a callback from Stripe which contains the OAuth token with the "connected" AccountId - this is also being "acct...".

sharp cargo
#

Yeah the account ID that's shown in https://dashboard.stripe.com/settings/account is the account ID of whichever account you're currenctly logged in as (you can be logged into multiple accounts which you can switch through the dropdown in the top left corner)

#

Are you 100% sure the account that you've connected through oauth is acct_1N5r66HE46Ih6ki5 and not acct_1N5sIxCG4ZVGtkI5?

signal quest
#

when I'm presented this page I simply pick my Stripe account which I want to connect to the Platform. This account I'm connecting is "acct_1N5r66HE46Ih6ki5"

#

and yes I'm 100% this is the account as the associated email address only has got 1 Stripe account against it

#

once the Stripe Connect connection is confirmed by me as a "client", the callbackURL receives this OAuth token:
{
"livemode": false,
"scope": "read_write",
"stripe_user_id": "acct_1N5sIxCG4ZVGtkI5"
}

#

based on my reading of Stripe docs the **stripe_user_id **s then the "connected" account's AccountId which need to be passed with every connected transaction

#

is the above right?

sharp cargo
#

Can you show me a screenshot of the page you see when you click the oauth link?

#

And yes, your read is correct - the stripe_user_id is what you'd use in the STripe-Account header if you want to make requests on bahelf of that account as the platform

signal quest
#

when I get this I'm already logged in with the account I want to connect, so I just simply click "Skip this form"

sharp cargo
#

Aha! That helps clarify things a lot

#

So the reason this is happening is because you're clicking the "Skip this form" button - when you click that button while trying to connect to an existing real stripe account we create a new "test mode only" account that has limited permissions

signal quest
#

why are you doing that without any description of this on a "test" page? That link seems to indicate "don't bother filling in any required details, this is just a test setup and you can safely ignore it"

#

so what do I need to d to get things working?

#

filling out all the necessary details like bank account, info about my company, etc. just for testing purpose?

willow fieldBOT
signal quest
#

so do I have to enter in all sort of business details just to try and test this using a Test Account?

sharp cargo
#

Yeah sorry this isn't super clear (this behavior has changed over the years and isn't super well documented)

signal quest
#

unfortunately that's something we cannot do

#

we already have existing clients on our "platform" where we just simply wanted to migrate the existing Stripe customers onto out Stripe Platform account with minimum effort

sharp cargo
#

Gotcha - then your only option would be to fully activate those accounts/provide real account information for them

signal quest
#

we were told all we need to do is connect these existing customers through the OAuth link - onboarding the clients via the API you referred to is just unexpected changes in our system

#

ok thanks

sharp cargo
#

And again - I'm sorry it's not the best flow. Standard accounts have the extra complication of being full accounts that user's can log into and any account information that is provided is shared between live/test mode (which is why testmode only accounts have to be specially created)

signal quest
#

is there any way I can access these "phantom" accounts if I click on the "Skip this form"?

#

the reason is I need some proof that all the connected transactions are there on the connected account, not just the platform. I have managers who need reassurance

#

I can see the processed connected transaction on the Platform account obviously so I know it works but would want to confirm these on the connected phantom account as well

zenith anchor
#

Hi there ๐Ÿ‘‹ taking over, as my colleague needs to step away

Give me a few minutes to get caught up.

sharp cargo
#

Alternatively, if you all you need is proof that the transactions are on the connected account you can use the API w/ the stripe-account header to check what is on the connected account