stripe_connect_platform - Connect twice | Stripe Developers | Page 1

naive pollen Jan 18, 2022, 4:00 PM

#

weary garden Jan 18, 2022, 4:04 PM

#

What is the best way to go through the Stripe Connect flow.......twice.

#

Result would be that the Stripe Connect association between our platform account is not changed - no keys are rolled - but we just save the same keys etc. in two different models in our db.

naive pollen Jan 18, 2022, 4:07 PM

#

Good question. You think that this is how the issue on your last thread happened?

#

Are you currently trying to go through the process twice with some test account and can't get the process to happen again?

weary garden Jan 18, 2022, 4:22 PM

#

Yes

#

Just wanted to see if there is a best practice way of doing it and my developer is testing the current flow now.

#

We could just not really go through the Connect flow and save the current data over to the new model but the customer likes the Stripe Connect flow and sometimes they connect a different Stripe account. It is just an issue when they only have one Stripe Account that they connect both times.

#

Also, do you have a deauth event - customer is worried that it will fail silently and he won't be collecting payments. Can we listen for an event and send him an email notification that he was just deauthorized?

naive pollen Jan 18, 2022, 4:40 PM

#

Looking in to the rest of that. Yes there is an event https://dashboard.stripe.com/events/evt_1KHR5tC6Ro2uoLsCZm9eOASK

#

You should be able to see it if you set up a connect webhook on your platform account that can receive that event type

naive pollen Jan 18, 2022, 5:10 PM

#

Had to drop off of this for a moment. Looking in to it again. Linking to the previous thread for reference. https://discord.com/channels/841573134531821608/933014527723864065

weary garden Jan 18, 2022, 5:24 PM

#

OK. I had the customer contact Stripe support via his account and send that req_ that was listed as "automatic" and deauthorized his connection to us. Super weird. Hopefully we will get figured out.

naive pollen Jan 18, 2022, 5:50 PM

#

Sounds good. As an update: I was able to test this on my side.

#

An account can go through the connect flow twice though after the first time it will create copies of the account and those copies will connect to the platform. I just directed myself to the OAuth link twice.

#

That did not reproduce your error, the copies were able to connect and it did not deauthorize the previous connection.

#

I was able to reproduce this by making the OAuth token call twice on the same authorization code though.

  -u sk_test_123: \
  -d "code"="ac_456" \
  -d "grant_type"="authorization_code"      ```

#stripe_connect_platform - Connect twice