If your payment platform already has PCI DSS locked down but enterprise deals keep stalling at the security review stage, we've seen this pattern dozens of times — and SOC 2 is almost always the missing piece. Here's how we guide payment processing companies through it.
Key Takeaways
- •Payment processing companies, payment gateways, and merchant services platforms need SOC 2 in addition to PCI DSS because the two frameworks serve fundamentally different audiences.
- •For the next operating decision, compare compliance for technology companies with managed compliance services.
- •PCI DSS and SOC 2 are complementary — not interchangeable — frameworks.
Payment processing companies, payment gateways, and merchant services platforms need SOC 2 in addition to PCI DSS because the two frameworks serve fundamentally different audiences. PCI DSS satisfies card network requirements and demonstrates cardholder data protection. SOC 2 satisfies enterprise buyer trust requirements and demonstrates that your organization's broader security controls — access management, change management, incident response, vendor oversight, and operational monitoring — are designed and operating effectively.
For payment companies selling to enterprise merchants, platforms, or financial institutions, SOC 2 has become a standard procurement requirement alongside PCI DSS.
This guide covers how to build a SOC 2 compliance program specifically for payment processing companies that already maintain PCI DSS compliance.
For the next operating decision, compare compliance for technology companies with managed compliance services. Confirm the work included, the evidence you need, and who will own implementation before committing to a provider.
Why Payment Companies Need Both SOC 2 and PCI DSS?
PCI DSS and SOC 2 are complementary — not interchangeable — frameworks. Understanding why enterprise buyers require both helps you prioritize and communicate your compliance position.
Different Audiences, Different Purposes
| Dimension | PCI DSS | SOC 2 |
|---|---|---|
| Who requires it | Card networks (Visa, Mastercard, etc.) and acquiring banks | Enterprise merchants, platforms, and financial institution partners |
| What it covers | Cardholder data environment (CHD and SAD) | Entire service delivery system including people, processes, and technology |
| Focus | Protecting payment card data specifically | Demonstrating organizational security maturity broadly |
| Assessment type | Self-assessment or QSA assessment | CPA firm attestation |
| Report format | Report on Compliance (ROC) or SAQ | SOC 2 Type I or Type II report |
| Buyer usage | Verified during onboarding; rarely reviewed in depth by merchants | Read in detail by security teams during procurement evaluation |
The Gap PCI DSS Does Not Fill
PCI DSS is scoped specifically to the cardholder data environment — the systems, networks, and processes that store, process, or transmit cardholder data. It does not evaluate your broader organizational security practices: how you manage employee access across all systems, how you handle change management for non-payment infrastructure, whether you conduct risk assessments beyond the CDE, or how you manage third-party vendors who do not touch cardholder data.
In our experience working with payment companies, this gap is where enterprise deals get stuck. Enterprise buyers — particularly large merchants, e-commerce platforms, and financial institutions — need assurance that your entire organization operates with security discipline, not just the payment-processing components. SOC 2 provides this broader view. We regularly see payment companies with PCI DSS but no SOC 2 struggle to close enterprise deals where the buyer's security team evaluates vendor security holistically.
How do SOC 2 and PCI DSS controls overlap?
Organizations already maintaining PCI DSS compliance have a significant head start on SOC 2. We tell our clients this is one of the best leverage points in compliance — you've already done the hardest technical work.
Overlap Map
| Control Area | PCI DSS Requirement | SOC 2 Equivalent | Overlap Level |
|---|---|---|---|
| Access management | Req 7: Restrict access by business need | CC6.1-CC6.3: Logical access controls | High |
| Authentication | Req 8: Identify users, authenticate access | CC6.1: Authentication mechanisms | High |
| Encryption (transit) | Req 4: Encrypt transmission over open networks | CC6.7: Transmission security | Full |
| Encryption (at rest) | Req 3: Protect stored cardholder data | CC6.1: Data protection | High |
| Logging and monitoring | Req 10: Log and monitor access | CC7.1-CC7.2: Monitoring and anomaly detection | High |
| Vulnerability management | Req 6: Develop secure systems | CC7.1: Vulnerability identification | Moderate |
| Network segmentation | Req 1: Network security controls | CC6.6: External threat protection | Moderate |
| Physical security | Req 9: Restrict physical access | CC6.4: Physical access controls | Moderate |
| Incident response | Req 12.10: Incident response plan | CC7.3-CC7.5: Incident management | Moderate |
| Security policies | Req 12: Security policies and programs | CC1-CC2: Control environment, communication | Moderate |
Where SOC 2 Goes Beyond PCI DSS
SOC 2 requires several control areas that PCI DSS does not address (or addresses only minimally). We recommend our payment processing clients pay close attention to these gaps early, since they represent the bulk of your incremental work:
- Formal risk assessment methodology: SOC 2 requires a documented risk assessment process with risk registers and treatment plans beyond PCI DSS's risk assessment requirement
- Vendor management program: SOC 2 expects security assessments of all third-party vendors, not just those in the cardholder data environment
- Change management formalization: SOC 2 requires documented change management controls with approval workflows across all in-scope systems
- Employee lifecycle management: SOC 2 evaluates background checks, security training, and offboarding for all employees, not just those with CDE access
- Board/leadership security oversight: SOC 2 expects evidence that security is discussed at the organizational leadership level
- Business continuity and disaster recovery: SOC 2 evaluates broader continuity planning beyond PCI DSS's CDE-focused requirements
- Independent CPA attestation: SOC 2 requires a CPA firm report; PCI DSS uses QSA assessment or self-assessment
Trust Service Criteria for Payment Platforms
Choosing the right Trust Service Criteria is critical for payment processing companies. Enterprise buyers in the payments industry have specific expectations, and we advise our clients to think carefully about which criteria to include from day one.
Recommended Criteria
| Criterion | Recommendation | Reasoning |
|---|---|---|
| Security (Common Criteria) | Required for all | Mandatory for every SOC 2 audit |
| Processing Integrity | Strongly recommended | Validates transaction accuracy, completeness, and authorization — core to payment platform value |
| Availability | Strongly recommended | Validates uptime and reliability commitments critical for payment processing |
| Confidentiality | Recommended | Validates protection of merchant data, transaction records, and business intelligence |
| Privacy | Situational | Required if you collect or process consumer PII directly (beyond card data) |
Processing Integrity: The Critical Criterion for Payments
Processing Integrity is the criterion that distinguishes payment company SOC 2 reports from generic SaaS SOC 2 reports. It evaluates whether your system processing is complete, valid, accurate, timely, and authorized — precisely the assurances enterprise merchants need when routing transactions through your platform.
Processing Integrity controls specific to payment platforms:
- Transaction completeness: Controls that ensure all initiated transactions are processed and no transactions are lost, duplicated, or dropped
- Transaction accuracy: Validation that transaction amounts, currencies, merchant identifiers, and settlement figures are processed correctly
- Transaction authorization: Verification that every transaction is properly authorized before processing and that unauthorized transactions are rejected
- Settlement accuracy: Controls ensuring that merchant settlements reconcile accurately with processed transactions
- Error detection and correction: Automated systems that identify processing errors, transaction discrepancies, and reconciliation failures with defined correction procedures
- Processing audit trails: Complete, immutable records of every transaction from initiation through settlement
Without Processing Integrity, your SOC 2 report documents generic security controls but does not directly address what enterprise payment buyers care most about: whether your platform processes their transactions correctly and reliably. We strongly recommend every payment processing company include it.
Scoping Challenges for Payment Platforms
Payment processing infrastructure has unique characteristics that create scoping challenges for SOC 2 audits. We help our clients navigate these early so there are no surprises during the audit itself.
Tokenization Vaults
If your platform uses tokenization to protect cardholder data, the tokenization vault occupies a unique position in your SOC 2 scope:
Payment Rails and Third-Party Processors
Payment platforms often connect to multiple payment rails (card networks, ACH, wire transfer systems) through third-party processors and financial institution partners. For SOC 2 scoping:
- Complementary User Entity Controls (CUECs): Document which security controls your merchants and partners must implement on their end
- Subservice organization considerations: If you rely on third-party processors for core transaction processing, their SOC 2 report (or lack thereof) affects your report. You must either use the inclusive method (incorporating their controls into your report) or the carve-out method (excluding them and noting the dependency)
- API security boundary: Your APIs that connect to payment rails must be in scope, with controls around authentication, rate limiting, input validation, and error handling
Settlement Systems
Settlement and reconciliation systems present scoping considerations because they handle financial data that directly affects merchant revenue:
- Settlement calculations must be in scope if Processing Integrity is included
- Reconciliation processes between transaction processing and merchant settlements should be documented as controls
- Settlement timing (daily, weekly, custom schedules) must be accurately described in the system description
Enterprise Buyer Expectations in Payments
Enterprise merchants, platforms, and financial institutions evaluate payment vendor SOC 2 reports with specific expectations that differ from typical B2B SaaS procurement. Based on what we see across our payment processing clients, here is what those buyers focus on.
What Payment Buyers Look For
| Buyer Expectation | What They Review | Why It Matters |
|---|---|---|
| Processing Integrity inclusion | Whether the PI criterion is in scope | Validates transaction accuracy and reliability |
| Availability commitments | SLA documentation and uptime evidence | Payment downtime directly impacts merchant revenue |
| Key management controls | Encryption key rotation, access restrictions, HSM usage | Critical for payment security infrastructure |
| Multi-tenancy isolation | Merchant data segregation controls | Ensures one merchant's data cannot be accessed by another |
| Incident response maturity | Response procedures, incident history, breach notification | Evaluates how the platform handles payment disruptions |
| Subservice organization treatment | How third-party processors are addressed in the report | Assesses supply chain risk in the payment flow |
Financial Institution Partners
In our experience:
How do you build a Unified PCI DSS + SOC 2 Program?
The most efficient approach — and what we recommend to every payment processing client — is to build a single compliance program that satisfies both frameworks rather than managing them separately.
Step 1: Map Existing PCI DSS Controls to SOC 2
Review your current PCI DSS controls and map each one to the corresponding SOC 2 Trust Service Criteria. The overlap map above provides the starting point. For each PCI DSS control, determine whether it fully satisfies the SOC 2 requirement, partially satisfies it (requiring extension), or has no SOC 2 equivalent.
Step 2: Extend Controls Beyond the CDE
The primary gap between PCI DSS and SOC 2 is scope. PCI DSS controls are scoped to the cardholder data environment. SOC 2 requires these same types of controls applied across your entire service delivery system. Extension means applying access management, monitoring, and change control practices to non-CDE systems that are in your SOC 2 scope.
Step 3: Add SOC 2-Specific Controls
Implement the SOC 2 requirements that PCI DSS does not cover:
- Formal risk assessment with risk register and treatment plans
- Comprehensive vendor management program covering all third-party vendors
- Board/leadership security oversight documentation
- Enhanced business continuity and disaster recovery testing
- Formalized employee lifecycle management with background checks and annual training
Step 4: Use a Single GRC Platform
GRC platforms like Vanta, Drata, and Secureframe support both SOC 2 and PCI DSS frameworks. Controls implemented once are automatically mapped to both frameworks, evidence is shared, and compliance status is tracked across both programs on a single dashboard.
Step 5: Coordinate Audit Timing
Schedule PCI DSS and SOC 2 assessments to run consecutively or use overlapping timelines. Using the same or affiliated audit firms for both engagements reduces total interview and evidence review time. Some CPA firms that perform SOC 2 audits also have QSA certifications for PCI DSS, enabling a single firm to conduct both assessments.
Cost Efficiency
The savings come from existing technical controls (encryption, logging, access management), established security policies, and organizational familiarity with compliance processes.
We help our clients build unified PCI DSS and SOC 2 programs from the ground up — mapping existing controls, closing gaps efficiently, and coordinating audit timelines so nothing is duplicated unnecessarily.
AICPA & CIMA’s SOC overview describes CPA assurance services. It defines the assurance context; it does not establish vendor rankings, market prices, or a particular company’s readiness.
Frequently Asked Questions
Why do payment companies need both SOC 2 and PCI DSS?
Does PCI DSS compliance give you a head start on SOC 2?
Which Trust Service Criteria should payment platforms select?
What makes SOC 2 scoping hard for payment platforms?
What do enterprise merchants expect from a payment vendor's SOC 2?

Tyler Carbone
Managing Director and Cofounder
Tyler Carbone is a Managing Director and Cofounder of Agency and one of the industry's leading voices on governance, risk, and compliance. He holds degrees from Harvard and a JD/MBA from the University of Virginia, and previously worked in cybersecurity at Deloitte. Tyler has helped hundreds of companies operate SOC 2, ISO 27001, HIPAA, and GDPR programs.
LinkedIn