Event payloads

Every delivery wraps its event in the envelope described in the Webhooks guide. This page lists the data object for each event type under api_version 2026-10-07. Fields can be added without a new version, so ignore fields you do not recognize; see Versioning.

Conventions

These rules hold for every event type, so they are stated once here.

Every data object carries organization_id, in addition to the envelope’s own organization_id.
Field names match the public API. A field that names the same thing as an API response field uses the same name: external_id, reward_id, status, provider_order_id.
Optional fields are omitted when absent. No field is ever sent as null. Treat a missing key and a null the same way when you parse.
Amounts are decimal strings, such as "100.00". face_value_minor is the one integer amount, because gift-card face values are integer minor units.
Related resources are named by their public id: redemption_id, reversal_id, reservation_id, event_id, fulfillment_id, fulfillment_account_id, reward_id.

Each event type is a movement event or a lifecycle event. The fields a family shares are listed once at the start of its section.

Movement events

A movement event announces one journal entry. Every journal action has exactly one movement event. A participant or group balance changes only through movement events that name it as the subject, the counterparty, or a transfer source or recipient, so those events reconstruct every participant and group balance. Program wallet balances cannot be reconstructed from webhooks, because prefunded issuance, voids, and settlement differences post to the wallet without an event naming it. Reconcile wallets with Get program balance or Get program statement. Every movement event carries these fields.

Field	Present	Description
`journal_entry_id`	Always	The journal entry this event announces. Read it with `GET /v1/journal-entries/{id}`.
`organization_id`	Always	Your organization.
`asset_id`	Always	The asset that moved.
`amount`	Always	The amount that moved, as a decimal string. Each event below states what it measures.
`participant_id` or `group_id`	One of the two, except in the program-wallet form	The account owner.
`program_id`	When the journal entry has one	The program the entry ran under. Each event below states when it is present.
`lot_count`	Stated per event	The number of existing lots the entry consumed, moved, or restored. Always present on `balance.expired`, `balance.matured`, and `balance.voided`. Present for `LOT` assets and omitted for `SIMPLE` assets on `balance.redeemed`, `balance.forfeited`, and a redemption reversal in `balance.reversed`. Never present on the other movement events.
`reference_id`	When the entry has one	The journal entry’s correlation reference.
`counterparty`	`balance.redeemed`, and a redemption reversal in `balance.reversed`, when the program’s redemption target is a group or program wallet	The group or program wallet on the other side of the entry: `{"type": "GROUP", "group_id": "..."}` or `{"type": "PROGRAM", "program_id": "..."}`. Omitted when the target is a system account. `transfer.completed` names its other side in `recipients` instead.

Target forms

Exactly one of participant_id or group_id identifies the account owner. The examples on this page show the participant form. The group form is identical, with group_id in place of participant_id. When the account owner is a program wallet, for example a CREDIT or DEBIT rule action with "target": {"type": "PROGRAM"}, the payload has neither participant_id nor group_id. Its program_id is both the program and the target. This is the program-wallet form. program.funded and program.burned always use it.

`balance.credited`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "100.00",
  "bucket": "AVAILABLE",
  "reference_id": "auth_12345",
  "settle": {"held_amount": "80.00", "delta": "20.00"}
}

amount is the value credited.

Field	Present	Description
`program_id`	Always	The program that issued the credit.
`bucket`	Always	The bucket credited: `AVAILABLE`, `HELD`, or `DEFERRED`.
`reference_id`	When the credit carries one	A credit to `HELD` with a `reference_id` is a provisional reward. A later credit to `AVAILABLE` with the same `reference_id` settles it. See Balance operations.
`settle`	Settlement only	`held_amount` is the total held under the reference before settlement. `delta` is the settled amount minus `held_amount`: positive for an over-capture, negative for an under-capture.

A credit or settlement into DEFERRED sends balance.credited with bucket: "DEFERRED". balance.matured follows when that value becomes spendable.

`balance.debited`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "100.00",
  "bucket": "AVAILABLE"
}

amount is the value debited.

Field	Present	Description
`program_id`	Always	The program the debit ran under.
`bucket`	Always	The bucket debited.

