#dmonn_applicationfee-list
obsidian rampartBOT
👋 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/1273646543273988116
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
vocal fog
Amazing!
obsidian rampartBOT
vocal fog
Worth noting, I'm a connect platform accessing another connect platform here (which in return gives me customer data of THEIR connected account). So I'm assuming my permissions don't stretch across that many layers? This did work up until about a week ago, though.
My account ID: acct_1PiGWxQHeWAkwIc2
The connected platform: acct_1DymDdALmngAHmwM
A connected account of the connected platform, which sends the Application Fee: acct_1KssQ1CTbRJHLoLD
Since the error says The provided key '' does not have the required permissions for this endpoint on account 'acct_1KssQ1CTbRJHLoLD'
random merlin
Yeah I'm nearly positive this was never meant to be possible
We don't allow "grandfather" connect relationships
But I'm checking on it
random merlin
Can you tell me why you are doing this @vocal fog ?
Why do you need the Customer info here?
vocal fog
Can you tell me why you are doing this <@588443161358237707> ?
I'm building a small Stripe Connect analytics app (mostly for my own marketplace, which is the acct_1Dy..., but maybe as a SaaS soon?).
Based on application fees collected, I can then for example say "these are your best customers in the past 30 days".
I can do the same just through customer IDs I guess, it's just less personable, e.g. I can't reach out to my best customers directly, I need to look them up in Stripe first.
Wouldn't be a big deal. Just a really sudden change that broke things, and nothing in the changelogs 🤔
random merlin
Yeah I haven't found the change exactly but it definitely looks like something changed on our end.
The reality is that this isn't supposed to be supported but even in those cases we try not to change past behavior and break integrations.
Let me chat with some folks internally about this and then circle back
vocal fog
Sure. Thanks for that! I guess two things come to mind:
-
Based on the list of other things I'm expanding in the same way, do you see a danger of more of this being closed down? In other words – will this stop working in the near future? Why can I still access the charge, for example?
-
I noticed I can get the customer name and email under certain circumstances from the
charge.billing_detailsobject instead. Name + email is really the only thing I care about. Maybe those can be made available? Or willbilling_detailsbe removed too?
random merlin
Yeah that's what I want to talk internally about
So good questions but give me a bit to get more information here from the owning Eng team
random merlin
Just FYI it seems that you or someone from your team had contacted our Support team as well via email. That ticket just got to my team this morning but I let my teammate know to just close that ticket and that I'd handle with you here.
obsidian rampartBOT
spiral nest
dmonn_applicationfee-list
spiral nest
@vocal fog we're investigating but overall I think that behaviour is expected. We definitely should have warned you first but my advice is to stop doing this expansion logic
vocal fog
<@588443161358237707> we're investigating but overall I think that behaviour is ...
Thanks @spiral nest, will look into that. Am I right in assuming that the other expansions (charges, connected accounts, balance transaction) will follow suit? Or is this about customer data being sensitive?
spiral nest
It's a bit complex but what matters is basically where the object lives You are a Connect platorm A. You have a connected account B. As a Connect platform you are allowed to look at objects on B such as their BalanceTransactions, Transfers, Payouts, Charges, etc. But you are not allowed to look at objects on connected accounts of B. So If B is a platform (which they are since they have ApplicationFees), you can not look at objects on C that is connected to B.
When you list the ApplicationFees on B, they are "owned" by B and exist on B, so that works. When you expand the BalanceTransaction for example, that object is also owned by B since it's money moving in their own balance so that works.
But some other objects are owned by C, where the real Charge was created such as the Customer or even the Charge and those you are forbidden to expand/access.
Does that make sense?
vocal fog
Makes total sense, thanks.
spiral nest
Sure thing! Sorry for the hassle, we're still looking into what changed since this shouldn't have happened so we appreciate you flagging here!
vocal fog
Appreciate you looking into this! I'll check for what we can do here 🙂