Cross-Framework Mapping

PSD2 SCAvsPCI SSF

See exactly how PSD2 SCA controls map to PCI SSF. Pre-computed mappings, identified gaps, and coverage analysis.

22
Controls Mapped
0
Gaps Found
67%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

PSD2 SCA maps to PCI SSF with 67% coverage across 4 directly mapped controls. Analysis of 6 PSD2 SCA controls identifies 2 compliance gaps — primarily concentrated in Governance and Compliance.

Source: TheArtOfService Knowledge Graph | 6 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 20 of 22 mapped controls across 4 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

SCA Core(7 mappings)

PSDTWO-1Strong Customer Authentication (SCA) Core Requirements7 targets
PCI-SSF-03Risk appetite and tolerance for IT risk
PCI-SSF-05Roles and responsibilities definition
PCI-SSF-06Network security and segmentation
PCI-SSF-07Endpoint protection and detection
PCI-SSF-08Application security controls
PCI-SSF-16Due diligence and onboarding
PCI-SSF-17Contractual security requirements

SCA Exemptions(6 mappings)

PSDTWO-2SCA Exemptions and Risk-Based Authentication6 targets
PCI-SSF-09Encryption and key management
PCI-SSF-10Secure configuration standards
PCI-SSF-11Business continuity planning and testing
PCI-SSF-12Disaster recovery procedures
PCI-SSF-14Critical service identification
PCI-SSF-15Communication and escalation procedures

Open Banking APIs(6 mappings)

PSDTWO-3Common and Secure Communication, API Access for AISPs and PISPs6 targets
PCI-SSF-03Risk appetite and tolerance for IT risk
PCI-SSF-16Due diligence and onboarding
PCI-SSF-17Contractual security requirements
PCI-SSF-21Incident detection and classification
PCI-SSF-24Customer notification procedures
PCI-SSF-25Post-incident review and improvement

Fraud and Incident Reporting(1 mappings)

PSDTWO-4Fraud Reporting and Incident Management
PCI-SSF-21Incident detection and classification

+2 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 718 frameworks.

Create Free Account →

Free forever — no credit card required

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between PSD2 SCA and PCI SSF?

PSD2 SCA has 6 controls across its framework, while PCI SSF covers 49 controls. Direct mapping analysis identifies 4 overlapping controls (67% coverage). The frameworks diverge most significantly in Governance and Compliance, where 1 PSD2 SCA controls have no direct PCI SSF equivalent.

How many controls map between PSD2 SCA and PCI SSF?

Of 6 total PSD2 SCA controls, 4 map directly to PCI SSF controls — representing 67% coverage. The remaining 2 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping PSD2 SCA to PCI SSF?

2 PSD2 SCA controls have no direct equivalent in PCI SSF. The highest concentration of gaps is in Governance and Compliance with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between PSD2 SCA and PCI SSF?

The domain with the highest gap count is Governance and Compliance (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.