Open dan-massey opened 3 weeks ago
I think I see where you're coming from here. Let me confirm your circumstance:
https://dashboard.stripe.com/${isTest ? "test" : ""}/connect/${accountId}
view Is this correct?
Side note, I ddin't know it was possible for a parent account to install an app on behalf for all their connected accounts, except when using the Connected Apps beta using a custom (non-stripe) dashboard. This could be an interface bug where your app is shown in the Stripe sidebar in the connected account view when it shouldn't be.
Yes, that's what I saw.
I've only reproduced this in test mode in the connect account I'm developing my app in, with the app installed in test mode. I don't know if it occurs when an end user installs the app from the marketplace.
I'm also not sure what the intended behavior is.
(If it's intended that Marketplace apps can be installed by a Connect account on behalf of all connected accounts and it becomes possible for the installed app to work correctly, it would be great to get enough information to be able to charge an account a subscription based on total number of accounts.)
I'm still working on a Stripe Apps Production example app that would facilitate charging for an app.
You don't have access to your connected accounts' connected accounts.
But say you offer a required login within your app to your microsite to facilitate payments for your app's subscription or usage; this is the direction you'd need to go. Imagine, say, your app has a login button. The login button would lead to a microsite automatically creating a Stripe User. This Stripe User would live in your API. Your user would also live as an actual user in another Stripe Company (from there, you could charge a subscription or usage fee). My example app is still a few months away. I met with the Stripe Apps team about this issue, and I know it's now on their roadmap...so they may offer their own solution. Give me a little patience, and I'll publish my production-ready example:
The example has these features:
Is your feature request related to a problem? Please describe. I'm struggling to make my app work correctly with Connected accounts viewed through the dashboard of the parent Connect account.
stripe.dashboard.customer.detail
viewportA1
, Account IDacct_1IfGs2KHtUMqOYFU
)extensionContext
extensionContext.environment.objectContext.id
and the account ID ofA1
from theextensionContext.userContext.account.id
A1
, e.g./test/customers/cus_OGAUOfA0Iey1jj
C1
with Account IDacct_1Q3W5yGfrzfb7Jof
) , e.g. by going to/test/connect/accounts/acct_1Q3W5yGfrzfb7Jof/customers/cus_QvMqTWzSvF9Gxm
extensionContext.userContext.account.id
gives me the Account ID ofA1
notC1
A1
s Account ID and the API call is rejected.Describe the solution you'd like Either:
stripe.dashboard.customer.detail
viewport in it's within a connected account (to stop it from being broken)