3-D Secure Documentation

The 3DS documentation consists of several key documents that define the three-domain model and overall architecture and provide the technical requirements, as well as a range of supporting documents to help the understanding and implementation of the 3DS protocol.

There are four key types of 3DS documentation:

  • Specifications – define the 3DS architecture and requirements
  • Specification bulletins – update or complement the specifications
  • Message extensions – enable the transport of additional data
  • Supporting documents such as guides, white papers or FAQ – provide additional

The 3DS Specification consists of five key documents listed below.

  • EMV 3-D Secure Protocol and Core Functions Specification (the main 3-D Secure specification) – defines the three-domain model, the messages, their data, and the channels for performing a 3DS authentication.
  • EMV 3-D Secure SDK Specification – defines the device-side component of 3DS. 3DS Requestors such as Merchants integrate this SDK with their mobile device app and make the app available to end users.
  • EMV 3-D Secure Split-SDK Specification – defines a variant of the 3DS SDK for which some of the client functionalities do not run on the device, but on a server component, thus implementing a 3DS SDK with functionalities split between a Split-SDK Client (client side) and a Split-SDK Server (server side).
  • EMV 3-D Secure SDK Device Information – defines the device information provided by the 3DS SDK when an authentication is initiated from an app.
  • EMV 3-D Secure Specification Bulletin No. 255 Specification Version Configuration – defines the status of the EMV® 3-D Secure Protocol and Core Functions Specification, the EMV 3-D Secure SDK—Device Information versions, and the EMV® 3-D Secure Message Extensions.

The SDK Specification and the Split-SDK Specification are only applicable to mobile device applications or the Split-SDK architecture.

There are currently four EMV 3-D Secure message extensions:

  • EMV 3-D Secure Bridging Message Extension – defines how existing 3DS v2.1.0 and v2.2.0 components can provide or consume additional data related to EMV® 3-D Secure Protocol and Core Functions Specification v2.3.1.
  • EMV 3-D Secure Device Acknowledgement Message Extension – defines how the 3DS Server can provide the Split-SDK-related data to the ACS and the ACS can acknowledge data received in EMV® 3-D Secure Device Information.
  • EMV 3-D Secure Payment Token Message Extension – defines how 3DS components can provide or receive token-related information.
  • EMV 3-D Secure Travel Industry Message Extension – defines how 3DS Servers can provide travel-related data to the ACS.