#alex-connect-permissions

1 messages · Page 1 of 1 (latest)

split bluffBOT
swift wedge
#

alex-connect-permissions

#

If you use OAuth for Connect then no, it's full read all the time and optionally full write.
What you can do though is use a different integration path called Stripe Apps where you pick the exact permission(s) your app can have, see https://stripe.com/docs/stripe-apps

rotund lynx
#

Hmm, I don't necessarily need to embed in the dashboard

#

I need to be able to trigger payments on my connected accounts behalf

#

Direct charges

#

(so that it shows as them on the statement)

split bluffBOT
swift wedge
#

Stripe Apps work outside of the Dashboard

rotund lynx
#

So can I create a payment intent on behalf of an account that has my app installed?

#

(and then process it, etc)

swift wedge
#

yes

rotund lynx
#

Hmmmm

#

Okay, I might add it as another integration path

#

How does it differ to connect then?

#

Or I guess, what are the major differences?

glossy orchid
#

I would recommend reading up on Connect if you haven't already. There are too many differences between Stripe Apps and Connect for us to be able to reasonably list here. Mostly, the funds flows are a little different and the permissions you have on the account different (as mentioned above).

rotund lynx
#

Gotcha. I mean, I guess I just want to understand the fund flow differences, but I would like to have them contrasted

#

(rather than having to infer it indirectly through docs, haha)

glossy orchid
#

It really just boils down to what you're trying to do. You mentioned privacy and koopajah gave an example of how to implement a more private environment for you users. Do you have a desired funds flow you're going for?

rotund lynx
#

I guess I just want my platform to be able to trigger charges on behalf of other stripe accounts

#

The way I'm using connect right now, I'm doing direct charges

#

No intention of using destination

glossy orchid
#

That works just fine for both, so there's not a lot of difference there

rotund lynx
#

Nice! Well, I'll do some reading in the future and once I have some time, I'll probably add it as a second integration type

#

Thank you! Surprised I didn't see it earlier.

glossy orchid
#

Sure thing! Feel free to pop back in if you find some more questions about a specific integration path. Happy to help