`balance.held` and `balance.released`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "100.00",
  "reference_id": "auth_12345"
}

balance.held announces value moving from AVAILABLE to HELD. balance.released announces value moving from HELD back to AVAILABLE. amount is the value moved.

Field	Present	Description
`program_id`	Always	The program the hold or release ran under.
`reference_id`	When the hold or release carries one	The correlation reference. A pending redemption’s authorization emits `balance.held` with the reservation’s reference.

A fail or cancel of a pending redemption that releases live reserved value emits balance.released.

`balance.voided`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "100.00",
  "reference_id": "auth_12345",
  "lot_count": 1
}

amount is the HELD value voided back to its source, the program wallet or system issuance. When the void request asked for more than the provisional rewards left under the reference, amount is the smaller amount that was voided.

Field	Present	Description
`program_id`	Always	The program the void ran under.
`reference_id`	Always	The hold reference the void targeted.
`lot_count`	Always	The number of provisional lots the void touched.

`balance.expired`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "35.0",
  "lot_count": 3
}

amount is the total forfeited to breakage. One event covers every lot of one asset in one bucket that expired for the same participant or group in the same sweep. The expiration journal entry has no program, so program_id is omitted.

Field	Present	Description
`program_id`	Never	The expiration entry runs under no program.
`lot_count`	Always	The number of lots that expired in this entry.

`balance.matured`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "100.00",
  "lot_count": 2,
  "issuer_programs": [
    {"program_id": "uuid", "amount": "100.00", "lot_count": 2}
  ],
  "reference_ids": ["auth_12345", "auth_67890"]
}

balance.matured announces lots in DEFERRED reaching matures_at and moving to AVAILABLE. One event can cover several lots of the same asset for the same participant, group, or program wallet, including lots that different programs issued for a shared asset. amount is the total that became spendable.

Field	Present	Description
`program_id`	Depends on the target	See the table below.
`lot_count`	Always	The number of lots that matured in this entry.
`issuer_programs`	Always	Splits `amount` and `lot_count` by the program that issued each lot. Each entry has `amount`, `lot_count`, and `program_id`. The entries add up to the top-level `amount` and `lot_count`, sorted by `program_id`. An entry without `program_id` covers lots whose issuing program is unknown and is always last.
`reference_ids`	When any matured lot has a `reference_id`	The distinct `reference_id` values of the matured lots, sorted.

When programs share an asset, one event can include lots that different programs issued:

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "100.00",
  "lot_count": 4,
  "issuer_programs": [
    {"program_id": "uuid", "amount": "60.00", "lot_count": 2},
    {"program_id": "uuid", "amount": "30.00", "lot_count": 1},
    {"amount": "10.00", "lot_count": 1}
  ]
}

The meaning of the top-level program_id depends on the target:

Target	Target field	`program_id`
Participant	`participant_id`	The program that issued every lot in the event. Omitted when the lots came from more than one program or when any lot’s issuing program is unknown.
Group	`group_id`	Same as for a participant.
Program wallet	None. The payload has no `participant_id` or `group_id`.	The program that owns the wallet. This holds even when another program issued the lots.

Read issuer_programs to see how much of amount each program issued. An endpoint subscribed to balance.matured receives the event for every program in your organization. A lot whose expires_at has already passed is forfeited by expiration and sends balance.expired instead of maturing.

`balance.redeemed`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "50.00",
  "bucket": "HELD",
  "reference_id": "scrip:rsv:...",
  "lot_count": 1,
  "redemption_id": "uuid",
  "counterparty": {"type": "GROUP", "group_id": "uuid"}
}

balance.redeemed announces the REDEMPTION journal entry of a redemption. amount is the value redeemed. An instant redemption spends from AVAILABLE. A pending redemption that is captured spends from HELD. journal_entry_id matches the redemption’s journal_entry_id for an instant redemption and its capture_journal_entry_id for a capture.

