#stripe_connect_platform - Customer Deauthorized
karmic shore
gleaming trellis
Here is the event.
You asked me to email Stripe support which I did. They won't discuss the customer account. Sigh. So I emailed the customer to email Stripe and he emailed Stripe and got a response to contact me and emailed it to me.
Customer is asking Stripe to just explain why an "automatic" deauth is occurring.
This was their response:
Hi there,
Thanks for getting in touch! Anthony here from Stripe Support.
I wish we could be of more help here, but if you're having a hard time connecting a Stripe account to <Stripe Connect Platform> --- the root cause is not likely something you're going to be able to action on your own. You're going to need to reach out to them directly.
The only exception to this is if, for whatever reason, you are inadvertently closing or exiting out of their onboarding process before it is complete. I don't know about <Stripe Connect Platform> process specifically, but I've seen this happen to users from time to time.
To give you some possible reason -
- The account opener visits the Applications tab in their dashboard and deauthorizes the platform
- The platform uses the OAuth API to deauthorize the account, removing their access. (https://stripe.com/docs/connect/standalone-accounts#revoked-access)
- The platform is using OAuth to onboard accounts, and the authorization code (ac_XXXXXX, included in the redirect_uri) is consumed with the /oauth/token endpoint multiple times. Consuming an authorization code multiple times deauthorizes the account, per the OAuth specification.
If you feel like you're going through the onboarding process and it is completing, and you do not appear to be Connected, or it is not possible for you to complete the process for some reason, you'll need to talk to them. If they require assistance, they can reach out to us via:
https://support.stripe.com/contact/
And it would definitely be helpful to them to provide some concrete details about the problem. Screen shots of where the process is going wrong would be great, as well as details about the system you're using. (Sending a PDF from a site like http://supportdetails.com/ is something I always find helpful when trying to troubleshoot similar problems.)
I hope this information helps. If you have any other questions, feel free to reply directly to this email and we'll be happy to help.
Regards,
Stripe Customer Service Rep
The only possible reason would be #3 (in list above sent by Stripe) since we do Oauth his account with the same URL possibly? But....the connection is completing. I literally watched him connect in a Zoom call and saw him hit buttons in our app that make successful API calls so he is getting connected successfully (and I can see that he is still now connected), just subsequently getting deauth'd mysteriously. You have the exact event now. I just need to know what causes an "automatic" deauth event multiple times and at 5am?
karmic shore
Looking into this. Will get back to you in a sec
gleaming trellis
Thank you! 🙂
In #3 when Stripe says "ac_xxxx" do they mean the account ID "act_xxxxx" and just forgot the "t". Seems like it all connects fine though my guess right now is that this deauth is from Stripe's side not ours - a mysterious #4. lol
Any update?
karmic shore
Still looking. Also juggling other users
gleaming trellis
ok
karmic shore
Hey. Looking into this more, an explicit request was made to deauthorize that account. A request was made via an app called paidmembersapp to /oauth/deauthorize for that account.
gleaming trellis
Can you provide the request ID? Are you sure that is the one associated with the event that was marked as "automatic" - the request I sent? I don't see any request headers or anything that says we made it so I'd like to see that.
supple locust
Hey 👋
stepping in for codename_duchess as they have to hop off soon
Let me look into getting you the request ID