|
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 |
|
When the 3-D secure authentication fails this message gives an indication about the reason of the failure.
|
String |
30 |
|
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 |
|
The 3-D secure session identifier, supplied by the issuer.
|
String |
32 |
|
The status of 3-D Secure check.
|
Static Value |
10 |
|
The result of 3-D Secure authentication.
|
String |
14 |
|
Braintree may check the provided postal code (AVS). The provided code indicates whether the address could be validated or not.
|
Static Value |
26 |
|
Braintree may check the provided street (AVS). The provided result indicates whether the buyer could be identified or not.
|
Static Value |
27 |
|
The status of Address & Postcode verification and Card Security code check.
|
Static Value |
10 |
|
The acquirer's acceptance (authorization) code.
|
String |
0 |
|
The account number of the customer from which the direct debit payment will come out.
|
String |
5 |
