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_payment_features [2020/03/13 17:49] robinc [Notes and Details About the Request] |
developer:api_specification:hpp_payment_features [2022/03/31 08:30] (current) lezlieh update with secure token |
||
---|---|---|---|
Line 77: | Line 77: | ||
| STOREDCREDENTIALUSE | N |UNSCHEDULED, INSTALLMENT or RECURRRING. See note **ND008 - Stored Credential use field behavior and settings**.| | | STOREDCREDENTIALUSE | N |UNSCHEDULED, INSTALLMENT or RECURRRING. See note **ND008 - Stored Credential use field behavior and settings**.| | ||
| STOREDCREDENTIALTXTYPE | N | FIRST_TXN, SUBSEQUENT_MERCHANT_INITIATED_TXN or SUBSEQUENT_CARDHOLDER_INITIATED_TXN. See note **ND008 - Stored Credential use field behavior and settings**. | | | STOREDCREDENTIALTXTYPE | N | FIRST_TXN, SUBSEQUENT_MERCHANT_INITIATED_TXN or SUBSEQUENT_CARDHOLDER_INITIATED_TXN. See note **ND008 - Stored Credential use field behavior and settings**. | | ||
+ | | BYPASS_SURCHARGE | N | Send a value of 'true' to identify that surcharge has not been applied to this payment. Only applicable if surcharging is enabled for the terminal.| | ||
</searchtable> | </searchtable> | ||
Line 112: | Line 113: | ||
\\ | \\ | ||
- | **ND003 - Secure Card Registration by Payment Request** | + | **ND003 - Secure Token Registration by Payment Request** |
- | It is also possible to take advantage of a Payment Request to register a Secure Card. In this case, the following extra parameter should also be included at the request body: | + | It is also possible to take advantage of a Payment Request to register a Secure Token. In this case, the following extra parameter should also be included at the request body: |
^ **FIELD** ^ **REQUIRED** ^ **DESCRIPTION** ^ | ^ **FIELD** ^ **REQUIRED** ^ **DESCRIPTION** ^ | ||
Line 247: | Line 248: | ||
</WRAP> | </WRAP> | ||
- | * __When the original request also requested the registering of a Secure Card__: | + | * __When the original request also requested the registering of a Secure Token__: |
<WRAP center box 100%> | <WRAP center box 100%> | ||
Line 261: | Line 262: | ||
</WRAP> | </WRAP> | ||
- | * __When the original request also requested the registering of a Secure Card__: | + | * __When the original request also requested the registering of a Secure Token__: |
<WRAP center box 100%> | <WRAP center box 100%> | ||
Line 280: | Line 281: | ||
\\ | \\ | ||
- | **ND004 - Secure Card Registration by Payment Request** | + | **ND004 - Secure Token Registration by Payment Request** |
- | When the **SECURECARDMERCHANTREF** field is sent on request, the Payment Gateway understands that you desire to create a Secure Card from the | + | When the **SECURECARDMERCHANTREF** field is sent on request, the Payment Gateway understands that you desire to create a Secure Token from the |
card data used for the transaction. In this case, the following extra parameter are going to be added to the response body: | card data used for the transaction. In this case, the following extra parameter are going to be added to the response body: | ||
Line 294: | Line 295: | ||
- | For more details on this feature, visit the **[[merchant:new_merchant:products#secure_card|Products - Secure Card]]** section. | + | For more details on this feature, visit the **[[merchant:new_merchant:products#secure_card|Products - Secure Token]]** section. |