...
width | 900px |
---|
Data Elements
...
...
threeDSServerTransID
...
string
...
M
...
Computop Paygate PayID in canonical format as specified in IETF RFC 4122.
...
acsChallengeMandated
...
boolean
...
M
...
Indication of whether a challenge is required for the transaction to be authorised.
...
acsDecConInd
...
boolean
...
C
...
Indicates whether the ACS confirms utilisation of Decoupled Authentication and agrees to utilise Decoupled Authentication to authenticate the cardholder. Required if Transaction Status = D.
...
acsOperatorID
...
string
...
C
...
DS assigned ACS identifier. Each DS can provide a unique ID to each ACS on an individual basis. Requirements for the presence of this field are DS specific.
...
acsReferenceNumber
...
string
...
M
...
Unique identifier assigned by the EMVCo Secretariat upon Testing and Approval.
...
...
object
...
C
...
App-based only. Identifies the ACS UI Template that the ACS will first present to the consumer. Required if Transaction Status = C.
...
acsSignedContent
...
string
...
C
...
App-based only. Contains the JWS object (represented as a string) created by the ACS for the ARes message. Required if the Transaction Status = C.
...
acsTransID
...
string
...
M
...
Universally Unique transaction identifier assigned by the ACS to identify a single transaction.
...
acsURL
...
string
...
C
...
Fully qualified URL of the ACS to be used to post the Challenge Request. For App-based, this data element is contained within the ACS Signed Content JWS Object. Required if Transaction Status = C.
...
authenticationType
...
string
...
C
...
Indicates the type of authentication method the Issuer will use to challenge the cardholder. Required if the Transaction Status = C or D.
Values accepted:
01 = static
02 = dynamic
03 = oob
Future implementation. Protocol Version 2.2.0 onwards -
04 = decoupled
...
authenticationValue
...
string
...
C
...
Payment System-specific value provided by the ACS or the DS to provide proof of authentication. Required if Transaction Status = Y or A. Conditional based on DS rules if Transaction Status = I.
...
broadInfo
...
string
...
C
...
Unstructured information sent between the 3DS Server, the DS and the ACS. Requirements for the presence of this field are DS specific.
...
cardholderInfo
...
string
...
C
...
...
...
...
...
...
...
transStatusReason
...
string
...
C
...
Provides information on why the Transaction Status field has the specified value. Required if the Transaction Status field = N, U, or R.
Values accepted:
01
= Card authentication failed02
= Unknown Device03
= Unsupported Device04
= Exceeds authentication frequency limit05
= Expired card06
= Invalid card number07
= Invalid transaction08
= No Card record09
= Security failure10
= Stolen card11
= Suspected fraud12
= Transaction not permitted to cardholder13
= Cardholder not enrolled in service14
= Transaction timed out at the ACS15
= Low confidence16
= Medium confidence17
= High confidence18
= Very High confidence19
= Exceeds ACS maximum challenges20
= Non-Payment transaction not supported21
= 3RI transaction not supported22
= ACS technical issue23
= Decoupled Authentication required by ACS but not requested by 3DS Requestor24
= 3DS Requestor Decoupled Max Expiry Time exceeded25
= Decoupled Authentication was provided insufficient time to authenticate cardholder. ACS will not make attempt26
= Authentication attempted but not performed by the cardholder
...
whiteListStatus
...
string
...
C
Future use. Only supported with protocol version 2.2.0 onwards. Enables the communication of trusted beneficiary/whitelist status.
Values accepted:
...
Y
= 3DS Requestor is whitelisted by cardholder
...
N
= 3DS Requestor is not whitelisted by cardholder
...
E
= Not eligible as determined by issuer
...
P
= Pending confirmation by cardholder
...
R
= Cardholder rejected
...
...
...
...
...
...
...
...
...
...
Schema
...
...
...
...
...
...