{"id":8330,"date":"2026-08-20T10:41:14","date_gmt":"2026-08-20T02:41:14","guid":{"rendered":"https:\/\/www.fraudlabspro.com\/resources\/?post_type=docs&p=8330"},"modified":"2026-08-20T10:41:15","modified_gmt":"2026-08-20T02:41:15","password":"","slug":"introducing-new-payload-format-for-custom-webhook","status":"publish","type":"docs","link":"https:\/\/www.fraudlabspro.com\/resources\/tutorials\/introducing-new-payload-format-for-custom-webhook\/","title":{"rendered":"Introducing New Payload Format for Custom Webhook"},"content":{"rendered":"\n
\"New<\/figure>\n\n\n\n

Introduction<\/h2>\n\n\n\n

We are pleased to introduce the updated custom webhook notification payload for FraudLabs Pro, designed to streamline real-time transaction tracking and offer seamless integration for your fraud detection workflows. Transitioning to a structured JSON format, the new payload delivers key transaction data\u2014including order id, customer name and email, and order amount\u2014directly to your custom endpoint. This modernization improves data readability, simplifies server-side parsing, and ensures your system receives reliable, instant updates whenever order statuses or manual review decisions are triggered in the FraudLabs Pro merchant portal.<\/p>\n\n\n\n

<\/div>\n\n\n\n

What\u2019s New in the Custom Webhook<\/h2>\n\n\n\n

Compared to the V1 payload, which used the id<\/code> and action<\/code> fields, the V2 payload uses more descriptive field names and includes additional transaction and customer information. The table below highlights the changes between the two payload versions.<\/p>\n\n\n\n

V1 Field<\/strong><\/td>V2 Field<\/strong><\/td>Description<\/strong><\/td><\/tr>
id<\/code><\/td>fraudlabspro_id<\/code><\/td>The unique identifier for the transaction.<\/td><\/tr>
action<\/code><\/td>fraudlabspro_status<\/code><\/td>The final action based on the rules analysis.<\/td><\/tr>
–<\/td>user_order_id<\/code><\/td>The merchant identifier used to uniquely identify a transaction.<\/td><\/tr>
–<\/td>full_name<\/code><\/td>The user’s first and last name.<\/td><\/tr>
–<\/td>email<\/code><\/td>The user’s email address.<\/td><\/tr>
–<\/td>currency<\/code><\/td>The currency used in the transaction in ISO-4217 (3 characters) format.<\/td><\/tr>
–<\/td>amount<\/code><\/td>The total amount of the transaction.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

This is a sample response in JSON:<\/p>\n\n\n\n