Field	Present	Description
`program_id`	Always	The program the redemption ran under.
`bucket`	Always	`AVAILABLE` for an instant redemption, `HELD` for a capture.
`reference_id`	Capture only	The reservation’s reference, the same value the authorization’s `balance.held` carried.
`lot_count`	`LOT` assets, omitted for `SIMPLE` assets	The number of lots consumed.
`redemption_id`	Always	The redemption. The matching `redemption.completed` carries its lifecycle view.
`counterparty`	When the redemption target is a group or program wallet	The group or program wallet that gained `amount`. Omitted for the `SYSTEM_REDEMPTION` and `SYSTEM_BREAKAGE` targets.

`balance.forfeited`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "40.00",
  "bucket": "AVAILABLE",
  "lot_count": 1
}

balance.forfeited announces a FORFEIT journal entry: Forfeit participant balance, Forfeit group balance, or a FORFEIT rule action. amount is the value forfeited to breakage. A forfeit whose filters matched no lots posts no journal entry and sends nothing. Expiration forfeits send balance.expired instead.

Field	Present	Description
`program_id`	Always	The program the forfeit ran under.
`bucket`	Always	The bucket the value left: `AVAILABLE` or `HELD`.
`lot_count`	`LOT` assets, omitted for `SIMPLE` assets	The number of lots consumed.

`balance.reversed`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "50.00",
  "bucket": "AVAILABLE",
  "lot_count": 1,
  "redemption_id": "uuid",
  "counterparty": {"type": "GROUP", "group_id": "uuid"}
}

balance.reversed announces a REVERSAL journal entry. Exactly one of redemption_id or event_id names what was reversed, and it tells you which way the value moved. amount is the value this entry moved.

Field	Present	Description
`program_id`	When the reversed entry had one	The program of the reversed entry.
`bucket`	Almost always	`AVAILABLE` for a redemption reversal. For an event reversal, the bucket the value was clawed back from: `AVAILABLE`, or `DEFERRED` for an award that had not matured. Omitted in the rare case that one line recovered value from both buckets; the journal entry’s postings then show the split.
`lot_count`	`LOT` assets	The number of lots restored or consumed. Omitted for a `SIMPLE`-asset redemption reversal. Always present for an event reversal, because only `LOT` assets can be event-reversed.
`redemption_id`	Redemption reversals	Value returned to the participant’s `AVAILABLE` bucket. `redemption.reversed` carries the lifecycle view.
`event_id`	Event reversals	Value clawed back out of `bucket` and returned to the issuance source. One event per reversed award line. `event.reversed` carries the lifecycle view with every line.
`counterparty`	Redemption reversals, when the original redemption credited a group or program wallet	The group or program wallet that gave `amount` back. Omitted for system-account targets. Never present on an event reversal.

`transfer.completed`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "source_participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "150.00",
  "splits_count": 2,
  "recipients": [
    {"participant_id": "uuid", "amount": "100.00"},
    {"group_id": "uuid", "amount": "50.00"}
  ]
}

amount is the total moved out of the source, which is the sum of the recipient amounts.

Field	Present	Description
`program_id`	Always	The program the transfer ran under.
`source_participant_id` or `source_group_id`	One of the two	The source account owner.
`splits_count`	Always	The number of recipients.
`recipients`	Always	One entry per recipient, with exactly one of `participant_id` or `group_id` and the `amount` that recipient received. Source and recipient types can differ.

`program.funded` and `program.burned`

{
  "journal_entry_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "asset_id": "uuid",
  "amount": "1000.00"
}

Both always use the program-wallet form. program.funded announces value entering a program wallet from system issuance. program.burned announces value leaving a program wallet to system breakage. amount is the value funded or burned. There are no fields beyond the shared set.

Lifecycle events

A lifecycle event announces a resource changing state. It carries the resource id, the resource’s status where it has one, and the ids of related resources. It never carries a journal entry id; the matching movement event does.

`redemption.pending`, `redemption.completed`, `redemption.failed`, and `redemption.cancelled`

The four redemption status events share one shape, built from the redemption resource.

redemption.pending

{
  "redemption_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "50.0",
  "status": "PENDING",
  "reward_id": "uuid",
  "quantity": 2,
  "reservation_id": "uuid",
  "expires_at": "2026-01-15T11:30:00Z"
}

redemption.failed

