This fall we saw some major announcements regarding changes in the way future POS credit card transactions were going to be processed. In October, MasterCard announced it would no longer require signatures at point-of-sale transactions in the U.S. and Canada beginning in April 2018. Shortly thereafter, Discover announced similar intentions, requiring no POS signatures, expanding this initiative to not only the U.S. and Canada, but also Mexico and the Caribbean. Not to be left behind, AmEx announced in early December it would also implement this change in April 2018 on a global scale. At this time, VISA is the lone holdout, still requiring signatures at point-of-sale. Odds are the antiquated signature requirement will be dropped by Visa soon considering that it is difficult to prove that the signature was indeed the cardholder’s.
Wow, seems like everything’s changing so fast with payment processing. First, you have ApplePay becoming a strong market player. Then you have the EMV Chargeback Liability shift coming up this fall.
Just one of those is enough to handle. So let’s throw PCI compliance right on top of that! Don’t worry – we got your back. With Solupay's dedicated relationship managers and our overall approach to ensuring PCI with our clients is handled, and not seen as a revenue opportunity, we have made PCI compliance a breeze.
In the article “PCI DSS 3.1 set for April 2015 release, will cover SSL vulnerabilities,” Tech Target announced the following that we felt important to share with our subscribers regarding PCI DSS 3.1, which was published a few days ago. PCI DSS 3.0 is scheduled to retire on June 30, 2015:
January 1, 2015 marked the official date that PCI DSS 3.0 became mandatory for merchants. There have been numerous articles speculating how this will impact merchants' success at passing compliance with their PCI Qualified Security Assessors (QSA). The new security standards were designed to eliminate the increasing prevalence of large scale breaches, but have caused some confusion and concern in smaller merchants, who struggle balancing costs vs. risks.
In a sneak preview of its 2015 PCI Compliance Report, the managed IT services giant, Verizon, hinted at two key problem areas that cause merchants to fall out of PCI DSS compliance: Struggling to maintain PCI Compliance year round, and firewalls.
Merchants accepting credit/debit cards for payment are required to become compliant with the Payment Card Industry Data Security Standards (PCI DSS). It is YOUR responsibility, as a merchant accepting credit and debit card payments, to safeguard customer card data by becoming PCI compliant.