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_secure_card_features [2018/12/24 11:27]
thiago123 [Request Body Fields]
developer:api_specification:hpp_secure_card_features [2019/10/07 09:14] (current)
leandro
Line 23: Line 23:
 | DATETIME ​  | Y | Date and time of the request. Format: DD-MM-YYYY:​HH:​MM:​SS:​SSS. | | DATETIME ​  | Y | Date and time of the request. Format: DD-MM-YYYY:​HH:​MM:​SS:​SSS. |
 | HASH       ​| ​ Y  | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**,​ in the next section. | | HASH       ​| ​ Y  | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**,​ in the next section. |
 +| STOREDCREDENTIALUSE |  N  | Values can be: UNSCHEDULED,​ INSTALLMENT or RECURRING. See note ND0004 - Stored Credential use field behaviour and settings |
 </​searchtable>​ </​searchtable>​
 \\ \\
Line 45: Line 46:
 This field is available for all terminal, but depending on configuration (**SC Hosted Page email field setup**), it might have one of the following behaviors when the customer gets to the hosted payment page: \\ **Hidden** - the gateway accepts the field, if sent, and adds it to the transaction,​ but does not show it for the customer); \\ **Visible** - the gateway accepts the field, if sent, and adds it to the transaction,​ also shows the field on the hosted payment page, and the user can changed it or not. In this last case, the field can be made optional or mandatory. This field is available for all terminal, but depending on configuration (**SC Hosted Page email field setup**), it might have one of the following behaviors when the customer gets to the hosted payment page: \\ **Hidden** - the gateway accepts the field, if sent, and adds it to the transaction,​ but does not show it for the customer); \\ **Visible** - the gateway accepts the field, if sent, and adds it to the transaction,​ also shows the field on the hosted payment page, and the user can changed it or not. In this last case, the field can be made optional or mandatory.
  
 +**ND0004 - Stored Credential use field behaviour and settings**
 +
 +This feature is currently available to TSYS Saratoga terminals and is configurable by customer support. This field will have the following behaviour:
 +Hidden - the gateway accepts the field, if sent, and adds it to the transaction,​ but does not show it for the customer.
 +
 +Note: STOREDCREDENTIALTXTYPE set as FIRST_TXN by default
 \\ \\
  
Line 89: Line 96:
 | CARDEXPIRY ​   | Expiry date of the card. | | CARDEXPIRY ​   | Expiry date of the card. |
 | DATETIME | The time of the registration. Format: YYYY-MM-DDTHH:​MM:​SS. | | DATETIME | The time of the registration. Format: YYYY-MM-DDTHH:​MM:​SS. |
-| HASH | A HASH code formed by part of the response fields. The formation rule is given at the **ND001 - Hash Formation**,​ in the next section. ​ |+| HASH | A HASH code formed by part of the response fields. The formation rule is given at the **ND001 - Hash Formation**,​ in the next section. ​ |  
 +| STOREDCREDENTIALUSE | Same as informed at the transaction'​s request. Returned if informed on request |  
 +| STOREDCREDENTIALTXTYPE | set as FIRST_TXN by default | 
 +| BRANDTXIDENTIFIER | If STOREDCREDENTIALUSE is sent in request and secure card is validated - then returned by acquirer | 
 +  
 </​searchtable>​ </​searchtable>​
 \\ \\
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International