#nimheru_api
plain vergeBOT
đ 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/1275100580632858725
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
crisp dirge
Hello, no that's not possible. Since Standard Accounts have a direct relationship with Stripe (they control via their own Dashboard), you don't manage this data for them.
meager coral
we provide a marketplace platform for event organisers to sell tickets to customers and as part of purchase/refund notification emails we include the support email address or phone number for the customer to contact the organiser
Stripe labels the support email as "A publicly available email address for sending support issues to."
crisp dirge
Gotcha, generally if you are going to manage this data for your users then you would use Custom/Express accounts.
meager coral
We arent looking to manage it, just view it
crisp dirge
Stripe labels the support email as "A publicly available email address for sendi...
Yeah because we expect the Standard Account to be the Merchant of Record here and for them to manage their email/phone
And if you were using Stripe receipt emails then that email/phone that they set would be provided
But sounds like you are using your own custom emails here
meager coral
We use both currently
So theres no way we can get read only visibility on this info? Even though we could via api keys?
crisp dirge
Yeah that's correct
meager coral
Do you have any links to further reading on this as Im struggling to find it documented anywhere (e.g. there's no mention of this limitation here; https://docs.stripe.com/api/accounts/object#account_object-business_profile)
crisp dirge
Not really -- https://docs.stripe.com/connect/accounts#standard-accounts details the high level idea that Standard Accounts manage their own settings (like support phone/email) and that you don't do that as the platform in this case.
But it doesn't explicitly layout the properties that will be avialable/hidden from you as the platform
meager coral
The email from stripe that prompted us to look at migrating to querying the account via our Connect api key instead of the account's own api keys mentioned "restricted api keys" but this appears to only be relevant to Stripe Apps and not Connect is that right?
crisp dirge
Not positive about the specific email but unless you are running a restricted key Stripe App (https://docs.stripe.com/stripe-apps/api-authentication/rak) then we highly recommend using your own platform key + Stripe Account header and never accessing the keys of your Connected Accounts
meager coral
stripe still provides them as part of the oauth "Complete the connection and get the account ID" step https://docs.stripe.com/connect/oauth-reference?locale=en-GB#post-token, are these going to disappear at some point then?
crisp dirge
There are no plans to fully deprecate that right now -- you would receive communication ahead of time if that was the case. But the recommended flow is to not use that access token.
meager coral
Ok understood, we want to move away from using them but we also want to make sure we are providing the right info to our customers (making sure they have the right contact info for an event organiser), we'll need to look at another way around it then
I understand the restriction but can I ask that its raised as a feature request that Connect applications can get access to "publicly available" or "customer-facing" properties of an account?
crisp dirge
Yep happy to submit that feedback