#shivam_api
coral otterBOT
đ 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/1402099969711669278
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
vagrant saffron
Hi! Looking into this.
I don't have access to this ticket: https://dashboard.stripe.com/support/sco_SlvD3ZBENg2Pe2 Do you have a ticket number?
Also you linked this issue: https://github.com/stripe/stripe-apps/issues/867, does your app not have a UI as well?
For testing you can follow the steps here: https://docs.stripe.com/stripe-apps/test-app
empty thorn
there is no ticket number. in that thread, unfortunately. Our app does not have a UI - we want it to serve as an authentication service to our main application
vagrant saffron
Does the article test article help with that?
empty thorn
https://docs.stripe.com/connect/oauth-changes-for-standard-platforms
we're running into the situation described in this post: our existing Stripe integration is a legacy platform read/write integration, and we have a customer that is connected to a different platform so can't connect to us. A read-only integration is fine for us, so if Stripe is able to update our integration to a read-only Extension that is compatible with this customer, that would be easiest.
First -- can we double-check if that's possible?
If not, (as we know Extensions are deprecated now), it seemed like we could move forward by creating a Stripe app, then we could get read-only access to the customer's account by having them follow a link to authorize the app -- to double-check, would that work for this type of customer?
And then if the best approach is to create an app, we need to figure out how to test/deploy it and differentiate it from our existing Stripe integration
vagrant saffron
First -- can we double-check if that's possible?
This is not possible because of the reason you mentioned: Extensions are deprecated.
If not, (as we know Extensions are deprecated now), it seemed like we could move forward by creating a Stripe app, then we could get read-only access to the customer's account by having them follow a link to authorize the app -- to double-check, would that work for this type of customer?
When the user installs your Stripe app, they need to provide the relevant permissions. So you don't need to do a separate auth: https://docs.stripe.com/stripe-apps/reference/permissions#customer
And then if the best approach is to create an app, we need to figure out how to test/deploy it and differentiate it from our existing Stripe integration
You will need to create a new account as you cannot have a connect account.
empty thorn
so just making sure -- there is no migration path for this? we must make a new account?
https://docs.stripe.com/stripe-apps/migrate-extension
vagrant saffron
I reviewed our documents but it's unclear whether you can continue using your current account with Connect platform read/write permission. As you have an open ticket, please inquire about this there, so the support team can check internally.
empty thorn
Sounds good - thanks sam.