Alerts Outcome Updated Event

wbhk

alerts.outcome.updated

The Alert Outcome Updated webhook (alerts.outcome.updated) is available exclusively for Chargeflow Alerts customers. It notifies your system whenever the outcome of handling a pre-chargeback alert changes.

The outcome field describes the result of Chargeflow's attempt to process the alert — whether a linked transaction was found and if a refund was successfully applied. This webhook ensures your systems remain up to date as alerts move through their lifecycle.

Possible outcome values: duplicate, not_found, prevented, pending, chargebacked, previously_refunded, error when handling the alert.

The webhook payload includes the alert ID, the updated outcome value, and supporting metadata. If further details are required, you can call the Get Alert by ID endpoint to retrieve the complete alert record.

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