Difference between revisions of "Setting/propertiesnotifydata"
Jump to navigation
Jump to search
Markkinchin (talk | contribs) |
Markkinchin (talk | contribs) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Select optional data to include | + | Select optional data to include with the notification |
| − | CVC is the | + | CVC is the security code of the credit card if one exists for this booking. |
Token is the token required to retrieve the Card for this booking from the JSON getCard API function. | Token is the token required to retrieve the Card for this booking from the JSON getCard API function. | ||
| − | JSON getCard is only available to PCI DSS compliant partners | + | <span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span>JSON getCard is only available to PCI DSS compliant partners |
| − | POST DATA will only be included in the message if you use https:// | + | <span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span>POST DATA will only be included in the message if you use https:// |
| + | |||
| + | |||
| + | |||
| + | Version 1 Webhook: The cvv and token fields are included as form url encoded POST data in the body of the notification. | ||
| + | |||
| + | Version 2 Webhook: The cvv and token fields are included in the JSON body of the notification | ||
Latest revision as of 11:07, 16 October 2024
Select optional data to include with the notification
CVC is the security code of the credit card if one exists for this booking.
Token is the token required to retrieve the Card for this booking from the JSON getCard API function.
JSON getCard is only available to PCI DSS compliant partners
POST DATA will only be included in the message if you use https://
Version 1 Webhook: The cvv and token fields are included as form url encoded POST data in the body of the notification.
Version 2 Webhook: The cvv and token fields are included in the JSON body of the notification
