Order processing completed

Summary

A locker_processed event is fired when an order is created after a successful payment event.

Payload

Information sent in the payload for a locker_processed 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. Default: locker_processed
checkout_id	string	The checkout id of the order created.	27835673-chre93c81118fc7-b3092639c1
checkout_recovery	string	The value of this field 0 or 1 indicates whether the order originated from a checkout recovery email. Allowed values: 0 1
coupon	string	The coupon code that was used on this order. Min Length: >=5 characters Max Length: <=300 characters
custom_data	string	A JSON encoded string of custom data that was passed into the checkout for this purchase	{"external_id": 42}
download	string<uri>	The download URL of the purchased product.
email	string<email>	The email address of the customer.
event_time	string<date-time>	The date and time the event was triggered in UTC (Coordinated Universal Time).
instructions	string	Instructions that have been sent to the customer.
licence	string	The license number associated with the order (when applicable).
marketing_consent	string	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.
product_id	string	The dashboard ID of the product purchased in this order.
quantity	string	The number of products or subscription seats sold in the transaction.
source	string	Referrer website URL(s) from where the traffic originated from.