summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorP. J. McDermott <pj@pehjota.net>2015-03-16 22:40:07 (EDT)
committer P. J. McDermott <pj@pehjota.net>2015-03-16 22:40:07 (EDT)
commit1333c614c0d1ff67a1e1ff7f16db275c610218cf (patch)
treed1e1194eb5c87723a71c337d9ce73dd17b3cbf88 /README
parente11cb0820f20d0c847961b47282fc98110b5fd86 (diff)
downloadepirts.js-1333c614c0d1ff67a1e1ff7f16db275c610218cf.zip
epirts.js-1333c614c0d1ff67a1e1ff7f16db275c610218cf.tar.gz
epirts.js-1333c614c0d1ff67a1e1ff7f16db275c610218cf.tar.bz2
README: Describe the state of free payments
Diffstat (limited to 'README')
-rw-r--r--README6
1 files changed, 5 insertions, 1 deletions
diff --git a/README b/README
index ea118ee..0c8f057 100644
--- a/README
+++ b/README
@@ -103,7 +103,11 @@ Stripe's payment page.
Therefore, under PCI DSS 3.0, **Epirts.js may not be used to process live
payment cards without first completing PCI SAQ A-EP and having an ASV perform
-quarterly vulnerability scans**.
+quarterly vulnerability scans**. Currently, the only way to control your
+store's checkout process and ensure that no non-free JavaScript programs are
+distributed to your customers is to use a program like Epirts.js (or process
+cardholder data directly on your server) and pay for a scanning service. Such
+is the state of payment processing.
Copyright Information
=====================