#hrishi-mittal_api
gusty ploverBOT
👋 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/1319376379233702051
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
verbal estuaryBOT
humble marsh
Hi there 👋 just checking, when you use the term app, is that indicating that you plan to build a Stripe App?
https://stripe.com/apps
Or is that just the term you're using for your product/system/offering?
short lichen
the latter. right now I'm building a google sheet add-on. so the user clicks on a "Connect stripe" button in a google sheet.
not a Stripe app
humble marsh
Hm, so Connect would be the next best option, though you'd have use our OAuth flows to connect to existing accounts. We also no longer recommend that flow, since the introduction of platform controls, as you run the risk of creating a new Connected Account if your user tries to link a Stripe account that is already controlled by another Platform:
https://docs.stripe.com/connect/oauth-standard-accounts
I think building a backend-only Stripe App would be the best path forward here:
https://docs.stripe.com/stripe-apps/how-stripe-apps-work#backend-only-applications
https://docs.stripe.com/stripe-apps/build-backend
short lichen
does a backend-only app not need a client id and secret?
humble marsh
I'm not sure what you're referring to by client id and secret, can you elaborate?
short lichen
for Oauth
to allow people to connect their stripe account to my product
maybe it's called application ID and secret?
humble marsh
Ah, yes, OAuth does require a client_id, that's the unique identifier for your Connect Platform.
A backend-only app does not use that mechanism. Instead the Connected Account connects to your Platform, and then you can use the stripeAccount header along with your Platform's secret API key to make requests for your Connected Accounts:
https://docs.stripe.com/stripe-apps/build-backend#using-stripe-apis
Stripe Apps build on top of Connect. If you remember when we offered Extensions, Stripe Apps are essentially the new version of those.
short lichen
Connected Account connects to your Platform
how do they do that if not via oauth?
humble marsh
Oh, apologies for the confusion, they still can be connected that way.
https://docs.stripe.com/stripe-apps/api-authentication
short lichen
ok, so i'm back to my original question - what client ID and secret do I use?
I have to say Stripe doesn't feel like the easy-to-use product it started out as. I'm often lost in the docs trying to figure out which bit I need. The documentation on Oauth is quite lacking
humble marsh
The link and secret are generated for you when you create the app.
Where you can retrieve the OAuth link is discussed in this step of our OAuth guide:
https://docs.stripe.com/stripe-apps/api-authentication/oauth#create-install-link
If you're talking about the signing secret, that's also retrieved from the dashboard when creating the app:
https://docs.stripe.com/stripe-apps/build-backend#before-you-begin
If you're referring to the secret key you would use to make API requests, that is your Platform's secret key and can also be found in the dashboard.
