ThreeDSRequestorPriorAuthenticationInfoXML

The ThreeDSRequestorPriorAuthenticationInfoXML tags and data validation rules are described in the following table. The XML tags should follow the order they are listed.

**ThreeDSRequestorPriorAuthenticationInfoXML tags**
Node/Element	Description	Mandatory	Format and Valid Characters	Max Length	Allowed Values
threeDSRequestorPriorAuthenticationInfo	The root element for all other threeDSRequestorPriorAuthenticationInfo elements.	No	Node
threeDSReqPriorAuthData	Data to document and support a specific authentication process. In the current version of the EMVCo specification, this data element is not yet defined.	No	Any	2048 bytes
threeDSReqPriorAuthMethod	Mechanism used by the Cardholder during a previous 3DS authentication as part of a previous transaction request. 01 = Frictionless authentication occurred by ACS 02 = Cardholder challenge occurred by ACS 03 = AVS verified 04 = Other issuer methods 05–79 = Reserved for EMVCo future use (values invalid until defined by EMVCo) 80–99 = Reserved for DS use	No	Digits from 01 to 99	2	01 02 03 04
threeDSReqPriorAuthTimestamp	Date and time in UTC of the previous cardholder 3DS authentication.	No	ISO8601	16	Date and time as: yyyy-MM-ddTHH:mm yyyy - Year MM - Month dd- Day T - Time separator HH - Hour mm- Minute
threeDSReqPriorRef	Additional information provided to the ACS to determine the best approach for handling a request. It contains an ACS Transaction ID for a prior authenticated transaction. For example, the first recurring transaction that was authenticated with the cardholder. In future, this will be returned in the ACSTransID field and made available in MyOpayo and the Reporting and Admin API.	No	Letters, digits, hyphens, and curly brackets	36