> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voucherify.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Purchase

> Event data sent for a Loyalty v2 PURCHASE transaction handled by Workflows

The `PURCHASE` event indicates that a member purchased a Loyalty v2 reward.

<Note>
  This page documents only the event data nested under `data`. See [Introduction to webhooks](/api-reference/introduction-to-webhooks) for the shared webhook structure, and [Workflows webhooks](/api-reference/workflows-webhooks) for the full Workflows webhook payload.
</Note>

This event can trigger a workflow when **Loyalty transaction** is configured with the **Reward transactions** group and the `PURCHASE` transaction type. If the workflow reaches a **Webhook callout** action, Voucherify sends a webhook to the action's target URL.

Workflows send this transaction in the `data.trigger` object. The example uses the `APPROVED` status. A workflow can filter the trigger by transaction status: `PENDING`, `PROCESSING`, `APPROVED`, `REJECTED`, or `REFUNDED`. The matched status is available in `data.trigger.transaction.status`; it does not create a separate event type. When a purchase is later refunded, the same `PURCHASE` event type is dispatched again with the `REFUNDED` status.

Purchasing a reward also creates a separate `POINTS_SPENT_ON_REWARD` card transaction. That payload is not included in this event. Use the [Points spent on reward event](/api-reference/loyalty-transactions/card/points-spent-on-reward) to get details about the card transaction. When the reward credits points to another Loyalty v2 card, Voucherify also creates a separate `POINTS_PURCHASED` transaction on the destination card. Use the [Points purchased event](/api-reference/loyalty-transactions/card/points-purchased) for that payload.


## OpenAPI

````yaml openapi-events/events-loyalty-transaction.json webhook PURCHASE
openapi: 3.1.0
info:
  title: Events - Events loyalty transaction
  version: '2024-01-01'
  description: ''
servers: []
security: []
paths: {}

````