#noooooproblem_unexpected
tribal pantherBOT
👋 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/1432438631242404024
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
solid parcel
Hello 👋
Can you provide the ID of the account so I can check how it was created?
tribal pantherBOT
lapis hedge
Hello
That's your Platform account or the Connected Account ID?
late nova
ConnectAcccount ID
lapis hedge
That account was created back in 2022
Do you allow OAuth onboarding to your Platform account? If so, the flow might've been used to connect an existing account
late nova
sorry about that, that was the wrong one
acct_1SLERcIbdJ41QKRv
this is the one that im looking for
lapis hedge
That account was created by your Platform using your secret API key - https://dashboard.stripe.com/acct_1M4T2pIERcTyk3MX/logs/req_VJNdp7fJPDKC6i
late nova
yea i see that as well, which was very concerning
lapis hedge
If you don't recognize the IP address/user-agent then it's possible that your key was leaked & in that case, I'd strongly recommend rolling your Private/Secret API key
late nova
i already have changed the keys and much more
just dont understand how it could be leaked in any shape or form
that IP address is most def fake as well
lapis hedge
Yeah, unfortunately we don't have visibility into how it got leaked
The common pattern is someone using it on the client-side application or mistakenly publicly logging it
late nova
is there any measure stripe recommends on cases like this