Ethoca Chargeback Alerts, Explained
An Ethoca chargeback alert is a heads-up before a chargeback is filed. Here is how the alert reaches you, what you send back, and what it does not do.
A customer calls their bank about a charge. The bank has not filed anything yet. But somewhere in that call is a warning you could use. Ethoca Alerts is built to catch that warning and get it to you first. This page explains what an Ethoca chargeback alert is, in Ethoca's own words, and what happens after it lands on your desk.
What an Ethoca chargeback alert is
Ethoca Alerts for Merchants is a real-time alert service. Ethoca says it warns merchants of possible fraud and dispute transactions before they become chargebacks.
So the alert is not the chargeback itself. It is a message that one might be coming. Ethoca's documentation says its service is an alert and response platform, not a chargeback management system. That line matters, and this page comes back to it at the end.
The service runs on a shared pipe between banks and shops. Ethoca Alerts connects issuers and merchants so they can share fraud and dispute data. Ethoca was acquired by Mastercard, but its brochure says its solutions are card brand agnostic, so all issuers can participate regardless of card brand.
How an alert happens
The trip is short. A cardholder reports a charge to their issuer. The issuer may send an alert through the Ethoca network. Issuers share confirmed fraud and customer dispute data, which is turned into alerts sent to merchants.
So the alert can reach you before the complaint becomes a chargeback. That gap is the whole point of the service, and it is what makes an alert different from the dispute itself.
The two alert types
Every alert is one of two kinds, and the kind decides what you can do with it.
The first is a customer dispute alert. Ethoca's documentation says a CUSTOMERDISPUTE alert means a customer has initiated a chargeback or dispute with their card issuer. In plainer words, a dispute alert means a cardholder contacted their issuer about a charge that might become a chargeback.
The second is a confirmed fraud alert. Ethoca's documentation says a CONFIRMEDFRAUD alert means a card issuer has identified the transaction as fraudulent. Here the cardholder has reported a charge as possibly unauthorized or fraudulent, and the issuer has agreed.
The two kinds call for different responses, and the outcome rules later in this page split along the same line.
How alerts reach you
Ethoca can push alerts to the merchant, or the merchant can pull them from Ethoca on a schedule. You can also use both. Ethoca's documentation says Push and Pull are not mutually exclusive and both end with Outcome submission.
Push means Ethoca comes to you. Ethoca's documentation says the Alerts Push API is a webhook that lets Direct Merchants and Partners receive alerts on the Ethoca network. Your system gets a call the moment an alert exists.
Pull means you go get them. Ethoca's documentation says the Alerts Pull endpoint lets merchant members pull alerts and send an acknowledgement that they received them. Your system asks on a schedule, and Ethoca hands over whatever is new.
The acknowledgement step
Before anything else, you confirm you got the alert. The merchant confirms it received an alert, and that confirmation is passed on to the issuer.
This step is small but it is not decoration. The issuer learns that you know about the complaint.
The outcome step
Now you review the sale and report back. An outcome is the result of the merchant's review, sent back to Ethoca.
The issuer uses the merchant's outcome to decide whether a chargeback is still needed. An outcome such as refunded lets the card issuer know not to raise a chargeback. So the outcome is the half of the loop that can stop the chargeback from ever being filed.
One warning before you submit. Ethoca's documentation says outcomes are immutable and the first final outcome you submit is what the issuer receives. There is no second try. Check your work before you send it.
Outcome codes and the matching rules
Ethoca's documentation lists RESOLVED, RESOLVED_PREVIOUSLY_REFUNDED, UNRESOLVED_DISPUTE, NOT_FOUND and OTHER as customer dispute outcome codes.
Not every code fits every alert. Ethoca's documentation says to check the alert's alertType field and match the outcome to the alert type. Two rules follow from that.
Ethoca Alerts documentation says CUSTOMERDISPUTE alerts cannot use STOPPED or PARTIALLY_STOPPED outcome codes. Ethoca Alerts documentation says CONFIRMEDFRAUD alerts cannot use RESOLVED or RESOLVED_PREVIOUSLY_REFUNDED outcome codes.
So a dispute alert and a fraud alert each have their own set of allowed answers.
What you can actually do
An alert does not mean a chargeback will happen, so the merchant reviews the sale and decides how to respond. Ethoca Alerts says merchants who receive an alert can review the transaction and determine the most appropriate response.
After an alert, a merchant can review the sale, stop fulfillment, or issue a refund before a formal dispute. The best move depends on the alert type.
For a customer dispute alert, a merchant can check with the customer, share a receipt or tracking, or refund. Maybe the customer forgot the purchase. Maybe the box is still on its way.
For a confirmed fraud alert, a merchant can cancel or refund the sale and look for other fraud. If one stolen card touched your shop, it is worth checking whether it touched you twice.
Ethoca Alerts says it can be integrated with existing fraud, risk, fulfillment, customer service, and dispute-management workflows. So the alert can land inside the tools your team already uses, rather than in a separate inbox nobody watches.
What Ethoca Alerts is not
Ethoca's documentation is plain on this. Its service is an alert and response platform, not a chargeback management system. It tells you a complaint exists and carries your answer back. It does not run your whole dispute operation.
That is not a knock on it. Ethoca Alerts can help merchants who take payments where the card is not present. Ethoca Alerts says using its alerts can help reduce chargeback costs, prevent unnecessary operational work, and improve customer outcomes.
But an alert service is one piece, not the whole plan. A broader approach needs merchant chargeback prevention built around how you sell, not just how you answer. To see how this kind of early warning stacks up against other programs, read about the chargeback alert model in general. For work that stops disputes before a bank hears about them, see how to prevent chargeback filings and build wider chargeback prevention habits.
The loop, in short, is this. A cardholder complains. The issuer sends an alert through Ethoca. You acknowledge it, review the sale, and submit an outcome. The issuer reads that outcome and decides whether a chargeback is still needed. Answer well and fast, and the chargeback may never be filed at all.