#ben_api
jovial gustBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1314657524468678707
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
low mesa
sorry
got wrapped up in what i was refactoring!
Yes, so previously we used the oauth flow to onboard and disconnect acccounts. Disconnoecting looked like this:
$stripe->oauth->deauthorize([
'client_id' => env('CONNECT_CLIENT_ID'),
'stripe_user_id' => $this->stripeAccountId(),
]);```
How does disconnect look when you have created / onboarded an account using the account api + account link api instead?
dapper flame
It depends on the specifics of the connected account and why you want to disconnect them. Do these accounts have full Stripe Dashboard access?
jovial gustBOT
low mesa
They are standard accounts, i presume yes they have full stripe dashboard access as I have not yet looked at restricting this
is it recommend that we do restrict this?
viral onyx
Here is what you'd want: https://docs.stripe.com/connect/platform-controls-for-stripe-dashboard-accounts#remove-accounts. You can also delete the account via the API: https://docs.stripe.com/api/accounts/delete
low mesa
also im getting really inconssitent results here, sometimes when i create + account link to onboard, then go to hosted onboard form, it logs me in and I can create from my existsing details, other times it givres me no option and wants me to setup a new account. why?
This is turning into a bit of a ballache
what im suddnely seeing in the network tab is an api call called 'new' that is returing a 401
viral onyx
Is it for the same credentials? How can I reproduce these on my end?
low mesa
im aoso persisrtently being logged out of stripe too which is somewhat infuriating. Ive never had this issues in the last 6 weeks of build
yes it is
i am using an existing account on benreza.martin@gmail.com which ive used throughout all my testing.
Im testing locally. In the last hour or so this has begun happening
viral onyx
I can't reproduce what you're seeing here. Can you just clear your cache/ cookies and restart?
My account is also logged in, it does not log out automatically.
low mesa
Yeah I can try that bear with me. I must have been asked for 2fa around 35 times now
viral onyx
Yeah, it asks me everytime too
low mesa
same issue
literally makes no sense, feel like im banging my head against the wall with this
viral onyx
I'm attempting to reproduce what you're seeing on my end but I can't. The fact that it's intermittent is what is confusing to me.
low mesa
well now its constant, ive not seen the option to create from existing account for ages now. Nothing has changed that could cause this; e.g. the stripe account I use on benreza.martin@gmail.com hasnt been changed.
It all started when these 2fa things started occuring which is new for me
req_UEt3hhgGUkpR17 - this is me creating the account
req_Qzgl8UpNPNOxFo - this is me generating hte link
evt_1QT65BS1BYcBaFZcXLtNN67N - this is the last event where things were fine
is it possible somehow this account that was fine, has gotten stuck in some bizarre state that i cant see in the dashboard and is now preventing me from connecting properly?
viral onyx
Well this account, acct_1QT649S1BYcBaFZc is deleted from the Dashboard at 2024-12-06 18:57:46 UTC
low mesa
yes i clear it out once things stopped working
ive tried literally everything now but im always getting forced to create a new account where as prior to this, at 18:16 it was fine and as expected
but im not letting it go as if it happen now, then it can happen in production
viral onyx
Yeah, I can't reproduce what you're seeing.
I've tested this multiple times and I can just resuse the account. It does not log me out automatically. However, I do see 2FA each time
low mesa
ive been changing settings one by one in our main account > connect settings> i switched off efvery country apart from USA under Countries and suddenly its back
this could be coincidence as that makes NFS
right ive isolated it. It isnt the setting. It only presents now if there is an account that I have begun to create and have some of hte detials populated, thati remove our end but not from this stripe account. So when I was originally testing there must have been some dormant account attached to the stripe account that was providing me the option to create from
christ
viral onyx
That explains why I was unable to reproduce this on my end
low mesa
well i can validate this at all, im still getting totally inconsitent results where as if we do this with a competitiro, we get consistent reuslts
so something is very very wrong here
jovial gustBOT
low mesa
i cant*
carmine trench
Hello 👋 , catching up here as my colleague needs to step out soon...
carmine trench
I am not immediately sure what the issue may be and am consistently seeing the correct behavior myself. If you log in to the standard dashboard, are all of your existing accounts still available in the dropdown in the upper left of the page?
low mesa
yes, i just cant consistently reprorudce this which does not fill me with any confidence in this at all
can i screenshare this as it would be so much simpler to show you whats happening here
as this is bizaree
carmine trench
I think I get the behavior. As long as you are providing the exact same email address, we should show the same list of existing accounts on the onboarding page. I am going to consult my colleagues on whether there is other debugging we can do at the moment but this may have to be something we create a ticket for so I can escalate to my colleagues that work on the onboarding page
low mesa
Can you give me a good reason to not use the oauth flow here? This all started today when I was told not to use this and use the API. Since then, its been nothing but problems
as i honstly cant wrap my hea aroudn this and ive lost an entire day to it
and do that team support on weekends?
carmine trench
Was this in a previous discord thread?
low mesa
errr yes i think so, it was all today
carmine trench
This server aren't open over the weekend, though depending on time zone our re-opening may be on sunday
Checking in to why my colleague suggested that, a lot can vary based on context here
low mesa
Ok so I want to achieve 2 main things here:
- We want control over this account and want to (if possible) prevent the account we create from being used by other providers
- We want to offer anyone with an existing account, to at least create an account from that, with us, to make the onboarding as easy as possible (to prevent drop off)
These are my 2 rquirements.
is it possible to setup a stripe account thart is only a test account? As I wanrt to validate what i think i am seeing now, but cant becuase all the account we have a production created accounts
carmine trench
It looks like they were more saying that OAuth is legacy but still usable. OAuth would fit both of those. We do have a restriction that accounts can only be connected to one platform at a time, but that mostly means that if an account is already connected to another platform, we create a new account with the same login and connect that new account to your platform. That seems to fit both of your requirements. We do try to encourage people to use our newer APIs and I do think the bug you are seeing is fixable but if it is stopping your progress that much you don't need to specifically use that API.
low mesa
So with oauth whilst we find we can sleecg from the list of accounts, it only allows us to do with accoutns that are not currently connected to another platform (as you said). Hwoever, when one is avialablew and selected, sometimes we are forced to set it up as new, othertimes it just connects. Again much like the API its totally inconsistent which is wierd.
The API works, but fels liks you get far less control as it doenst use query params in the return URL and that has otb defiend when you create the link, so its somewht limting versus oatuh.
I thin part of the issue we are seeing is from using test mode and that preventing us from connecting to most of these accounts which are production accounts
carmine trench
I am honestly not sure what may be happening here. If you provide the same parameters and enter the same email address, it should give the same results, which is the behavior that I am seeing here. Subtle differences can make some things surprisingly different with onboarding, but the upfront selection of available accounts is consistent for me. It is also something that is decided on via our backend, so I don't think your device/browser would be effecting this. Trying to think of how to get a clear repro to escalate to my colleagues.
low mesa
I think it’s could be related to test mode and the accounts we have available but im really not sure. Hence me suggesting a screen share.
Another inconsistency is what I see versus one of my team when using the same account is different. He sees a list, I see 2 lists where ther top is accounts I can select and bottom is ineligible accounts
carmine trench
I may have been misunderstanding what you mean by "inconsistent". So you mean that all accounts across test mode and live mode are not always shown, not that the list of account differs when you do the same thing in the same mode?
low mesa
Ive gotten to the bottom of it, one of the guys from ireland has been assisting me too. Its to do with legal entity sharing limits, which we must have hit with our internal test accounts