#kevinbett
1 messages · Page 1 of 1 (latest)
Hey there, what about this makes it unexpected specifically?
Can you share any specific events/examples related to this?
this is the issue i encountered
Are you the platform developer here?
yes iam the Developer
I took the "acc"for this user and searched on the platform connected accounts and didn’t find any results for that "acc"
It looks like you consumed the OAuth token twice, which causes a disconnect
You need to be very careful to consume that only once
so what should i do to recconect the account back is there a call i should make
You need to take the account through the oauth flow again, ie they need to re-authorize your platform
so that means the previous 'acc' can’t be retrieved they will be assigned a new one?
I assume you mean the access code given to you to consume during the oauth flow, and no you can't use it again
Or do you mean something else?
seams weren’t on same page'. so i mean the user registered as a seller on the Platform and they were give accouint id and right now the connected account can’t be found on stripe
so the question im having is can the connected seller account id be retrieved using the oath?
yes that seller account be reconnected back to Platform
If they log in and you do you oauth again
how will they login yet their connnected account isn’t there or we will need to run the action register the user as seller once more
from our Application ui
If this is a standard account, can they not log in directly via the dashboard using their email address?
I'll note: Stripe, here, is using "Standard" as a very specific thing - i.e. there are "Standard", "Express" and "Custom" Connected accounts - Stripe does not just mean "standard, usual accounts". I'll also note your screen shot (up there ^^^) says "Stripe Express"