#_meetshah

1 messages · Page 1 of 1 (latest)

timid spearBOT
river plume
#

You are the platform Account owner or the connect Account owner ?

vagrant swallow
#

No I am Administrator

river plume
#

Is there a particular reason for using Oauth and not AccountLink ?

vagrant swallow
#

Yeah so We can connect existing stripe account

river plume
#

Ah I see

#

can you share a screenshot of the error please ? and the oauth link

#

Alongside the Connect Account Id

vagrant swallow
#

acct_1Nb6LdDgqR5w8erL account id

You cannot perform this request as you do not have Platform Controls for Standard on the account.

above message in redirect uri

river plume
#

And could you please share the oauth url you are using ?

short verge
#

to clarify, what is the name of your business?
That account ID you mentioned is already connected to an platform called "Infy TV" for instance, is that you?

vagrant swallow
#

yes

short verge
#

ok. Well that account seems properly connected and you'll see it in the list of connected accounts in your dashboard.

#

So ignoring that error you mention, do things work otherwise, you can call the API on behalf of that account and do things, you can see them in your dashboard etc?

vagrant swallow
#

Yeah. I can see
but in testing I am not getting this kind error

and our flow working fine
but now I am getting this error and flow is not working as excepted

short verge
#

which parts specifically don't work as expected? If it's just that you're getting some error visiting that OAuth URL that is probably safe to ignore and is caused by something else like you're visiting the link while logged into your own account.
Clearly the actual connect account user was able to visit that link and successfully use it to connect to your account, since they are connected.

vagrant swallow
#

Ohkay

#

basicaly I am checking error messag if exist than I am redirecting it

#

as faiure

short verge
#

I'm not sure what that means unfortunately or how you are checking that erorr message with what code or where.

vagrant swallow
#

error = args.get('error')
I am directly taking it for redirect url

short verge
#

where does that code run exactly?

vagrant swallow
#

args = request.args
if not args:
return redirect(link, code=302)
code = args.get('code')
state = args.get('state')
error = args.get('error')
if error:
link += f"?msg={error}"
capture_message(error)
return redirect(link, code=302)

#

link this I am taking arguments

short verge
#

what page on your website does that code run on?

#

what is request and where is that coming from, basically.

vagrant swallow
#

so it is callback method of oAuth

#

I am handling this in api

short verge
#

so that is the code that runs on your server when the redirect_uri is visited?

vagrant swallow
#

yes

short verge
#

ok. Well are you sure that the error you see in that logs has anything to do with that account you mentioned earlier?

timid spearBOT
short verge
#

like I said, they are successfully connected properly, so clearly your code was able to extract the code argument and submit to to the oauth/tokens endpoint, so there was probably no error in that case.

#

so as I said, maybe the error was just from something else like yourself or some other user visiting the OAuth link, and your actual real user has no problem.