Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
developer:api_specification:hpp_secure_card_features [2020/03/05 10:38] robinc [Notes and Details About the Request] removal of configuration by customer support |
developer:api_specification:hpp_secure_card_features [2022/03/04 10:59] (current) lezlieh [update to 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 Token Registration and Update ===== |
| * REQUEST URL: **https://testpayments.nuvei.com/merchant/securecardpage** | * REQUEST URL: **https://testpayments.nuvei.com/merchant/securecardpage** | ||
| Line 38: | Line 38: | ||
| </WRAP> | </WRAP> | ||
| - | **ND002 - Valid Secure Card Update** | + | **ND002 - Valid Secure Token Update** |
| - | To initiate card details updating, the value of the ACTION parameter should be changed to “update”. Also, in case you want to update a Secure Card of MERCHANTREF **1234321**, a Secure Card should already exist with this same MERCHANTREF, or the updated won't preoceed. | + | To initiate card details updating, the value of the ACTION parameter should be changed to “update”. Also, in case you want to update a Secure Token of MERCHANTREF **1234321**, a Secure Token should already exist with this same MERCHANTREF, or the updated won't preoceed. |
| **ND0003 - E-mail field behavior and settings** | **ND0003 - E-mail field behavior and settings** | ||
| Line 84: | Line 84: | ||
| ==== Response Body Fields ==== | ==== Response Body Fields ==== | ||
| - | Assuming valid details were sent, the Hosted Registration or Update page will be displayed, clicking on “Register” or “Update” will save the card details, result GET parameters will be forwarded to the Secure Card URL that is configured on the Terminal Setup page. The response body field will be: | + | Assuming valid details were sent, the Hosted Registration or Update page will be displayed, clicking on “Register” or “Update” will save the card details, result GET parameters will be forwarded to the Secure Token URL that is configured on the Terminal Setup page. The response body field will be: |
| <searchtable> | <searchtable> | ||
| Line 99: | Line 99: | ||
| | STOREDCREDENTIALUSE | 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 | set as FIRST_TXN by default | | | STOREDCREDENTIALTXTYPE | set as FIRST_TXN by default | | ||
| - | | BRANDTXIDENTIFIER | If STOREDCREDENTIALUSE is sent in request and secure card is validated - then returned by acquirer. | | + | | BRANDTXIDENTIFIER | If STOREDCREDENTIALUSE is sent in request and secure token is validated - then returned by acquirer. | |
| </searchtable> | </searchtable> | ||
| \\ | \\ | ||
| Line 139: | Line 139: | ||
| <searchtable> | <searchtable> | ||
| ^ **CONSTRAINT** ^ **DESCRIPTION** ^ | ^ **CONSTRAINT** ^ **DESCRIPTION** ^ | ||
| - | | C001 | If invalid parameter values are sent, an Error Page will appear and the web browser will not be redirected to the Secure Card Receipt Page. This should not happen in a production environment after integration is completed. | | + | | C001 | If invalid parameter values are sent, an Error Page will appear and the web browser will not be redirected to the Secure Token Receipt Page. This should not happen in a production environment after integration is completed. | |
| </searchtable> | </searchtable> | ||
| \\ | \\ | ||