#kaintr_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1258052697211404321
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
Hello
There's no additional auth involved from Stripe in this case.
So if you're asking about if you should be authenticating the connected accounts on an application level yourself? The answer is yes.
So if I map authid (in my DB) to their stripeId and ensure that when calling my API we authenticate the user then it's fine that we then use the Stripe ID ascosiated with their account and this is all the authentication required?
Or is that insecure?
(I'm using Supabase)
Object IDs are useless without the API key. So storing the Stripe account IDs in your database should be fine as long as your API key is securely stored.
Okay so the ultimate security flaw would be exposing the API Key (which I will make sure doesn't happen)
Thank you very much ๐
NP! ๐ Happy to help
If I have more questions should I post here or go through the same way I posted this original question?