Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next 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/12/12 17:07]
robinc [Request Body Fields] added StoredCredentialUse field info
Line 74: Line 74:
 | LINE_ITEM_'​N'​_TOTAL_AMOUNT |  N  |Final item value based on total (quantity x unit price) after discount and tax applied. Max of 13 characters and 3 decimal points, depending on your terminal'​s currency. See **ND006** for more details.| | LINE_ITEM_'​N'​_TOTAL_AMOUNT |  N  |Final item value based on total (quantity x unit price) after discount and tax applied. Max of 13 characters and 3 decimal points, depending on your terminal'​s currency. See **ND006** for more details.|
 | CUSTOMFIELD | N | Any of the available Custom Fields for the Terminal. If there are Custom Fields enabled for the particular Terminal in use, the Hosted Page is gonna show the ones not sent on request and hide the ones sent, pre-populating them with the informed values. Their values are going to be stored and used by the Payment Gateway for the requests sent to the Receipt URL and the Validation URL. To understand more visit the section regarding **[[developer:​api_specification:​special_fields_and_parameters|Special Fields and Parameters]]**. | | CUSTOMFIELD | N | Any of the available Custom Fields for the Terminal. If there are Custom Fields enabled for the particular Terminal in use, the Hosted Page is gonna show the ones not sent on request and hide the ones sent, pre-populating them with the informed values. Their values are going to be stored and used by the Payment Gateway for the requests sent to the Receipt URL and the Validation URL. To understand more visit the section regarding **[[developer:​api_specification:​special_fields_and_parameters|Special Fields and Parameters]]**. |
-OTHERFIELD ​| N | Any other fields sent in the request will be treated as a custom ​field. ​They are not going to be storedbut they are going to be used by the Payment Gateway for the request sent to the Receipt URLNote that this is subject to the max length of a HTTP GET request which we would conservatively recommend considering to be 2000 characters. |+ORIGNALBRANDTXIDENTIFIER ​| N | String, max length is 64 - Merchant sends the transaction identifier received from acquirer See note **ND0006 - Stored Credential use field behavior and settings**
 +| STOREDCREDENTIALUSE |  N  |UNSCHEDULEDINSTALLMENT or RECURRRINGSee note **ND0006 - Stored Credential use field behavior and settings**.| 
 +| STOREDCREDENTIALTXTYPE | N | FIRST_TXN, SUBSEQUENT_MERCHANT_INITIATED_TXN or SUBSEQUENT_CARDHOLDER_INITIATED_TXN. See note **ND0006 - Stored Credential use field behavior and settings**. | 
 </​searchtable>​ </​searchtable>​
  
Line 244: Line 247:
 \\ \\
  
-**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"​.
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International