#phillip-objectIDs
1 messages · Page 1 of 1 (latest)
hi there! it's fine to have PaymentMethod IDs in the frontend. There's no sensitive information in the PaymentMethod ID itself, nor can any sensitive information be retrieved using the PaymentMethod ID without a secret key
Is there any object ID's that I should be careful with passing to the front end? I currently have paymentMethods ID's, subscription ID's, product ID's, price ID's, etc
I guess the main concern is the possibility of people being able to use this info for any exploits?
no specific object ID comes to mind. There are specific fields which are retrievable via the publishable key but they are non-sensitive info. Fields which are retrievable using the publishable key are explicitly mentioned in the API docs saying RETRIEVABLE WITH PUBLISHABLE KEY e.g. https://stripe.com/docs/api/payment_intents/object The only thing which you want to make sure you never expose is your API secret key.
Thank you for the quick response! I appreciate your help