The credit card diagram above shows where sensitive cardholder data is listed on a credit card. Those that collect, process, store, or transmit payment card transactions must complete and maintain the strict processes of maintaining PCI compliance. Note that those entities involved with payment card transactions can never save sensitive authentication data after authorization. This includes the 3 or 4 digit security code printed on the front or back of a card (CVV), the data stored on a card’s magnetic stripe or chip (also called “Full track data”), or personal identification numbers (PIN) entered by the cardholder.
PCI standards apply to many financial systems such as:
- Point-of-sale systems
- Store networks and wireless access routers
- Card readers
- Payment card data stored in paper-based records
- Online payment applications and shopping carts
- Payment card data storage and transmission
Becoming PCI compliant and maintaining that compliance can be a rigorous process; it can involve hiring an expensive third-party consultant to install costly software and hardware, enforcing new security controls, and even agreeing to a contract that makes you agree to the bank’s terms for annual PCI compliance, completing annual self-assessments(which are often not in your best interest), and more.
Please refer to the PCI Small Merchant Guide to Safe Payments to get more information about how you can better protect payment card data and your business..
What are the PCI compliance levels and requirements?
If your business takes payment cards with any of the five members of the PCI SSC credit card brands (American Express, Discover, JCB, MasterCard, and Visa), then you are required to be PCI compliant, which is determined by your annual transaction volume. For example, sellers with a higher volume of transactions are mandated to work with internal security assessors (ISAs), qualified security assessors (QSAs), and PCI-approved scan vendors (ASVs).
There are four different levels of compliance which establish the requirements that sellers are responsible for maintaining. The PCI Council regards a business as “in compliance” by meeting 100% of the criteria. Because of this complex responsibility, many large businesses work with a PCI-compliance consultant on requirements and how to meet these PCI-compliant level standards. While each credit card brand has its own slightly different criteria, generally the PCI-compliance levels are as follows*:
PCI compliance levels
Merchant Level |
Applicable to |
PCI Requirements* |
1 |
1) Sellers that process over 6M transactions per year |
|
2) Any merchant that has had a data breach or attack that resulted in an account data compromise
3) Any merchant identified by any card association as Level 1 |
Annual Report on Compliance (ROC) by a Qualified Security Assessor (QSA)—also commonly known as a Level 1 onsite assessment—or internal auditor if signed by officer of the company |
Quarterly network scan by Approved Scan Vendor (ASV)
Attestation of Compliance form |
|
|
|
|
2 |
Sellers that process 1M to 6M transactions per year |
Complete the PCI DSS Self-Assessment Questionnaire according to the instructions it contains |
Complete and obtain evidence of a passing vulnerability scan with a PCI SSC Approved Scanning Vendor (ASV)
Complete the relevant Attestation of Compliance in its entirety (located in the SAQ tool)
Submit the SAQ, evidence of a passing scan (if applicable), and the Attestation of Compliance, along with any other requested documentation, to your acquirer |
|
|
|
|
3 |
Sellers that process 20,000 to 1M e-commerce transactions per year |
Complete the PCI DSS Self-Assessment Questionnaire according to the instructions it contains |
Complete and obtain evidence of a passing vulnerability scan with a PCI SSC Approved Scanning Vendor (ASV)
Complete the relevant Attestation of Compliance in its entirety (located in the SAQ tool)
Submit the SAQ, evidence of a passing scan (if applicable), and the Attestation of Compliance, along with any other requested documentation, to your acquirer |
|
|
|
|
4 |
Sellers that process fewer than 20,000 e-commerce transactions and all other sellers that process up to 1M transactions per year |
Complete the PCI DSS Self-Assessment Questionnaire according to the instructions it contains. |
Complete and obtain evidence of a passing vulnerability scan with a PCI SSC Approved Scanning Vendor (ASV)
Complete the relevant Attestation of Compliance in its entirety (located in the SAQ tool)
Submit the SAQ, evidence of a passing scan (if applicable), and the Attestation of Compliance, along with any other requested documentation, to your acquirer. |
*Each of the five payment brands has its own data security programs that require merchants to safeguard credit card processing data. Here’s a helpful example of Visa’s PCI DSS requirements.
What are the consequences for noncompliance?
If you aren’t aware of all the rules around PCI compliance or the punishment for being noncompliant, you’re not alone.
Even though PCI compliance is not a law, that doesn’t take the burden away from your business. According to the Identity Theft Resource Center’s 2021 Data Breach Report, there were 1,862 data breaches last year, which is higher than both 2020’s total of 1,108 and the previous record of 1,506 set in 2017. This emphasizes the importance of ensuring that your payment processing life cycle is secure.
If your business is not compliant with PCI standards, you could be at risk for data breaches, fines, card replacement costs, costly forensic audits and investigations into your business, brand damage, and more if a breach occurs.
In fact, a study was done that illustrated that approximately 30% percent of small businesses report that they don’t know the penalties for noncompliance with PCI DSS 3.0.
Penalties are not highly publicized, but they can be horrific for businesses. For example, if your company violates PCI-compliance standards, credit card brands can charge fines from $5,000- $100,000 per month to your acquiring bank. The banks often deny liability and these fees are now the merchants responsibility. Even after being charged the fee, banks can terminate contracts or charge higher fees for transactions after reports of your company’s breaches and violations.
Disregarding the financial cost, there are also even greater potential liabilities that could affect your business. According to PCI Security Standards, failing to comply with PCI standards and resulting data breaches could result in:
- Lost confidence, so customers go to other merchants
- Diminished sales
- Cost of reissuing new payment cards
- Fraud losses
- Higher subsequent costs of compliance
- Legal costs, settlements, and judgments
- Fines and penalties
- Termination of ability to accept payment cards
- Lost jobs (CISO, CIO, CEO, and dependent professional positions)
- Going out of business