#Selakyn-client-side-checkout
modest lake
Hi, thank you
trail sail
are there any specific docs you're looking at, at the moment?
modest lake
My problem is, I see everytime that people make a request on an express server and then create the checkout. I removed the server part and enable only the client-side
modest lake
are there any specific docs you're looking at, at the moment?
yes wait
below
I enable the client-side
trail sail
Gotcha. Thanks for sharing.
As far as I understand client-only checkout, there shouldn't be much to worry about. Even if someone gets access to product IDs, they'd need access to your secret keys in order to update them.
But yes, It may lack features compared to client-server integrations and Payment Links.
modest lake
Okey I see. In the browser we can see for example the quantities and the ids of items that some client want to purchase. Is there any way to change theses values directly on the source code ? And an other question, is there a way that someone find the secret key ? it will be in a .env file but won't be pushed on github.
trail sail
In the browser we can see for example the quantities and the ids of items that some client want to purchase. Is there any way to change theses values directly on the source code ?
I'm not sure I understand the question. Can you give me an example?
is there a way that someone find the secret key ? it will be in a .env file but won't be pushed on github.
As long as you don't share your Stripe account credentials with anyone, you should be fine
modest lake
> In the browser we can see for example the quantities and the ids of items that...
I find that answer of my first question haha. And thanks for the second!
Thank for your help !