nathina_api

[tame wren]

👋 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/1284036648564162624

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[torpid ibex]

hello, if you're using Stripe Elements (a.k.a Stripe.js) to collect card details in the browser, that's totally normal.

The browser runs on your computer and you type your card details in your browser (in our card element or PaymentElement). Since the card details are typed into the browser by hand, it's normal that the browser sees the card number. And then the card details need to go to Stripe in some way and that's done via one of our APIs. The information is not "sent in plaintext". It's encrypted since it's an HTTPS request and no one can see what's in it but Stripe on the way.
The browser can see the card details, because it's typed there. So it's normal that if you inspect the network request in Chrome, you can see them in clear text. No one can get them unless they already have access to the computer. Either by standing next to the you, or by having infected the computer, but in that case the malicious application would already be able to see what you type.

[short jetty]

okay sir, this is our development environment here also i able to see the card details in the payload is it normal ?

[torpid ibex]

yes that's normal

[short jetty]

so you meant this one is safe right?

[torpid ibex]

yes, it's safe

[short jetty]

okay, Thank you so much sir