#reginbald_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ 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/1215303933220622346
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
No nothing wrong with that really if you want to do that. Object IDs really aren't sensitive -- you can't do anything with them unless you have the secret API key for the account where the object was created/is stored.
So mostly just never share your secret key, but setting object IDs as metadata is fine if you have a use-case for that
Only thing I'll say is that might get confusing...
I might recommend just creating your own UUID and setting it on both Customers' metadata
But up to you really
Ok great! thanks, I'm just trying to look up the customer in the connected account that is the same user as the customer in the platform account
so perhaps I should just use the user id
I can see that the Stripe dashboard replaces the customer id with a link to the customer page in the platform account which might be convenient for debugging
It creates a link to the platform Customer if you set the Customer as metadata?
(We don't actually know much about the Dashboard as we just focus on the API)
Yeah, I can send you a picture if you want
Nah that's okay. But that's interesting! I didn't know we did that to be honest.
So that might be a good thing if you are working against the dashboard and need to see the "source" customer
Yep that does seem helpful
Thanks for the help ๐
Sure!