What Is a Chargeback Alert and What Can You Do?
A chargeback alert is an early warning that a sale may turn into a formal dispute. Here is how alerts travel, what the two types mean, and what a merchant can do in the window before a chargeback is filed.
What a chargeback alert is
A chargeback alert is an early warning that a sale may turn into a formal dispute. It arrives before the chargeback itself. That gap is the whole point. A merchant who learns about a problem early can review the sale, stop fulfillment, or refund it before a formal dispute is filed.
Ethoca Alerts for Merchants is a real-time alert service that warns merchants of possible fraud and dispute transactions before they become chargebacks. Ethoca Alerts connects issuers and merchants so they can share fraud and dispute data.
So the alert is not the chargeback. It is a heads-up that one may be coming. That difference is what makes the tool useful.
How an alert travels: issuer to network to merchant
The path is short. The cardholder reports the charge to the issuer. The issuer may send an alert through the Ethoca network. The merchant gets it in real time.
Three parties touch the alert on its way. The cardholder reports the problem. The issuer decides to send word out. The network carries it to the merchant. No one waits for the formal dispute process to finish first.
The two alert types
Alerts come in two kinds. Each one means something different, and each one calls for a different response.
A fraud alert means a cardholder has reported a charge as possibly unauthorized or fraudulent. Ethoca's documentation says a CONFIRMEDFRAUD alert means a card issuer has identified the transaction as fraudulent.
A dispute alert means a cardholder contacted their issuer about a charge that might become a chargeback. Ethoca's documentation says a CUSTOMERDISPUTE alert means a customer has initiated a chargeback or dispute with their card issuer.
Read the difference carefully. One is about fraud. The other is about a customer unhappy with a sale they may well have made themselves.
What a merchant can do when an alert arrives
An alert does not mean a chargeback will happen, so the merchant reviews the sale and decides how to respond.
What you should do next turns on which kind of alert you got.
For a customer dispute alert, a merchant can check with the customer, share a receipt or tracking, or refund.
For a confirmed fraud alert, a merchant can cancel or refund the sale and look for other fraud.
Ethoca's page says merchants receiving real-time fraud alerts can stop order fulfillment and issue refunds. That matters most when the goods have not shipped yet.
Responding back: acknowledgement and outcome
The alert is not a one-way message. The merchant talks back.
First comes the acknowledgement. The merchant confirms it received an alert, and that confirmation is passed on to the issuer.
Then comes the outcome. An outcome is the result of the merchant's review, sent back to Ethoca. An outcome such as refunded lets the card issuer know not to raise a chargeback.
The issuer uses the merchant's outcome to decide whether a chargeback is still needed.
One rule matters here. Ethoca's documentation says an outcome cannot be changed after the fact, and the issuer gets the first final outcome the merchant sends. You only get one answer. So the first answer you send back should be the right one.
Ethoca's documentation also says duplicate alerts can occur during webhook retransmission and should be deduplicated based on alertId. If your system sees the same alert twice, treat it as one.
Push vs. pull delivery
Alerts can reach a merchant two ways. Ethoca can push alerts to the merchant, or the merchant can pull them from Ethoca on a schedule.
Push means the alert lands on your system the moment it exists. Pull means your system checks in on a clock.
Ethoca's brochure says merchants using Ethoca Alerts through API can automate much of the process with virtually no manual effort.
How alerts differ from RDR
Alerts are one family of pre-dispute tools. Visa has another.
Chargeblast's docs say RDR is a dispute resolution product offered by Visa where the acquirer is responsible for refunding the transactions. Chargeblast's docs say no action is required by the merchant for RDR.
So the two work differently. An alert asks the merchant to review and respond. RDR resolves the transaction without the merchant lifting a hand. One is a decision tool. The other is an automatic refund path on the Visa side.
To go deeper on Ethoca Alerts, see Ethoca chargeback. For the Visa-side tool, read about RDR chargeback.
What an alert service is not
Ethoca's documentation says the service sends alerts and takes responses, and it does not manage chargebacks.
That line is worth sitting with. An alert service tells you a problem may be coming. It does not manage your disputes for you.
Think of it as one part of a larger system, not the system itself.
Where alerts fit in a broader prevention strategy
Ethoca Alerts says using its alerts can help reduce chargeback costs, prevent unnecessary operational work, and improve customer outcomes.
Ethoca Alerts says it can be integrated with existing fraud, risk, fulfillment, customer service, and dispute-management workflows.
So an alert service works after the sale but before a chargeback.
For the wider picture, start with merchant chargeback prevention and chargeback prevention.
Use it well. Review the sale, pick the right response, and send the outcome back. The chargeback that never gets filed is the one that costs the least.