EMV 3-D Secure (3DS2) — Payment Authentication Protocol
EMV 3-D Secure (3DS2, version 2.3.1) is the payment authentication protocol developed by EMVCo to enable secure card-not-present (CNP) transactions. It replaces the original 3DS1 protocol with improved user experience, risk-based authentication, and support for Strong Customer Authentication (SCA) as required by regulations such as PSD2. 3DS2 uses a message-based architecture to enable richer data exchange between merchants, issuers, and acquirers, facilitating frictionless authentication and out-of-band verification.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (4)
Interoperability and Extensions
| Code | Title |
|---|---|
| 3DS-4.1 | Directory Server Interoperability |
| 3DS-4.2 | Message Extensions |
| 3DS-4.3 | Split-SDK Specification |
Protocol and Core Functions
| Code | Title |
|---|---|
| 3DS-1.1 | Three-Domain Model |
| 3DS-1.2 | Authentication Request/Response |
| 3DS-1.3 | Challenge Flow |
| 3DS-1.4 | Data Elements |
| 3DS-1.5 | Risk-Based Authentication |
SDK Specification
| Code | Title |
|---|---|
| 3DS-2.1 | SDK Architecture |
| 3DS-2.2 | Device Information Collection |
| 3DS-2.3 | SDK Security Requirements |
Security and Compliance
| Code | Title |
|---|---|
| 3DS-3.1 | 3DS Server Security |
| 3DS-3.2 | Message Integrity |
| 3DS-3.3 | Data Encryption |
| 3DS-3.4 | PCI 3DS Compliance |
Your Compliance Coverage
If you comply with EMV 3-D Secure (3DS2) — Payment Authentication Protocol, you already cover:
Chile Personal Data Protection Law (Law No. 21.719)
53%
8 controls mapped
Compare →Connecticut Data Privacy Act (CTDPA)
53%
8 controls mapped
Compare →NIST SP 800-171A Rev 3 — Assessing CUI Security Requirements
47%
7 controls mapped
Compare →+ 598 more: 3GPP Security Architecture (TS 33.501 — 5G Security) (47%), UK Open Banking Standard (47%)
See all 601 mapped frameworks ↓Maps to 601 other frameworks
Frequently Asked Questions
What is EMV 3-D Secure (3DS2) — Payment Authentication Protocol?
EMV 3-D Secure (3DS2) — Payment Authentication Protocol is a compliance framework from International (EMVCo) with 4 domains and 15 controls. EMV 3-D Secure (3DS2, version 2.3.1) is the payment authentication protocol developed by EMVCo to enable secure card-not-present (CNP) transactions. It replaces the original 3DS1 protocol with improved user experience, risk-based authentication, and support for Strong Customer Authentication (SCA) as required by regulations such as PSD2. 3DS2 uses a message-based architecture to enable richer data exchange between merchants, issuers, and acquirers, facilitating frictionless authentication and out-of-band verification. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does EMV 3-D Secure (3DS2) — Payment Authentication Protocol have?
EMV 3-D Secure (3DS2) — Payment Authentication Protocol has 15 controls organised across 4 domains. The largest domains are Protocol and Core Functions (5 controls), Security and Compliance (4 controls), Interoperability and Extensions (3 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does EMV 3-D Secure (3DS2) — Payment Authentication Protocol map to?
EMV 3-D Secure (3DS2) — Payment Authentication Protocol maps to 601 other compliance frameworks. The top mapping partners are Chile Personal Data Protection Law (Law No. 21.719) (53% coverage), Connecticut Data Privacy Act (CTDPA) (53% coverage), NIST SP 800-171A Rev 3 — Assessing CUI Security Requirements (47% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with EMV 3-D Secure (3DS2) — Payment Authentication Protocol compliance?
Start your EMV 3-D Secure (3DS2) — Payment Authentication Protocol compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about EMV 3-D Secure (3DS2) — Payment Authentication Protocol requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 15 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 693 frameworks.
Get Started Free →Free forever — no credit card required