|
Indicates if 3-D Secure authentication was performed.
|
Boolean |
31 |
|
Indicates if 3-D Secure authentication is offered for this type of card.
|
Boolean |
31 |
|
The 3-D secure authentication status indicates if the 3-D secure authenticate has been executed and if not why it has been failed.
|
Static Value |
33 |
|
The 3-D Secure CAVV.
|
String |
401 |
|
When the 3-D secure authentication fails this message gives an indication about the reason of the failure.
|
String |
30 |
|
Specifies if 3-D Secure was initialized successfully.
|
Boolean |
10 |
|
Specifies if 3-D Secure was initialized successfully.
|
Boolean |
10 |
|
Indicates if the liability shift has occurred as a result of 3-D Secure authentication.
|
Boolean |
31 |
|
Whether the header information from customer's browser required to process 3-D Secure authentication was present.
|
Boolean |
32 |
|
The timestamp after the 3-D Secure process is finished.
|
Datetime |
0 |
|
The timestamp of the 3-D Secure process initialization.
|
Datetime |
0 |
|
Whether the 3-D secure authentication was processed during this charge attempt.
|
Boolean |
11 |
|
The URL to redirect the customer for 3-D Secure authentication.
|
String |
32 |
|
The 3-D request data which will be passed to the issuer.
|
String |
32 |
|
Whether we have requested 3-D authentication (e.g. we would not do so in case of recurring transactions).
|
Boolean |
32 |
|
Indicates whether 3-D Secure request was sent or not.
|
String |
0 |
|
Computop Paygate PayID in canonical format as specified in IETF RFC 4122.
|
String |
0 |
|
The 3-D secure session identifier, supplied by the issuer.
|
String |
32 |
|
The 3-D Secure status as received from processor for this transaction.
|
Static Value |
0 |
|
The 3-D Secure random token generated on return.
|
String |
400 |