Differences
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 [2022/03/04 10:35] lezlieh update with secure token |
developer:api_specification:hpp_secure_card_features [2022/03/04 10:36] lezlieh update with |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| 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. | 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** | ||