This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
developer:api_specification:hpp_payment_features [2019/06/04 14:27] vinayh [Notes and Details on the Response] |
developer:api_specification:hpp_payment_features [2019/06/04 14:40] vinayh [Notes and Details on the Response] |
||
---|---|---|---|
Line 244: | Line 244: | ||
\\ | \\ | ||
- | **ND002 - Treat Metrix Enabling** | + | **ND002 - Sentinel Defend Enabling** |
- | Threat Metrix must be enabled for your Gateway and on the Terminal used for processing the request needs to be also enabled for Threat Metrix feature so your response contains these fields. | + | Sentinel Defend must be enabled for your Gateway and on the Terminal used for processing the transaction request so that the response contains those fields. |
\\ | \\ | ||
- | **ND003 - Treat Metrix REVIEW status** | + | **ND003 - Sentinel Defend REVIEW status** |
If a transaction is returned with "FRAUDREVIEWSTATUS" as "REVIEW", this transaction can be changed manually, using the new report feature on Selfcare System, or using the transaction update XML gateway service, to "APPROVE" or "REJECT" the transaction. Transactions with this status are not going to be settled until the transaction status is changed. See the XML Gateway method for more details, more specifically, its **Transaction Update** feature, to change the transaction returned as "REVIEW" to "REJECT" or "APPROVE". | If a transaction is returned with "FRAUDREVIEWSTATUS" as "REVIEW", this transaction can be changed manually, using the new report feature on Selfcare System, or using the transaction update XML gateway service, to "APPROVE" or "REJECT" the transaction. Transactions with this status are not going to be settled until the transaction status is changed. See the XML Gateway method for more details, more specifically, its **Transaction Update** feature, to change the transaction returned as "REVIEW" to "REJECT" or "APPROVE". |