#dan-lupashku_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1263756833579864186
๐ 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.
- dan-lupashku_api, 15 hours ago, 4 messages
It looks like I'm getting the information I already know. Can someone give me some new information please?
hello! Maybe can you share more on what new information you're looking for? Like what codename_duchess has already mentioned, you'll want to create a new account and install your app on it
is there something specific about that suggestion that wouldn't work for you?
Yes, I just don't understand, is it not possible at all to use our own app?
We will have to run some background processes that require sending API requests to Stripe.
We need to go through the oauth flow to get the access token.
While our app will be installed, we still won't be able to use it because we can't go through the oauth process.
Is that right, is there no way around this?
Hi @glossy oriole do you encounter any errors? can you share with us some screenshots so that we have a better understanding of the problem that you are facing?
I have read the docs and I understand why this happens, it's also explained on that page
The reason is that we are the developers
And the app is already installed
Ok, have you tried creating another Stripe account and install your app there?
Can you try it out?
Please try to understand my request
Are we going to be able to use the app with our own account?
maybe let me change the question slightly, have you tried using the app with your own account and are running into issues? From our perspective, if you have a Stripe App and it's installed, it should have whatever it requires to run. So are you saying that you tried the App that is automatically installed in your own account and are running into issues?
if you are running into an issue with the App installed on your own account, can you explain what your App is doing and share the specific error message that it's running into, that'll allow us to better understand what you're trying to do
https://docs.stripe.com/stripe-apps/upload-install-app#install-in-live-mode @glossy oriole have you tried this?
We can not go through the oauth flow
It's your own app, why do you need the OAuth flow?
You only need to use the OAuth flow when your app is installed in a different Stripe account.
But how should we get the access tokens?
I want us to use it as a customer would use it
So we want to have an oauth flow to get the access tokens and then make requests to the Stripe API to sync some of the information
If we can not go through the oauth flow then how can we get the access tokens that we need?
Again, you can't use the OAuth flow on your own account.
Ok, so once we publish it we won't be able to use it with our own Stripe account?
It's the same question but I just want to make sure that's the case and I'm not missing anything.
This doesn't seem right to me.
Yes you can use Stripe app in you own account, but you don't need to use the Oauth flow.
Yes - the app in the account yes
But no oauth flow?
So what is usable from the app is only what's in the Stripe dashboard.
All the other features which rely on API calls from our own services won't work because we can't go through oauth.
The app will be half broken - no data synchronization, no api calls from our servers, etc.
Is that right?
sure, thanks
I'm not sure I follow what exactly is the problem. can you clarify what is currently not working with your Stripe app? like are you getting an error message somewhere? if so, can you share it here?
No
I want to install our own app
But it says it's already installed
And I can't install it because I'm the developer
yes that makes sense
And I can not go through the oauth because of this
If I can not go through oauth then I can't make API calls
If I can not go through oauth then I can't make API calls
does it mean your app is trying to make API calls, but it fails with error message?
I can not go through oauth
if so, can you share the error message?
I can not get the access tokens
the problem is
- I need the access tokens
- I have to go through oauth to get them
- I CANN NOT GO THROUGH OAUTH BECAUSE IT SAYS THAT WE ARE THE DEVELOPER ALREADY AND WE CAN"T INSTALL IT
nr 3 is the problem - we can not go thorough oauth to get the tokens
you keep contradicting yourself.
- first you say that your app is working fine with no errors
- then you say your app is not able to make API call
so is it working or not working? and if it's not working, can you share a concrete example fo what is not working?
let me ask you this
how can I go thorough oauth with the app?
I want to get the access tokens through oauth - how can I do that?
by using the oauth link, correct?
you cannot install your own app on your own account. you would need to create a brand new Stripe account to install the app.
yes, so this is my confusion and problem
once we launch the app - we can't install it and use it for ourselves?
and there'sno way around this?
Stepping in here to assist. If you want to self-install the Stripe App on the publishing account then my understanding is that you have two ways to do that:
- Upload a test version of the app on a 2nd account marked as public so that it can be installed on your main account
- Use a 2nd account to publish and just install it into the first, with the downside that your activity is distributed across two Stripe accounts
Ok, I understand
If we go with option 2 and create a new account that we'll use to distribute the app, then:
- Would we have to go thorough the verification process with that account as well?
- Is the fact that that's a new account going to somehow impact the app distribution process?
- Is there anything else that could make things bad for us? Maybe you blocking the app because we're using a new account or something like that?
- Yes
- Not sure what you mean. It wouldn't be delayed because the account is new, no
- No it'd go through the normal review process
ok, are there any downsides that we're not aware of with this?
The main one is that as noted you'd have a separate Stripe account for app activity. That may be an issue depending on your app and how you integrate with Stripe overall. Something you'd need to assess
yeah, and I'm not very familiar with the apps
I can't find any information about this though - how would our account impact the app
or the other way around, how is the app going to impact our account
I don't understand what you're asking me. What is the purpose of your app? What does it do?
The main purpose is to sync our customers Stripe data with our CRM (We're a SaaS company)
For starters the app won't have any interactions within the Stripe dashboard - we're just going to make API calls to sync some of the data
Then it shouldn't really be an issue then
And we are using our own app for ourselves, for sales. We'd also like to use the App we're building as well.
Ok, I get this.
We could use a new account for this.
However, would we be able to use the same account if we use a different authentication method? Let's say by using Restricted API keys?
In that case I guess we could do it since from what I understand only the oauth flow is not working for our own app, but we should be able to use restricted api keys because the app would already be installed in our account, right?
No, you can't self-install the app regardless of the auth method used
It is "installable" only in test mode?
No, I explained how it can be installed in livemode
But you just said that we can't self install the app
Ok, so I think there's a confusion.
Do you mean that we can not:
Self-install by going through the regular flow of approving the app,
BUT
We can still use the app because it is going to be installed in our account through the upload process?
Both the solutions I provided require a 2nd account, yes: #1263756833579864186 message
I'm reading this: https://support.stripe.com/questions/why-cant-i-install-an-app#:~:text=You are not an Administrator,your role in each account.
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
"You cannot install an app on the account that has published it through the Marketplace. The app will already be installed on your account through the upload process"
So if the app is going to be in our account because of the upload process then why can't we use the Restricted API Keys authentication?
Is it because the customers can get they keys only once, at the instal ltime?
It'll be 'installed', but non-functional if that makes sense. That is my understanding
Okay, I see
thank you
and thank you for your patience
I have no more questions ๐
Of course, np! Let us know how you get on
Actually one more ๐
sorry
So all we want to do is actually synchronize some stripe data with the CRM.
We don't care about anything visual in the Stripe dashboard.
Is creating an app the right way to do it or is there a better way?
Yes you're essentially describing what was once called an 'extension'. Which reads data from Stripe accounts without actually charging payments. Extensions are deprecated now, and replaced by a Stripe App
ok, thank you