--- developer:api_specification:hpp_payment_features [2019/05/24 12:18]
robinc [Request Body Fields] Additional fields added
+++ developer:api_specification:hpp_payment_features [2019/12/12 17:12]
robinc [Notes and Details About the Request] Added ND0006
@@ 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.|
 | 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 stored, but they are going to be used by the Payment Gateway for the request sent to the Receipt URL. Note 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  |UNSCHEDULED, INSTALLMENT or RECURRRING. See 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>
@@ Line 83: / Line 86: @@
 **ND001 - Hash Formation**
-The gerenal rule to build HASH field is given at the **[[developer:api_specification:special_fields_and_parameters|Special Fields and Parameters]]** page. For this specific feature, you should use the following formats:
+The general rule to build HASH field is given at the **[[developer:api_specification:special_fields_and_parameters|Special Fields and Parameters]]** page. For this specific feature, you should use the following formats:
 When using a Single Currency Terminal, the string to generate the HASH field is going to formed using:
@@ Line 128: / Line 131: @@
 Depending on your customer's browser definitions and if there's a language template defined for his/ her language priority, the Payment Gateway is going to send the payment receipt translated. If the language is not supported by the gateway, the receipt is going to be sent using the gateway's language.
+\\
+**ND006 - Stored Credential use field behavior and settings**
+This feature is currently available to TSYS Saratoga terminals and is configurable by customer support. These fields will only be used on a payment if you have secure card storage enabled. The fields will have the following behavior: Hidden - the gateway accepts the fields, if sent, and adds them to the transaction, but does not show it for the customer.
 ==== Examples for a Request ====
@@ Line 244: / Line 252: @@
 \\
-**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".
 \\

Differences

Worldnet

Learn More

Request

Contact Us