{
"transaction": {
"id": "lctx_16d2f5a39b461",
"card_id": "lcrd_28c4e7b195fa",
"program_id": "lprg_3e8a1c74d952",
"member_id": "lmbr_91f6b2e84a37",
"card_definition_id": "lcdef_6a2d9f41c783",
"card_type": "INDIVIDUAL",
"type": "POINTS_SPENT_ON_REWARD",
"details": {
"reason": "Points spent on reward",
"rejection": null,
"metadata": {},
"points": {
"total": 300
},
"reward": {
"id": "lrew_3e8a1c74d952"
},
"cost": {
"id": "lrcst_6a2d9f41c783"
},
"spending": {
"id": "lrspn_91f6b2e84a37"
},
"reward_transaction": {
"id": "lrtx_55bfc63a8142"
},
"target_card": null,
"purchase_transaction": null
},
"status": "APPROVED",
"created_at": "2026-09-07T09:15:43.091Z",
"updated_at": "2026-09-07T09:15:43.284Z",
"object": "card_transaction"
}
}Points spent on reward
Event data sent for a Loyalty v2 POINTS_SPENT_ON_REWARD transaction handled by Workflows
WEBHOOK
POINTS_SPENT_ON_REWARD
{
"transaction": {
"id": "lctx_16d2f5a39b461",
"card_id": "lcrd_28c4e7b195fa",
"program_id": "lprg_3e8a1c74d952",
"member_id": "lmbr_91f6b2e84a37",
"card_definition_id": "lcdef_6a2d9f41c783",
"card_type": "INDIVIDUAL",
"type": "POINTS_SPENT_ON_REWARD",
"details": {
"reason": "Points spent on reward",
"rejection": null,
"metadata": {},
"points": {
"total": 300
},
"reward": {
"id": "lrew_3e8a1c74d952"
},
"cost": {
"id": "lrcst_6a2d9f41c783"
},
"spending": {
"id": "lrspn_91f6b2e84a37"
},
"reward_transaction": {
"id": "lrtx_55bfc63a8142"
},
"target_card": null,
"purchase_transaction": null
},
"status": "APPROVED",
"created_at": "2026-09-07T09:15:43.091Z",
"updated_at": "2026-09-07T09:15:43.284Z",
"object": "card_transaction"
}
}The
This event can trigger a workflow when Loyalty transaction is configured with the Card transactions group and the
POINTS_SPENT_ON_REWARD event indicates that points were spent on a reward from a Loyalty v2 card.
This page documents only the event data nested under
data. See Introduction to webhooks for the shared webhook structure, and Workflows webhooks for the full Workflows webhook payload.POINTS_SPENT_ON_REWARD 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, or REJECTED. The matched status is available in data.trigger.transaction.status; it does not create a separate event type.
Purchasing a reward also creates a separate PURCHASE reward transaction. That payload is not included in this event. Use the Purchase event to get details about the reward transaction. When the purchased 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 to get details about the destination card transaction.Body
application/json
Event data object schema for POINTS_SPENT_ON_REWARD.
A Loyalty v2 card transaction with the POINTS_SPENT_ON_REWARD type.
Show child attributes
Show child attributes
Response
Webhook accepted
Last modified on September 25, 2026