#madeincosmos
fierce wharf
cinder token
👋 happy to help
Particularly I would like to test what happens after I authorize an App and what webhooks do I get.
could you elaborate more please?
This part seems impossible to test right now:
yes that's correct
split cave
One of the things I would like to test is to make an API call to create a payment link with application_fee_amount from inside my app
App authorizes my API calls as the account itself, not as the platform account of the connect API, so setting application_fee_amount makes no sense
For testing purposes, I could do both:
- Install the app
- Connect it via connect
Would that approximate the end experience?
And will that be the end experience? Should I design UI for nudging customers to Connect their standard accounts? Or will this be handled in UI?
cinder token
One of the things I would like to test is to make an API call to create a paymen...
that's possible
wait too many questions here
let's break it down
split cave
The document I linked in the screenshot is suggesting I somehow will get connect-like permissions when my app is in the marketplace, correct?
shell flax
Hey, stepping in here
To clarify, accounts installing your app will automatically establish a connection to the account/platform that owns the Stripe App with the permissions determined by your app manifest
So there's no need to then manually setup that connection after installation
split cave
Fantastic! Thank you
As there is no way to test this currently, should I install app for myself, and then seperately connect to the "platform" account to test some particula flows?
shell flax
Indeed, the process of installing an app on another account during development is pretty poor right now. But we're working to improve that
What specifically do you want to test?
split cave
"application_fee_amount" is kind of important for my business model 😄
I want to create a payment link within the app with application_fee_amount attached
shell flax
I guess this would be a direct charge (e.g. passing the Stripe-Account header), not a destination charge?
split cave
Correct
shell flax
So yes, in this instance as you can't really install the app on another account during testing you'll probably need to just establish a Connect relationship via OAuth or an Account Link: https://stripe.com/docs/connect/standard-accounts
Then your app should be able to create the Payment Link for that account, simulating the connection that installing the app would establish
split cave
Its totally fine for testing, I just wanted to confirm my assumption that this flow will be supported in the marketplace in the future
shell flax
Which flow?
split cave
Giving me permissions to act with Stripe-Account header
shell flax
Yep, it works today. See: https://stripe.com/docs/stripe-apps/build-backend#authenticate-requests
Just make sure you define the required permissions in your app manifest: https://stripe.com/docs/stripe-apps/reference/permissions
e.g. payment_links_write
split cave
When I usually build connect apps, I can point to the "Connect Webhooks" on platform and dont need to set up webhook urls on connected accounts
Here, there seems to be no such way, as I assume the connect webhooks URL on the platform account that owns the app will be used
But that is not explained in the documentation and that confusion has sent me here
shell flax
It's the same for Stripe Apps. You'd want a Connect webhook on the account that 'owns' the app: https://stripe.com/docs/stripe-apps/build-backend?public-private=public#receiving-events-webhooks
The underlying Connect principles are the same
shell flax
Awesome!