#cruso
1 messages ยท Page 1 of 1 (latest)
Hi ๐
You can proceed to develop a back-end only Stripe App. The app will still need to be installed through the Marketplace and the user will need to use the UI to accept the permissions your app requests.
But otherwise you should be able to do that.
So there would be no way for us to trigger the integration flow from our own platform?
ฤฑ.e. connect with stripe button
No, you can only direct them to your app in the Marketplace
Are there any alternative tools we can use for this flow? Or is there a special link to our app so that we can help the user find our app on the marketplace?
Also as far as I understand the Marketplace isn't open to public yet. In this case there is no way for us to take this application live without waiting on the waitlist?
I.e. can we use connect to enable this functionality or would that be "bad practice"?
Correct, this is still in beta.
Honestly I wish we didn't deprecate Connect Extensions without the Stripe Apps marketplace being open and stable.
You_could_ enable this functionality with Connect and just use OAuth to link accounts
Oh okay. That would work for us.
In that case, should we go for a standard, express or a custom app you think?
Considering we will not utiilize any payment etc functionality and only need the oauth flow, I guess a custom app makes sense?
Well for Connect Extensions you are usually linking already existing Stripe Accounts to your service. So in that case they would be Standard accounts. Or were you planning on creating new Accounts?
No you are right. We only need existing Stripe Account holders to give us consent through Oauth. No need for new account creation.
Okay then those are Standard Accounts ๐
Perfect thanks ๐
For authentication I see there is Oauth and also "Connect Onbaording"
would we proceed with Oauth in this case?
(Sorry for all the questions, I geniunely am a little confused and couldn't find the right answers myself)
Yes for Connect the only way to link an existing account is really using the OAuth link
Ok that makes sense
We will proceed with this flow then. Thanks a lot for your help.
Lastly, are there any other tips / pitfalls we should watch out for in our case?
The only thing I can think of is that OAuth uses generic read and read_write permissions. When Stripe Apps is mature and you want to migrate they will use granular object permissions. It's something to keep in mind.