1900 E. Ocean Blvd, Long Beach, CA 90802
Security & Compliance

PCI Compliance Made Simple

Understanding the Payment Card Industry Data Security Standards (PCI DSS) — what it means for your business, what your obligations are, and how we help you stay protected.

PCI DSS Council Founded September 7, 2006 By Visa, Mastercard, American Express, Discover & JCB

The Standard That Protects Every Card Transaction

On September 7, 2006, the five major card brands — Visa, Mastercard, American Express, Discover, and JCB — joined forces to form the Payment Card Industry Security Standards Council and establish the PCI Data Security Standards (PCI DSS).

These standards apply to any organization that stores, processes, or transmits cardholder data for any of the major credit card brands. If your business accepts credit cards, PCI DSS applies to you.

Compliance involves completing an annual Self-Assessment Questionnaire (SAQ) and, depending on your transaction volume, submitting to quarterly network vulnerability scans performed by an Approved Scanning Vendor (ASV).

The 12 core requirements of PCI DSS are organized into 6 logical control groups, covering everything from network security and encryption to access control and monitoring. There are 9 variations of the SAQ tailored to how your business actually handles card data.

Applies to All Major Networks
Visa Mastercard Amex Discover JCB
Annual RequirementComplete your SAQ every year to maintain compliance
Quarterly ScansASV network scans required for most merchants
12 RequirementsOrganized into 6 logical security control groups
9 SAQ VariationsBased on how your business handles cardholder data

Visa's Four Merchant Levels

Your annual transaction volume determines your merchant level, which in turn dictates your specific compliance requirements and validation methods.

Level 1
Over 6 Million Transactions

Annually. Requires an annual on-site security audit by a Qualified Security Assessor (QSA) and quarterly network scans by an ASV.

1
Level 2
1–6 Million Transactions

Per year. Must complete an annual SAQ and quarterly vulnerability scans with an Approved Scanning Vendor.

2
Level 3
20,000–1 Million Transactions

Annually (e-commerce). Requires an annual SAQ and quarterly network scans. Typically applies to online-only merchants.

3
Level 4
Under 20,000 Transactions

Per year (e-commerce) or up to 1M other transactions. Annual SAQ recommended; quarterly scans may be required by your acquirer.

4

The 5-Step Compliance Process

1
Determine Your Merchant Level

Based on your annual transaction volume across all channels, identify which of Visa's four merchant levels applies to your business. Your level determines the specific validation requirements you must meet.

Levels 1–4 based on annual volume
2
Complete the Self-Assessment Questionnaire (SAQ)

Select the appropriate SAQ version based on how your business stores, processes, and transmits cardholder data. There are 9 variations. Answer all questions honestly and document your security controls.

9 SAQ versions available
3
Complete the Attestation of Compliance (AOC)

After completing your SAQ, fill out the Attestation of Compliance — a formal declaration that your business meets PCI DSS requirements. Like the SAQ, there are 9 AOC variations corresponding to your specific situation.

Completed after SAQ submission
4
Complete Quarterly Vulnerability Scans

If required by your merchant level or acquirer, arrange quarterly network scans through an Approved Scanning Vendor (ASV). These external scans identify vulnerabilities in your internet-facing systems before attackers can exploit them.

Every 90 days via an ASV
5
Submit Documents to Your Acquirer

Submit your completed SAQ, AOC, and ASV scan reports to your acquiring bank or payment processor. Level 1 merchants may need annual validation by a Qualified Security Assessor (QSA) instead of the SAQ.

Annual submission required
Submitting compliance documents electronically
RS Merchant Services compliance team working together

Our Team Helps You Stay Compliant Year-Round

We send compliance reminders, connect you with trusted ASV partners, and guide you through the SAQ process — so you can focus on running your business.

SAQ & AOC — Your Compliance Documents

Self-Assessment Questionnaire (SAQ)

The SAQ is a validation tool for merchants who are not required to undergo an on-site data security assessment. It covers all 12 PCI DSS requirements organized into 6 control groups. You must complete it annually, and the correct version depends on how your business handles cardholder data.

9 SAQ variations — choose the one that matches how your business handles card data
Attestation of Compliance (AOC)

The AOC is completed immediately after your SAQ. It is a formal attestation — signed by an officer of your company — confirming that your business meets the PCI DSS requirements applicable to your merchant type. The AOC has 9 variations that mirror the SAQ structure.

9 AOC variations that mirror the SAQ — completed together as a compliance package
Reviewing PCI compliance documentation on computer
Reviewing Your SAQ Annual questionnaire covering all 12 PCI DSS requirements
Compliance officer completing attestation
Attestation of Compliance Formal sign-off by an authorized officer of your company

The Real Cost of Ignoring PCI DSS

  • Fines & Monetary Sanctions Card brands can levy significant fines — ranging from thousands to hundreds of thousands of dollars — for non-compliance or security breaches.
  • Loss of Processing Privileges Your acquiring bank may terminate your ability to accept credit cards altogether, effectively shutting down a critical revenue channel.
  • Data Breach Liability If a breach occurs and you weren't compliant, you assume full liability for fraud losses, card replacement costs, and forensic investigation fees.
  • Lawsuits & Legal Action Customers and banks affected by a breach may pursue civil litigation against your business for failing to adequately protect their data.
  • Criminal Prosecution In some cases, business owners have faced prosecution for negligently failing to protect customer payment data, particularly in states with data protection statutes.
Cybersecurity and data protection 🔒 Security First
Federal Law Doesn't Require It. But You Still Need It.

PCI Compliance is not currently mandated by federal law in the United States. However, if you want to accept credit cards, the card brands require it — and the consequences of non-compliance can be financially devastating.

Annual compliance reminders are typically sent to merchants via email or included on their processing statement. Many processors also offer access to a compliance partner or portal to help you complete the process.

Note: Nevada has incorporated PCI DSS into state law, making it legally mandatory for merchants operating there.

PCI Compliance FAQ

Non-compliant merchants may face monthly non-compliance fees from their processor, increased transaction rates, and — in the event of a breach — full financial liability for losses, card replacement costs, and forensic investigation expenses. In the worst case, you could lose the ability to accept credit cards entirely.
The correct SAQ depends on how your business accepts and handles card data. For example, SAQ A is for card-not-present merchants who fully outsource card processing. SAQ B covers merchants using standalone terminals. SAQ D is the most comprehensive and covers all other merchants. Your processor or compliance partner can help you identify the right one.
It depends on your SAQ type and whether your systems are internet-facing. Some merchants who fully outsource payment processing (SAQ A) are not required to perform network scans. However, merchants with any internet-facing IP components that could affect cardholder data security typically do need quarterly ASV scans. Check your specific SAQ requirements or ask your compliance partner.
We send annual compliance reminders via email and processing statements so you never miss a deadline. We also connect you with compliance partners who can walk you through the SAQ, assist with vulnerability scans, and answer any questions. Our goal is to make compliance as painless as possible so you can focus on running your business.
PCI DSS is not a federal law in the United States — it is a contractual requirement imposed by the card brands (Visa, Mastercard, etc.) as a condition of accepting their cards. However, Nevada has incorporated PCI DSS into state law. Regardless of your state, if you accept credit cards, non-compliance puts your merchant account and your customers' data at serious risk.
We're Here to Help

Need Help Getting PCI Compliant?

Our team can connect you with a compliance partner who will walk you through the entire process — SAQ, ASV scans, and everything in between. We also offer a free PCI for Dummies e-book to get you started.