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
developer:api_specification:hpp_payment_features [2019/05/17 14:02]
127.0.0.1 external edit
developer:api_specification:hpp_payment_features [2019/10/07 09:26] (current)
branko
Line 62: Line 62:
 | 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 going to 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 going to 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. | | 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. |
 +| ORIGINALBRANDTXIDENTIFIER | N | String, max length is 64 - Merchant sends the transaction identifier received from acquirer See note **ND0006** - Stored Credential use field behaviour and settings |
 +| STOREDCREDENTIALUSE | N | UNSCHEDULED,​ INSTALLMENT or RECURRING. See note **ND0006** - Stored Credential use field behaviour and settings| ​
 +| STOREDCREDENTIALTXTYPE | N | FIRST_TXN, SUBSEQUENT_MERCHANT_INITIATED_TXN or SUBSEQUENT_CARDHOLDER_INITIATED_TXN. See note **ND0006** - Stored Credential use field behaviour and settings |
 +
 +
 </​searchtable>​ </​searchtable>​
  
Line 174: Line 179:
 These fields are associate with of the Transaction`s Level 3 Enhanced Data. To be used, it's necessary that your terminal has the enhanced data enabled and set to LEVEL 3. To be valid, these fields need to be added to the transaction together with the Level II fields. Also, consider that the enhanced data fields are not mandatory, but if you send any Level 3 data fields, your application must send at least one item, and this item must contain at least the unit price, quantity and final amount. This feature is only available for specific acquirers (contact our support team for more details). These fields are associate with of the Transaction`s Level 3 Enhanced Data. To be used, it's necessary that your terminal has the enhanced data enabled and set to LEVEL 3. To be valid, these fields need to be added to the transaction together with the Level II fields. Also, consider that the enhanced data fields are not mandatory, but if you send any Level 3 data fields, your application must send at least one item, and this item must contain at least the unit price, quantity and final amount. This feature is only available for specific acquirers (contact our support team for more details).
  
 +**ND007 - Stored Credential use field behaviour 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 behaviour:
 +Hidden - the gateway accepts the fields, if sent, and adds them to the transaction,​ but does not show it for the customer.
 \\ \\
 {/gateway} {/gateway}
Line 255: Line 264:
 | CUSTOMFIELD | Same as informed at the transaction'​s request. Returns all custom fields informed on request. | | CUSTOMFIELD | Same as informed at the transaction'​s request. Returns all custom fields informed on request. |
 | OTHERFIELD | Same as informed at the transaction'​s request. Returns all additional fields informed on request. | | OTHERFIELD | Same as informed at the transaction'​s request. Returns all additional fields informed on request. |
 +| BRANDTXIDENTIFIER | Same as informed at the transaction'​s request. Returned if informed on request |
 +| STOREDCREDENTIALUSE | Same as informed at the transaction'​s request. Returned if informed on request |
 +| STOREDCREDENTIALTXTYPE | Same as informed at the transaction'​s request. Returned if informed on request |
 +
 </​searchtable>​ </​searchtable>​
 \\ \\
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International