{
"transaction": {
"id": "lctx_15d2f5a39b461",
"card_id": "lcrd_28c4e7b195fa",
"program_id": "lprg_3e8a1c74d952",
"member_id": "lmbr_91f6b2e84a37",
"card_definition_id": "lcdef_6a2d9f41c783",
"card_type": "INDIVIDUAL",
"type": "POINTS_SPENT_ON_ORDER",
"details": {
"reason": "Points spent on order payment",
"rejection": null,
"metadata": {},
"points": {
"total": 200
},
"order": {
"id": "ord_6a2d9f41c783"
},
"order_transaction": {
"id": "lotx_91f6b2e84a37"
}
},
"status": "APPROVED",
"created_at": "2026-09-07T09:15:43.091Z",
"updated_at": "2026-09-07T09:15:43.284Z",
"object": "card_transaction"
}
}Points spent on order
Event data sent for a Loyalty v2 POINTS_SPENT_ON_ORDER transaction handled by Workflows
WEBHOOK
POINTS_SPENT_ON_ORDER
{
"transaction": {
"id": "lctx_15d2f5a39b461",
"card_id": "lcrd_28c4e7b195fa",
"program_id": "lprg_3e8a1c74d952",
"member_id": "lmbr_91f6b2e84a37",
"card_definition_id": "lcdef_6a2d9f41c783",
"card_type": "INDIVIDUAL",
"type": "POINTS_SPENT_ON_ORDER",
"details": {
"reason": "Points spent on order payment",
"rejection": null,
"metadata": {},
"points": {
"total": 200
},
"order": {
"id": "ord_6a2d9f41c783"
},
"order_transaction": {
"id": "lotx_91f6b2e84a37"
}
},
"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_ORDER event indicates that points were spent on an order 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_ORDER 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.
Paying with points also creates a separate PAY_WITH_POINTS order transaction. That payload is not included in this event. Use the Pay with points event to get details about the order transaction.Body
application/json
Event data object schema for POINTS_SPENT_ON_ORDER.
A Loyalty v2 card transaction with the POINTS_SPENT_ON_ORDER type.
Show child attributes
Show child attributes
Response
Webhook accepted
Last modified on September 25, 2026