Alerts Created Event

wbhk

alerts.created

The Alert Created webhook is available exclusively for Chargeflow Alerts customers. It notifies your system in real time whenever a new pre-chargeback alert is created for your account. When a new alert is received by Chargeflow, the webhook sends an HTTP POST request to your configured endpoint containing the alert ID and key metadata.

Merchants can use this webhook to:

Trigger automated workflows (e.g., refund, order cancellation, tagging) immediately when an alert is received.
Ingest alerts into internal systems for logging, monitoring, or case management.
Notify relevant teams (support, fraud, risk) without needing to poll the API.

The webhook payload includes the alert ID and basic fields typically available at ingestion. For full alert details—which may evolve over time (e.g., matched transaction ID, refund status)—you can call the Get Alert by ID endpoint.

Payload

string

required

The unique identifier of the alert

account_id

string

required

The account identifier associated with the alert

ext_account_id

string

The external account identifier from the platform

transaction_id

string

The transaction identifier associated with the alert

created_at

string

The date when the alert was created

network_transaction

object

Network transaction details associated with the alert

status_date

string

The date when the status was last updated

status

string

The current status of the alert. Status can be one of the following: alerted, pending, refund_initiated, prevented.

statement_descriptor

string

The statement descriptor for the transaction.

amount

number

The amount associated with the alert

currency

string

The currency of the alert amount

outcome

string

The outcome of the alert. Outcome can be one of the following: duplicate, not_found, prevented, pending, chargebacked, previously_refunded, error.

type

string

The type of alert. Type can be one of the following: fraud_warning, ethoca, cdrn, rdr, other.

reason

string

The reason for the alert. Reason can be one of the following: fraud, processing, authorization, service.

Response

200

Payload

Choose an example