#khoi
fierce crescent
solid storm
hi pgskc, i am using stripe connect express as a platform
we have a connect customer signed up 2 hours ago and their account id is: acct_1LpzqE2f1IftviR7
however, i am not seeing it on my stripe dashboard and no associated logs with it. It's as if this acct doesn't exist at all acct_1LpzqE2f1IftviR7
vale apex
Hi, taking a look
It looks like it's connected to a Platform account. What are you seeing when you search for this account id in the Dashboard?
solid storm
i am not seeing anything at all
"Could not load the connected account"
i am wondering if we messed up with api key provisioning here ... and it got assigned to a different platform account
but we got several connect accounts on our paltform recently and they all seem fine
vale apex
Hmm, do you have multiple Stripe accounts?
solid storm
i have
so you actually saw that account in stripe system
acct_1KejnuGzJjwu8BjO this is my main platform account - is it associated to that
vale apex
Can you try Retrieving the account via the API, https://stripe.com/docs/api/accounts/retrieve ?
vale apex
I'm looking, I can confirm that this connected account is connected to the Platform Account you shared above. I'm now trying to rule things out. I'm also testing it on my end
vale apex
Can you share that request id with me please? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
vale apex
Hmm, looking
solid storm
ya this is odd, i am getting all kind of callbacks from Stripe: with their name, email, mcc, carge/pyayment info
but can't see it on stripe dashboard or logs
vale apex
When you made that account Retrieve call, did you see any error on your console?
solid storm
"message": "The provided key 'sk_live_*********************************************************************************************P7X84m' does not have access to account 'acct_1LpzqE2f1IftviR7' (or that account does not exist). Application access may have been revoked.",
vale apex
I see that the account was briefly deauthorized, https://stripe.com/docs/api/events/types#event_types-account.application.deauthorized but it was authorized shortly. Can you try the Retrieve call again? Are you seeing the same error?
solid storm
you mean retrieve the connect account right?
{
"error": {
"code": "account_invalid",
"doc_url": "https://stripe.com/docs/error-codes/account-invalid",
"message": "The provided key 'sk_live_*********************************************************************************************P7X84m' does not have access to account 'acct_1LpzqE2f1IftviR7' (or that account does not exist). Application access may have been revoked.",
"type": "invalid_request_error"
}
}
ya still no luck
vale apex
I was able to further investigate and confirm that OAuth Token was consumed twice, which disconnected this account from the platform.
vale apex
I think you'd need to create a new account and I highly recommend that you start using the Accounts API instead: https://stripe.com/docs/connect/express-accounts
solid storm
wait so what happened to that outstanding connect express account
is there a way for me to do this on behalf of our customer instead of having them go through the same flow again?
vale apex
You can pre-fill their information: https://stripe.com/docs/connect/express-accounts#create-account and make it easier for them
solid storm
there is nothing you can do in the backend right now?
sorry it's a fairly big account for us so we would rather find a way to resolve this on our end
vale apex
I'm afraid not.
solid storm
if they go through my express flow again
with the same info
will there be any issues?
vale apex
Actually, I think you can reconnect the Express account, sorry for the confusion.
Further investigating, please give me a moment
solid storm
omg yes please!!!
vale apex
I'm confirming with a colleague here, sorry for the wait.
solid storm
this would be of tremendous help!!
vale apex
I was able to confirm that they'd need to go through the OAuth flow again, I'm afraid.
solid storm
... oh
vale apex
I think they would be fine passing the same data
Essentially, I would debug your code and make sure that your not consuming the OAuth token twice. Or just move away from it and just use the Account API I shared before.
solid storm
did something change with stripe oauth recently
it was working perfectly fine for the psat 6 months :/
vale apex
I do no think anything changed in the last 6 months - it has been a common issue before, did you make any changes on your code?
solid storm
No we didn’t
But it’s also odd that some other accounts can still sign up just fine
You confirmed that the root cause it’s because we consume the auth code twice?
gilded condor
Really if you have the bandwidth you want to switch to Connect Onboarding
And not use OAuth
This was mentioned above
solid storm
Gotcha
gilded condor
But it is the proper fix and the right route to go here
solid storm
And that will still work with this customer right
Will it just be a net new express account for them
gilded condor
No for this customer you need to send them through OAuth again
solid storm
Ooo
gilded condor
Unless you create them a new Express Account and they use a different email+phone combo
But for all folks going forward, you will never run into this issue if you use Connect Onboarding isntead of OAuth
solid storm
Gotcha