High Risk Transaction Updated

A high_risk_transaction_updated event is fired when a transaction already flagged as high risk is accepted or rejected.

Information sent in the payload for a high_risk_transaction_updated webhook is summarised in the table below.

PropertyTypeDescriptionExample
alert_idstringThe unique identifier for this Paddle webhook alert. Integer value sent as a string.
alert_namestringThe alert name.
high_risk_transaction_updated
case_idstringThe case id for the flagged order.
checkout_idstringThe checkout id of the order created.27835673-chre93c81118fc7-b3092639c1
created_atstring<date-time>Date and time this order was flagged.
customer_email_addressstring<email>The email address of the customer.
customer_user_idstringThe customer user ID.
custom_datastringA JSON encoded string of custom data that was passed into the checkout for this purchase{"external_id": 42}
event_timestring<date-time>The date and time the event was triggered in UTC (Coordinated Universal Time).
marketing_consentintegerThe value of this field 0 or 1 indicates whether the user has agreed to receive marketing messages from the vendor.
Allowed values: 0 1
order_idstringThe Paddle Order ID for this payment. This can be used to look up the order within your Vendor Dashboard.
p_signaturestringThis field contains an encrypted token that you can use to verify the request authenticity. See Verifying Webhooks.
passthroughstringThis field contains any values that you passed into the checkout using the passthrough parameter. See the Pass Parameters documentation for more information.
Max Length: `<=1000 characters
product_idstringThe dashboard ID of the product purchased in this order.
statusstringThe status of the flagged order.
Allowed values: accepted rejected