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 Both sides next revision
developer:api_specification:hpp_secure_card_features [2018/10/26 09:17]
thiago123 Adding nuvei constraints
developer:api_specification:hpp_secure_card_features [2018/12/24 11:27]
thiago123 [Request Body Fields]
Line 20: Line 20:
 | TERMINALID | Y | A TerminalID provided by %CompanyName. | | TERMINALID | Y | A TerminalID provided by %CompanyName. |
 | MERCHANTREF| Y | Unique reference assigned by the Merchant site/ solution to identify the stored card details. The length is limited to 48 characters. | | MERCHANTREF| Y | Unique reference assigned by the Merchant site/ solution to identify the stored card details. The length is limited to 48 characters. |
-| RECEIPTPAGEURL | N | Receipt url used to send the response of the registration back. It works as a webhook where the gateway expects a URL pointing to a feature available at the merchant'​s domain, to process the response of the secure card registration/​ update. | 
 | EMAIL | N | Cardholder e-mail, which is going to be used, if sent, to provide the cardholder with receipt notifications when the transactions is processed. See note **ND0003 - E-mail field behavior and settings**. | | EMAIL | N | Cardholder e-mail, which is going to be used, if sent, to provide the cardholder with receipt notifications when the transactions is processed. See note **ND0003 - E-mail field behavior and settings**. |
 | 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. |
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International