#backenddev_55020
mystic raftBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- backenddev_55020, 20 minutes ago, 11 messages
indigo trellis
hi there!
that's completely up to you
the main secret key allows your application to do anything with Stripe. a restricted key (like it's name implies) will restric what is possible to do
high root
ok .. what is the use of publishable key if its used by frontend only (webapp , mobile app) , as they interact with only the backend (i.e server endpoint) ..
indigo trellis
it depends on how you integrate with Stripe.
for example when using the Payment Element, you need to create a PaymentIntent on the backend (which requires a secret key), and ocnfirm the PaymentIntent on the frontend (which require a publishable key).
but if you use Checkout Session (for example), then you only need a secret key.
high root
yes , we intend to use only checkout session (as of now ) in our stripe integration .. we are building a website where user can do one time payment to purchase goods .. new microservice i am building will implement a server endpoint for invoking checkout session API towards stripe ... so as per your suggestion i can use secret key as well ... right ?
indigo trellis
either secret key or restricted key. both can work.
high root
ok thanks
indigo trellis
happy to help 🙂