#vitorleitao.
1 messages · Page 1 of 1 (latest)
Thanks for the info, checking in to this
Perfect, thank you very much
I am also not seeing where the negative balance is at the moment but am still looking. Can you try this again and send me the request ID from the request that got this error? https://stripe.com/docs/api/request_ids
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Sure, let me see if I can get it
req_XQDiEG2KTYdwSm
this would be another one that failed
Having trouble looking up that request for some reason, still looking
Out of curiosity, are you just starting development for your express platform? Or is this a test account for an existing platform. The OAuth flow is considered legacy, for newer users we recommend using this onboarding flow https://stripe.com/docs/connect/express-accounts
This is an existing platform, and we create the users by using the CustomerService.createAsync
for a bit of context, we have a user that has a stripe account, and wants to remove all references to my company, but we want to keep the information on our end, so effectively we want to break the link between us and the customer account
The support team said to use that Deauth method
is this incorrect?
Gotcha, that makes sense in this context. Do you know when that req_XQDiEG2KTYdwSm request was made? I see an attempt to look at it from the dashboard today but am not seeing a log of when the request was actually made. Not sure if I am searching the wrong time period
it was done literally 20seconds before I sent it to you
cound it be because its in test mode?
Gotcha
Not test mode, it is because it is OAuth. OAuth requests from it are separate from how the rest of our API works and interacts with our systems. I will consult a colleague on how to look in to these requests
Perfect, thank you very much
So it looks like we stopped allowing deauthorizations like this last November. You can still delete express accounts, but deauthorization is no longer allowed
I will make sure we update our docs and error message to reflect this.
Is there a way to simply break the link between the customer and our stripe, so we can still maintain the details on our end?
Can you try making this request? https://stripe.com/docs/api/accounts/delete
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
And would this still maintain the customer in our side? or would it delete it?
As in look them up via the API? I can check
via API or the UI, because the goal is simply for the customer to stop seeing my company in their login
Let me get a screenshot so its easier to see what I mean
What we are trying to do, is break the link between these, so that they no longer show up on the users
From my testing, you cannot access the account anymore from the API after deletion. I am unsure about the UI of the Express dashboard but you can try deleting that test account and refreshing the page
but while maintaining the data on our side, in case we need to go back
Express accounts are always made by and exist for a singular platform account, so I'm not sure what the user is looking to do here.
I see what you mean.
It might be the user is confusing an account created by Express with his own personal stripe account.
Is there a way to block or lock an account and stopping access to the dashboard for it?
From what I can see, that would be deleting it if anything. This would remove the account from your API and dashboard though so you wouldn't have as much data as you would like
I think you'd still be able to look up payment intents and such on your platform related to the account though. Do you have specific pieces of data you are looking to still have access to?
ok, if all payment related data is still available, then a delete might be enough for us
we will try on our test account just to confirm