arch37ype-connect | Stripe Developers | Page 1

cursive rose Mar 11, 2022, 11:38 AM

#

hi! how did you set it up exactly? (which specific guide do you use for your integration?) . This can be a common problem if you use OAuth for instance and have an issue finalising the connection.

jovial dagger Mar 11, 2022, 11:43 AM

#

I have used the API to create a "standard" account, then generated an account link. My application then correctly responded to an account.updated webhook call for the connect account in question. That webhook request from Stripe contained charges_enabled: true and details_submitted: true

#

So our application marked that account as ready to use

cursive rose Mar 11, 2022, 11:44 AM

#

hmm ok, interesting. And you don't see it in the list in the dashboard? What's the account ID acct_xxx of this account?

jovial dagger Mar 11, 2022, 11:45 AM

#

Sent it to you privately

#

not sure if that's necessary

cursive rose Mar 11, 2022, 11:45 AM

#

I have DMs disabled. Just post it here! the acct_xx ID is not sensitive.

jovial dagger Mar 11, 2022, 11:46 AM

#

Ok sure. acct_1Kb0ZhQLMFnseCkb

cursive rose Mar 11, 2022, 11:46 AM

#

ok, so that account has been deleted(which is why you would not see it in your dashboard).

jovial dagger Mar 11, 2022, 11:47 AM

#

Ok, i wondered if that was the case. I realised this morning that our app does not respond to account deletion or deauthorisation

#

So that would have been account.deleted event?

cursive rose Mar 11, 2022, 11:48 AM

#

it's account.application.deauthorized

#

but yeah, it's possible for the user to log into their Stripe dashboard and close their account if they wish, you'd get that event if they do that.

jovial dagger Mar 11, 2022, 11:49 AM

#

So, I assume it'd be safe to listen to both those events and follow the same path of deactivation in our application

#arch37ype-connect