{
  "redemption_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "50.0",
  "status": "FAILED",
  "reward_id": "uuid",
  "quantity": 2,
  "failure_reason": "provider_rejected"
}

Field	Present	Description
`redemption_id`	Always	The redemption.
`organization_id`, `program_id`, `participant_id`, `asset_id`	Always	The redemption’s organization, program, participant, and asset.
`amount`	Always	The redemption amount, as a decimal string.
`status`	Always	The redemption’s status when the event fired: `PENDING`, `COMPLETED`, `FAILED`, or `CANCELLED`.
`reward_id`, `quantity`	Catalog redemptions	The reward and the number of units. Amount redemptions omit both.
`reservation_id`, `expires_at`	`redemption.pending` only	`reservation_id` identifies the ledger reservation backing the authorization. `expires_at` is the effective capture deadline: the earliest of the request deadline, the program’s `pending_redemption_ttl`, and the backing lots’ expiration. Schedule fulfillment from this value instead of computing it from your request. See Use the returned deadline.
`failure_reason`	`redemption.failed` and `redemption.cancelled`, when one was supplied	An automatic timeout uses `failure_reason: "expired"`.

Each redemption status event pairs with one movement event:

Lifecycle event	Movement event
`redemption.pending`	`balance.held`
`redemption.completed` for an instant redemption	`balance.redeemed` with `bucket: "AVAILABLE"`
`redemption.completed` for a captured pending redemption	`balance.redeemed` with `bucket: "HELD"`
`redemption.failed` or `redemption.cancelled`	`balance.released`, when live reserved value was released

`redemption.reversed`

{
  "reversal_id": "uuid",
  "redemption_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "asset_id": "uuid",
  "amount": "50.0",
  "status": "FULLY_REVERSED",
  "reward_id": "uuid",
  "quantity": 1
}

This event leads with the reversal. It pairs with balance.reversed carrying the same redemption_id.

Field	Present	Description
`reversal_id`	Always	The reversal.
`redemption_id`	Always	The redemption that was reversed.
`organization_id`, `program_id`, `participant_id`, `asset_id`	Always	The redemption’s organization, program, participant, and asset.
`amount`	Always	The value this reversal returned.
`status`	Always	The redemption’s status after the reversal: `PARTIALLY_REVERSED` or `FULLY_REVERSED`.
`reward_id`	Catalog redemptions	The reward.
`quantity`	Unit-based catalog redemptions	The number of units this reversal returned.

`redemption.fulfillment_succeeded` and `redemption.fulfillment_failed`

redemption.fulfillment_succeeded

{
  "fulfillment_id": "uuid",
  "redemption_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "fulfillment_account_id": "uuid",
  "status": "SUCCEEDED",
  "provider": "TREMENDOUS",
  "provider_order_id": "ord_abc123",
  "face_value_minor": 2500,
  "face_currency": "USD"
}

redemption.fulfillment_failed

{
  "fulfillment_id": "uuid",
  "redemption_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "fulfillment_account_id": "uuid",
  "status": "FAILED",
  "provider": "TREMENDOUS",
  "face_value_minor": 2500,
  "face_currency": "USD",
  "failure_reason": "provider_permanent_error"
}

These events announce the outcome of a gift-card order. They never carry a claim link or any other credential. Retrieve the card’s URL with Create a claim link after success.

Field	Present	Description
`fulfillment_id`	Always	The fulfillment.
`redemption_id`	Always	The redemption the order belongs to.
`organization_id`, `program_id`, `participant_id`	Always	The redemption’s organization, program, and participant.
`fulfillment_account_id`	Always	The fulfillment account that paid for the order.
`status`	Always	The fulfillment status, as on the redemption’s `fulfillment` object: `SUCCEEDED` or `FAILED`.
`provider`	Always	The fulfillment account’s provider.
`provider_order_id`	Once an order was placed	The vendor’s order id. Omitted when the failure happened before any order was placed. Present on the failed event when a placed order later failed.
`face_value_minor`, `face_currency`	Always	The card’s face value in integer minor units, and its currency.
`failure_reason`	`redemption.fulfillment_failed` only, always present there	See Failure reasons.

`fulfillment_account.funds_low`

