Differences
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_secure_card_features [2019/12/11 17:06] robinc [Request Body Fields] added StoredCredentialUse field info |
developer:api_specification:hpp_secure_card_features [2019/12/11 17:12] robinc [Notes and Details About the Request] Added ND0004 |
||
|---|---|---|---|
| Line 32: | Line 32: | ||
| **ND001 - Hash Formation** | **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: |
| <WRAP center box 100%> | <WRAP center box 100%> | ||
| Line 45: | Line 45: | ||
| 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 behavior and settings** | ||
| + | |||
| + | This field is currently available to TSYS Saratoga terminals and is configurable by customer support. This field will have the following behavior: Hidden - the gateway accepts the field, if sent, and adds it to the transaction, but does not sow it for the customer. | ||
| + | |||
| + | Note: STOREDCREDENTIALTXTYPE set as FIRST_TXN by default. | ||
| \\ | \\ | ||