High risk transaction updated
Summary
Section titled “Summary”A high_risk_transaction_updated event is fired when a transaction already flagged as high risk is accepted or rejected.
Payload
Section titled “Payload”Information sent in the payload for a high_risk_transaction_updated webhook is summarised in the table below.
| Property | Type | Description | Example |
|---|---|---|---|
| alert_id | string | The unique identifier for this Paddle webhook alert. Integer value sent as a string. | |
| alert_name | string | The alert name. high_risk_transaction_updated |
|
| case_id | string | The case id for the flagged order. | |
| checkout_id | string | The checkout id of the order created. | 27835673-chre93c81118fc7-b3092639c1 |
| created_at | string<date-time> | Date and time this order was flagged. | |
| customer_email_address | string<email> | The email address of the customer. | |
| customer_user_id | string | The customer user ID. | |
| custom_data | string | A JSON encoded string of custom data that was passed into the checkout for this purchase | {"external_id": 42} |
| event_time | string<date-time> | The date and time the event was triggered in UTC (Coordinated Universal Time). | |
| marketing_consent | integer | The 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_id | string | The Paddle Order ID for this payment. This can be used to look up the order within your Vendor Dashboard. | |
| p_signature | string | This field contains an encrypted token that you can use to verify the request authenticity. See Verifying Webhooks. | |
| passthrough | string | This 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_id | string | The dashboard ID of the product purchased in this order. | |
| status | string | The status of the flagged order. Allowed values: accepted rejected |