{
"transaction": {
"id": "lttx_8d2f5a39b461",
"card_id": "lcrd_28c4e7b195fa",
"program_id": "lprg_3e8a1c74d952",
"member_id": "lmbr_91f6b2e84a37",
"card_definition_id": "lcdef_6a2d9f41c783",
"tier_structure_id": "lts_3e8a1c74d952",
"tier_id": "lt_91f6b2e84a37",
"status": "APPROVED",
"created_at": "2026-09-09T10:15:43.091Z",
"updated_at": "2026-09-09T10:15:43.284Z",
"object": "tier_transaction",
"type": "UPGRADED",
"details": {
"points": 1200,
"tier_from": "lt_6a2d9f41c783",
"tier_to": "lt_91f6b2e84a37",
"origin": {
"type": "card_operations",
"card_transaction_ids": [
"lctx_8d2f5a39b461"
]
},
"rejection": null,
"start_at": "2026-09-09T10:15:43.091Z",
"expires_at": "2027-09-09T23:59:59.999Z"
}
}
}Upgraded
Event data sent for a Loyalty v2 UPGRADED transaction handled by Workflows
WEBHOOK
UPGRADED
{
"transaction": {
"id": "lttx_8d2f5a39b461",
"card_id": "lcrd_28c4e7b195fa",
"program_id": "lprg_3e8a1c74d952",
"member_id": "lmbr_91f6b2e84a37",
"card_definition_id": "lcdef_6a2d9f41c783",
"tier_structure_id": "lts_3e8a1c74d952",
"tier_id": "lt_91f6b2e84a37",
"status": "APPROVED",
"created_at": "2026-09-09T10:15:43.091Z",
"updated_at": "2026-09-09T10:15:43.284Z",
"object": "tier_transaction",
"type": "UPGRADED",
"details": {
"points": 1200,
"tier_from": "lt_6a2d9f41c783",
"tier_to": "lt_91f6b2e84a37",
"origin": {
"type": "card_operations",
"card_transaction_ids": [
"lctx_8d2f5a39b461"
]
},
"rejection": null,
"start_at": "2026-09-09T10:15:43.091Z",
"expires_at": "2027-09-09T23:59:59.999Z"
}
}
}The
This event can trigger a workflow when Loyalty transaction is configured with the Tier transactions group and the
UPGRADED event indicates that a member moved to a higher Loyalty v2 tier.
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.UPGRADED 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, APPROVED, or REJECTED. The matched status is available in data.trigger.transaction.status; it does not create a separate event type.
details.tier_from and details.tier_to are tier IDs. They are not nested tier objects.Body
application/json
Event data object schema for UPGRADED.
A Loyalty v2 tier transaction with the UPGRADED type.
Show child attributes
Show child attributes
Response
Webhook accepted
Last modified on September 25, 2026