Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h1>No. Do not use javascript to secure credit card payments.</h1> <p>If you did, it would be trivial for someone to copy all your source code, and then poison the DNS cache or even setup phishing sites and send your users' payments into their bank account.</p> <p>Here's a scenario.</p> <ol> <li><p>You complete your website, example.com, and put everything online. Site launches, yay. You've used javascript to secure your credit card payments system.</p></li> <li><p>Someone named Nefarious Hacker notices that you're not using a tried-and true method of securing vital personal information, so he downloads all of your HTML, JS, and CSS.</p></li> <li><p>N. Hacker strips out all the js based encryption, leaving only the form. He then hosts it at evil-example.com. It looks <em>exactly</em> like your site, and behaves exactly like your site. Except that it submits unencrypted credit card data to N Hacker's database.</p></li> <li><p>N. Hacker sends out some phishing emails that point users to evil-example.com. A few users, believing the evil site to be valid, submit payments. Their credit card is now stolen.</p></li> <li><p>N Hacker is able to successfully poison a DNS cache, so some users going to example.com instead are served up evil-example.com. They have no reason to believe the site is fake (the url is what they expect), so they submit payments. Their cards are now stolen.</p></li> </ol> <p>If you had an SSL cert, the users would know IMMEDIATELY that the evil-example.com was not trusted, or that evil-example.com pretending to be example.com was fake.</p> <p>(I'll make it big so it's obvious)</p> <h1>Bottom line - <em>javascript is not secure enough to do CC payments</em>.</h1>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload