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.16: V.16 Attribute Verification Message Extension

A non-critical extension, for browser, app and 3RI channels and payment and non-payment categories, through which the requestor (or DS) asks the ACS (or DS) to verify attributes such as age, date of birth, citizenship, ID number or a core data element (cardholder name, billing address) with a match type (greater, less, equal and so on, or compare) and a match value; the verifier returns result codes (matched, not matched, partial, supported but not verifiable, not supported) either in the ARes (Verification Response Indicator N) or after a challenge in the RReq (indicator Y), all attributes in one message, and on suspected fraud a failed result with core Transaction Status Reason 11. Because the data can be sensitive, the requestor or ACS should obtain cardholder consent first. The extension is not among those the v2.3.1.1 core specification lists in its supporting documents; it was published afterwards.

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.