EMV 3-D Secure (3DS) - Payment Authentication Protocol
Versions 2.2 and 2.3.1: features added after v2.0.0 – EMV 3-D Secure (3DS) - Payment Authentication Protocol

EMV 3-D Secure (3DS) - Payment Authentication Protocol V.20: V.20 UTC time, HTTP request identifiers and broadcast information

Three housekeeping rules of 2.3.1.1: the 3DS Server, DS and ACS keep their clocks within 15 minutes of UTC when setting or checking UTC date and time elements, and the DS (and optionally the ACS) returns Error Code 203 when the SDK signature timestamp or purchase date and time arrives more than 30 minutes off UTC, local times being converted to UTC first; each request carries an X-Request-ID header and each response an X-Request-ID and X-Response-ID set to the transaction identifier Table A.29 assigns to that message leg; and the 3DS Server, DS and ACS may exchange Broadcast Information in the AReq and ARes, an object giving the category (general, certificate validity, fraud alert, operational alert, transactional data, other), a description of up to 4,000 characters, an optional relevance end date, a severity (critical, major, minor, informational), the intended recipients and the source.

Maintained by Gerard BlokdykControl text last updated

Other controls in Versions 2.2 and 2.3.1: features added after v2.0.0 – EMV 3-D Secure (3DS) - Payment Authentication Protocol

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.