This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
developer:api_specification:hpp_secure_card_features [2019/12/11 17:17] robinc [Examples for a Request] added StoredCredentialUse input type |
developer:api_specification:hpp_secure_card_features [2022/03/04 10:35] lezlieh update with secure token |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Hosted Page Secure Card Feature ======= | + | ====== Hosted Page Secure Token Feature ======= |
~~TOC~~ | ~~TOC~~ | ||
Line 5: | Line 5: | ||
\\ | \\ | ||
- | This feature enables you to register a Secure Card using the Hosted Page method. For more details on Secure Cards, please visit the **[[merchant:new_merchant:products#secure_card|Products]]** page. | + | This feature enables you to register a Secure Token using the Hosted Page method. For more details on Secure Tokens, please visit the **[[merchant:new_merchant:products#secure_card|Products]]** page. |
- | Use the Request URL and the Request Body Fields to perform a request for this feature, then put in place your Secure Card URL so the Gateway can use the Response Body Fields to send the registration's response. | + | Use the Request URL and the Request Body Fields to perform a request for this feature, then put in place your Secure Token URL so the Gateway can use the Response Body Fields to send the registration's response. |
===== Secure Card Registration and Update ===== | ===== Secure Card Registration and Update ===== | ||
Line 48: | Line 48: | ||
**ND0004 - Stored Credential use field behavior and settings** | **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 is optional and 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. | + | This field is currently available to TSYS Saratoga terminals. This field is optional and 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. | Note: STOREDCREDENTIALTXTYPE set as FIRST_TXN by default. | ||
Line 97: | Line 97: | ||
| 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> | ||
\\ | \\ |