#jeremy_code
summer canopyBOT
đ 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/1244839826218291221
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
mint vector
Client secret is fine to be exposed at frontend. It's meant to render the Payment Element to collect the payment method details for a specific payment intent
Client secret can't modify the Payment Intent details
digital fable
I submitted part of my code to google gemini. It said I should never expose the client secret on the front end. This is why I am checking. I used the stripe example as a starting point and want to make sure the code is safe
mint vector
Thanks for sharing the information. Sharing the client secret is safe as it is needed for the Stripe Elements at frontend
Client secret has restricted access to the payment information
digital fable
Thank you for putting my mind at rest. You can close the thread now.