{
  "organization_id": "uuid",
  "fulfillment_account_id": "uuid",
  "provider": "TREMENDOUS",
  "redemption_id": "uuid",
  "fulfillment_id": "uuid",
  "program_id": "uuid",
  "participant_id": "uuid",
  "face_value_minor": 2500,
  "face_currency": "USD"
}

Sent the first time a gift-card order enters AWAITING_FUNDS because the fulfillment account could not cover it. Add funds to the account in the dashboard; Scrip then retries the order. Repeated low-balance responses for the same fulfillment do not send another alert. If the funding window ends before the account is funded, the order fails with failure_reason: "insufficient_funds" and redemption.fulfillment_failed follows. See Handle a pending order. This event never carries a claim link.

Field	Present	Description
`organization_id`	Always	Your organization.
`fulfillment_account_id`	Always	The account that needs funds.
`provider`	Always	The account’s provider.
`redemption_id`, `fulfillment_id`	Always	The order that is waiting.
`program_id`, `participant_id`	Always	The program and participant of that redemption.
`face_value_minor`, `face_currency`	Always	The card value the account could not cover.

`fulfillment_account.status_changed`

{
  "organization_id": "uuid",
  "fulfillment_account_id": "uuid",
  "provider": "TREMENDOUS",
  "previous_status": "PENDING_REVIEW",
  "status": "ACTIVE",
  "status_reason": "reauth_required"
}

Sent when a fulfillment account’s status changes: onboarding progresses, the account is approved or rejected, you enable or disable it, or it needs to be reconnected. This event never carries a session URL or credential. Reconnect or remove the account in the dashboard.

Field	Present	Description
`organization_id`	Always	Your organization.
`fulfillment_account_id`	Always	The account.
`provider`	Always	The account’s provider.
`previous_status`	Always	The status before the change.
`status`	Always	The status after the change: `PENDING_ONBOARDING`, `PENDING_REVIEW`, `ACTIVE`, `DISABLED`, or `REJECTED`.
`status_reason`	When the account carries one	Set for `REJECTED`, and for a `DISABLED` account that cannot be re-enabled as it is. `reauth_required` means reconnect it. `provider_disconnected` means delete it and connect again. See Get a fulfillment account.

`reward.status_changed`

{
  "reward_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "previous_status": "ACTIVE",
  "status": "OUT_OF_STOCK"
}

previous_status and status are always different; a same-status write produces no event. Creating a reward does not send this event. See Reward status events for what triggers it.

Field	Present	Description
`reward_id`	Always	The reward.
`organization_id`, `program_id`	Always	The reward’s organization and program.
`previous_status`	Always	The status before the change.
`status`	Always	The status after the change: `DRAFT`, `ACTIVE`, `OUT_OF_STOCK`, or `ARCHIVED`.

`participant.created`

{
  "participant_id": "uuid",
  "organization_id": "uuid",
  "external_id": "user_123",
  "status": "ACTIVE",
  "program_id": "uuid"
}

Field	Present	Description
`participant_id`	Always	The participant.
`organization_id`	Always	Your organization.
`external_id`	Always	Your identifier for the participant, as on the participant resource.
`status`	Always	The status the participant was created in: `ACTIVE`, `SUSPENDED`, or `CLOSED`, as on the participant resource. `POST /v1/participants` can create a participant as `SUSPENDED` or `CLOSED`. A participant an event created is `ACTIVE`.
`program_id`	When the creating call enrolled the participant	Set for `POST /v1/participants` with `program_id`, and for every participant an event created. Omitted otherwise.

`participant.tier_changed`

{
  "participant_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "tier": "loyalty",
  "level": "gold"
}

Exactly one of participant_id, group_id, or program_id identifies the target of the tier change. When the target is a program, program_id is both the target and the program. The SET_TIER rule action can target groups and programs through its target field, so do not assume the target is a participant.

Field	Present	Description
`participant_id`, `group_id`, or `program_id`	Exactly one	The target of the tier change.
`organization_id`	Always	Your organization.
`program_id`	Always	The program the tier belongs to.
`tier`	Always	The tier’s key.
`level`	When a level was assigned	The new level. Omitted when the tier was removed, which is a downgrade to base.

