#fermentfan_webhooks
scenic hullBOT
👋 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/1290591978454646786
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
neon onyx
hi! that event would be the way, if it were possible. For Standard accounts like that one, as far as I know you don't get to see that level of information, the onboarding/PII is between them and Stripe. It would be different for Custom accounts for instance since you'd have to be involved in the KYC
in your use case I would just ask the user for their legal name in your own UI/site/onboarding instead of trying to get it from Stripe.
warm latch
Hi thanks for the answer. Funnily enough I can see the legal name if I manually request it through the API!
neon onyx
interesting
warm latch
I guess then I have to request it from the API when the webhook is called
neon onyx
possibly, though I'm surprised this works. Unfortunately we're not very clear in documentation internally or externally about what information is and is not returned for platforms of Standard accounts but my general understanding is you should not expect to see most of the KYC information and it's 'safer' to just collect what you need in your own onboarding
scenic hullBOT