Skip to main content
The payload for a webhook is a single event referencing a resource that has recently changed. The target object is a summary of that resource, captured when the event occurred. It contains a subset of the fields that the API returns for the resource, and some fields that only appear in webhooks, such as payment_link_id on transactions. Gr4vy stores the payload when the event occurs, so a retried delivery sends the same snapshot, even if the resource has changed since. Fetch the resource from the API before you take an irreversible action, such as shipping an order, or when you need a field that the summary doesn’t include, such as a transaction’s cart items or 3-D Secure details.

Transaction payloads

In a transaction event, payment_method is null when the transaction has no payment method. buyer is null unless the transaction has at least one of a buyer ID, display name, external identifier, account number, or billing details. A guest checkout can have billing details without a buyer, in which case buyer.id is null.
Transaction payloads can contain personal data, such as the buyer’s name, email address, phone number, and address, and any personal data you put in metadata. Mask or remove these fields before you log a webhook payload.