Skip to main content
When webhooks are configured for your account, Chargeblast delivers notifications to your endpoint. Each request includes the headers and signing scheme described in Webhooks, including X-Event-Type, whose value is one of the event types below.
Alert events: alertCategory reflects the alert type (for example Ethoca, CDRN, RDR, TC40). Which types each alert webhook event supports is defined in the table; some events omit certain types by design.Deflection events: payloads use the deflection body schema (not the alert schema). See Webhooks (Deflection tab).
For payload field definitions and authentication, see Webhooks.

​
Alert events

​
Deflection events

​
Event details

​
alert.created

Fires when an alert record is first created and a created-style notification should go to subscribers. Covers normal provider ingest, Verifi/RDR notification paths when enabled, and manual replay or test sends from tooling.

​
alert.updated

Fires when an alert change should notify subscribers and the alert already has a matched charge (matched charge id present). Updates on unmatched alerts do not produce this event.

​
alert.refunded

Fires when Chargeblast treats the alert as refunded, including cases where Verifi delivers the alert already resolved/refunded. Can appear in quick succession after alert.created when the inbound state is pre-resolved. Not emitted for TC40.

​
alert.matched

Fires when the alert is confirmed matched to a single charge. The payload includes match metadata. Saving the same matched charge again without a meaningful change does not emit another alert.matched.

​
alert.will_expire

Ethoca and CDRN only. A scheduled job emits this approximately 46-48 hours before the alert expires, for eligible WIP alerts that still need attention. RDR and TC40 are not included. Each alert receives this event at most once (deduped).

​
alert.within_refund_rules

Fires when an alert is within your configured automation rules after the rules engine evaluates it (Ethoca, CDRN, and RDR only; not TC40). There is no deduplication; the same alert could receive this event again if the qualifying flow runs more than once. Not every alert.within_refund_rules is followed by alert.refunded; the refund step can still fail (or never run) even when this event fires.

​
deflection.created

Fires when Chargeblast first persists a deflection (CE or FPT). The JSON body is the deflection schema (Deflection tab), not an alert object. type is CE or FPT; status is one of Succeeded, Reversed, Failed, or Timeout.

​
deflection.updated

Fires when an existing deflection is updated for subscribers — typically a CE status change from a later Verifi notification, or after the deflection is billed (fees populated). Same deflection body schema as deflection.created.
  • Webhooks - Headers, body schema, signature verification
  • Alert types - Ethoca, CDRN, RDR, TC40, and other networks