#Chase Moskal
1 messages ยท Page 1 of 1 (latest)
If a user hasn't completed the onboarding, you can create a new account link with type=account_onboarding
type=account_update is only for custom connected account which completed onboarding process and would like to update account details
okay, maybe let's consider a scenario like this:
- my app creates a new stripe account for a user
- user performs and completes onboarding
- user then goes into their stripe dashboard, and deauthorizes my platform
- user now wants to "reconnect/reauthorize" my platform
- ๐ค should my platform create an
account_onboardingaccountLink, or anaccount_updateaccountLink? is this the right way to think about this?
and how can i detect when the reauthorization has happened? perhaps a webhook like account.updated?
for context,
we're trying to figure out a better way to approach stripe connect for our integration -- perhaps to allow users to swap stripe accounts -- and reconnect to accounts that had been previously been disconnected.
How do you create a connected account currently?
using the node sdk, we call stripe.accounts.create,
then we generate an accountLink type=account_onboarding for that new account.
they're standard accounts.
I see! In this flow, connected account can't be deauthorised themselves in the dashboard
Since their connected account was created and managed by your platform
oh, very interesting -- this might be fantastic news ๐
so, we don't have to listen for account.application.deauthorized webhook?
and we don't have to think about reconnecting/reauthorizing at all?
account.application.deauthorized is for legacy flow where an existing Stripe account would like to connect to a platform, then deauthorise. This is no longer recommended
Yup, you're right with your current integration
oh wow, i'm so glad i asked! you've probably just saved us many hours going down the wrong path!
okay, let's call this issue solved! thanks so much, massively appreciated!
๐๐๐
No problem! Happy to help ๐