`event.completed`

{
  "event_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid"
}

Field	Present	Description
`event_id`	Always	The event whose rules ran.
`organization_id`, `program_id`	Always	The event’s organization and program.

`event.failed`

{
  "event_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "error": "description of what went wrong",
  "error_code": "participant_suspended"
}

Field	Present	Description
`event_id`	Always	The event that failed.
`organization_id`	Always	Your organization.
`program_id`	When the event resolved a program	Present for every failure after ingestion accepted the event. Omitted when the failure happened before the program was resolved.
`error`	Always	A description of what went wrong.
`error_code`	When the failure has a stable code	A machine-readable code such as `program_not_found`, `participant_suspended`, `participant_inactive`, or `program_inactive`. The same code is on the event resource from `GET /v1/events/{id}`, so you can branch on it without string-matching `error`. Failures without a stable code, such as an invalid payload, omit it.

`event.reversed`

{
  "reversal_id": "uuid",
  "event_id": "uuid",
  "organization_id": "uuid",
  "program_id": "uuid",
  "shortfall_policy": "report",
  "lines": [
    {
      "original_journal_entry_id": "uuid",
      "asset_id": "uuid",
      "requested": "54.25",
      "recovered": "54.25",
      "shortfall": "0.0"
    }
  ]
}

One event per reversal. Each line that recovered value pairs with one balance.reversed carrying the same event_id.

Field	Present	Description
`reversal_id`	Always	The reversal.
`event_id`	Always	The event that was reversed.
`organization_id`, `program_id`	Always	The event’s organization and program.
`shortfall_policy`	Always	The shortfall policy the reversal ran with, in the same lowercase form as the reverse request and response. `report` is currently the only value.
`lines`	Always	One entry per reversed award line: `original_journal_entry_id`, `asset_id`, and the `requested`, `recovered`, and `shortfall` amounts as decimal strings.

For endpoint setup, signature verification, and retry behavior, see the Webhooks guide.

Scrip API

Endpoints

Conventions

Movement events

Target forms

`balance.credited`

`balance.debited`

`balance.held` and `balance.released`

`balance.voided`

`balance.expired`

`balance.matured`

`balance.redeemed`

`balance.forfeited`

`balance.reversed`

`transfer.completed`

`program.funded` and `program.burned`

Lifecycle events

`redemption.pending`, `redemption.completed`, `redemption.failed`, and `redemption.cancelled`

`redemption.reversed`

`redemption.fulfillment_succeeded` and `redemption.fulfillment_failed`

`fulfillment_account.funds_low`

`fulfillment_account.status_changed`

`reward.status_changed`

`participant.created`

`participant.tier_changed`

`event.completed`

`event.failed`

`event.reversed`

​Conventions

​Movement events

​Target forms

​balance.credited

​balance.debited

​balance.held and balance.released

​balance.voided

​balance.expired

​balance.matured

​balance.redeemed

​balance.forfeited

​balance.reversed

​transfer.completed

​program.funded and program.burned

​Lifecycle events

​redemption.pending, redemption.completed, redemption.failed, and redemption.cancelled

​redemption.reversed

​redemption.fulfillment_succeeded and redemption.fulfillment_failed

​fulfillment_account.funds_low

​fulfillment_account.status_changed

​reward.status_changed

​participant.created

​participant.tier_changed

​event.completed

​event.failed

​event.reversed

Conventions

Movement events

Target forms

`balance.credited`

`balance.debited`

`balance.held` and `balance.released`

`balance.voided`

`balance.expired`

`balance.matured`

`balance.redeemed`

`balance.forfeited`

`balance.reversed`

`transfer.completed`

`program.funded` and `program.burned`

Lifecycle events

`redemption.pending`, `redemption.completed`, `redemption.failed`, and `redemption.cancelled`

`redemption.reversed`

`redemption.fulfillment_succeeded` and `redemption.fulfillment_failed`

`fulfillment_account.funds_low`

`fulfillment_account.status_changed`

`reward.status_changed`

`participant.created`

`participant.tier_changed`

`event.completed`

`event.failed`

`event.reversed`