#rust_connect-extensions

1 messages · Page 1 of 1 (latest)

fresh snowBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1448779407513878753

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

ocean plaza
#

I can also provide email thread ofr more context

wraith ember
ocean plaza
#

Hi, I'm aware its a legacy extension but I was told by stripe suport through email they'll enable it for us for context


Setting Up Parallel Support
Configuration Options:

You'll need to implement logic in your application to differentiate between the two integration paths (existing Stripe Connect and the new Stripe Connect Extension) based on customer settings. This might involve adding a configuration flag or setting in your database that indicates which integration a customer should use.
API Integration:

Update your API calls to take into account which system the customer is using. This might involve routing requests to appropriate endpoints for connected accounts based on their designated integration type.
Reauthentication Process:

Make sure to communicate clearly with customers about how the reauthentication will work for those on the new extension. You'll want to provide guidance on any necessary changes they should be aware of.
Documentation:

Review the following Stripe documentation, which will provide you with essential information on integrating both systems:
Stripe Connect Overview
Building Extensions
Managing connected accounts using Connect [Additional: https://support.stripe.com/questions/us-verification-requirements-for-platforms-with-custom-accounts-faq, https://support.stripe.com/questions/payouts-or-charges-not-enabled-for-connected-accounts-with-platform-gathered-verification-requirements, https://support.stripe.com/questions/connect-platforms-manage-onboarding-and-risk-requirements-for-connected-accounts]
Next Steps for Transition
Review Your Migration Plan:```
# 
Scheduled Transition Time:

Confirm the transition time with your team and communicate this timeframe to your customers.
Customer Communication:

Send out reminders or notifications to customers, advising them of the upcoming changes and providing clear instructions on what actions they may need to take, particularly regarding reauthentication.
Go Live:

At the scheduled time, implement the changes on your end as per your migration plan and ensure that monitoring is in place to catch any potential issues immediately.
Post-Transition Monitoring:

After the transition, monitor your system closely for any errors or unexpected behavior, and be prepared to assist customers with any issues they encounter.
Please let us know if you need further support with any of these steps, or if you have additional questions. We're here to help you ensure a smooth transition.```
#

above within the code block is an email directly from stripe support through email letting me know how to migrate to stripe app

#

my main concern lies within what I need to do to migrate over my Stripe Connect Oatuh to Stripe Connnect Extension

#

For additional context :

Current Setup

  • Using Stripe Connect OAuth with read-write permissions
  • Can access "Connected Accounts" tab in Stripe dashboard
  • Have visibility into customer dashboards
  • Pull all entities, events/webhooks, and create checkout sessions

Customer Use Case

  • Some customers have a main account configured as a platform account
  • Their invoicing is managed through a connected account (child of platform)
  • All invoices/subscriptions originate from the connected account
  • Need to authenticate into the connected account and pull updates via API/webhook

Primary Goal

  • Transition to Stripe Connect Extension while maintaining current functionality for existing customers.
silver spindle
#

👋 @ocean plaza I'm really confused by the wording here. Not your fault at all but a lot of the emails you quote make no sense to me

#

My understanding is that if you are a Connect Extension (what we call Legacy but I personally disagree :p) you already use Connect OAuth so there's no logical "migration" to Connect Extensions to me
So I'm struggling to understand what our support team is asking you to do

#

rust_connect-extensions

ocean plaza
#

Sorry for the confusion I'm trying to understand what I need to do here as well 😅

Problem summary - One of my customers main account is a platform account. They have another account that manages their invoicing via connected account to that main account. Invoices and/or subscriptions currently are 100% originated and sent from the connect account. My main question here is: Does the Connect Extension allow for authentication into the connected account and can we pull updates via API / webhook to the connected account ?

#

Also we're connecting to standard accounts

silver spindle
#

Sorry the wording is again really tough to grasp in what you said 😓

You are a Connect platform acct_YOU
You have a client that has a Stripe account acct_CLIENT

They are a Connect platform themselves with connected accounts is that correct?
If so: you can not in any way access the data of their connected accounts

ocean plaza
#

You are a Connect platform acct_YOU
You have a client that has a Stripe account acct_CLIENT
Yes to both

They are a Connect platform themselves with connected accounts is that correct?
The escalated stripe support email is telling me otherwise, would email screenshots help here ?

silver spindle
#

Not really based on the other emails you quoted that made no sense to me

#

As far as I can tell you have a complex long running support thread already so I don't think Discord is the right medium to unblock you at this point honestly

I'm happy to try but I need you to explain exactly what's happening, I can't really help right now as I don't get the problem at all

#

Do you have an example acct_CLIENT I can look at? Feel free to just DM it to me instead of in public

ocean plaza
#

The core problem is that I have a customer whose Stripe setup is itself a Connect Platform with a connected account. The customer's main account is the platform, but all their invoicing and subscriptions originate from their connected account.

When I use Connect OAuth, it always authenticates to the platform account - but the customer needs me to access the connected account where the actual billing data lives.

After talking with stripe support and having it escalted through email, we've come to the conclusion that the Connect Extension allows me to authenticate directly into the connected account (rather than just the platform) so they can pull invoice/subscription data via API and webhooks from where it actually resides.

So now i'm wondering what I have to change on my end to get this to work since there aren't clear documentations on this

fresh snowBOT
silver spindle
#

I'm super confused, that's literally what I asked earlier and you said explicitly no

me: They are a Connect platform themselves with connected accounts is that correct?
you: The escalated stripe support email is telling me otherwise, would email screenshots help here ?

ocean plaza
#

Ah i misread, yeah they are a connect platform themslves with connected accounts

silver spindle
#

What you are trying to do is impossible. You as a Connect platform, can never see the information in connected accounts of your own connected accounts

So you are acct_YOU and are a Connect platform
Your client is acct_CLIENT and is connected to your platform via OAuth
You can see everything in their account
But if that account has a connected account acct_ABC it is impossible for you to see acct_ABC in any way unless that specific account also connects to your platform

ocean plaza
#

maybe i'm misunderstanding here, so is this email referring to something else ?

image.png
silver spindle
#

honestly when I read #1 I feel like that person is totally confused and is saying something completely wrong

#

ultimately what you described is absolutely impossible with our product

ocean plaza
#

got it i'll email them again and ask for clarification