#bodhi-hawken_conenct-identify-verification
frank stagBOT
👋 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/1368983951095496834
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
static rover
Hi 👋
Can you share an API request ID that shows the error you are receiving? It will start with req_
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
potent kite
req_xF4RkIv9EzCEBN
just for reference i am able to make all other relevant calls for our connected platforms
create payments customers ect
and although the error mentions oAUTH i can’t find any docs pointing towards how we can get extra access with it. seems like a red herring
static rover
The Oauth error does indeed appear to be a red herring. Since standard accounts have full access to the Stripe dashboard, I don't think the platform can make identity verification calls on their behalf>
What is the overall flow you are attempting to build?
potent kite
our connected accounts would like to verify the ID of some of their customers
we manage the platform and we’re adding a customer verification feature for them. the most secure way that keeps all the customer data in their account would be to do that by making the calls in their account
it also keeps the billing in their account so we don’t have to add that on top
static rover
Ah okay I did some digging and it looks like this is a feature that is not generally available to Connect Platforms
potent kite
is it a feature that can be enabled or should we just do the good old API key copy instructions?
static rover
You should absolutely avoid API key copying. That is not a practice we recommend and we actively discourage users from sharing their API keys with service providers.
I recommend you reach out to Support to see if there is a way to enable that for your account.
potent kite
absolutely agree but if it’s the only option 🤣
but great, sounds like it’s a feature that can be made available to us
i’ll reach out
is there an email for the relevant identity team i should go too?
static rover
Not specifically. You should just try to thoroughly explain your use case and exactly what APIs you are using. Include the example request you provided to me. That will help the first tier of support route your question to the appropriate team.
potent kite
darn! that maze is always infuriating to navigate! cheers though! thanks for your help!
static rover
I can definitely sympathize! However, I find that a decent amount of the issue with getting questions to the right staff has to do with questions not being clear in their details.
One thing to keep in mind is that our staff (myself included) are trained on Stripe technologies and policies. So we can more readily help if your questions are focused on you work with Stripe APIs and tooling.
When users start with vague questions about business models that don't easily map to Stripe product, that is when it gets hard to know how to help.
potent kite
thanks for your help, i shall do the dance with support!
static rover
Best of luck!
frank stagBOT