How Ethoca alerts work on Shopify, and the four ways they fail
An Ethoca alert tells you one thing. A cardholder has already called their issuing bank about a specific order, and Mastercard is giving you a short window to refund it before a chargeback gets filed. Ethoca's own guidance targets a refund within about 24 hours of the signal reaching you. Almost everything that makes this category underperform happens inside that window, or in the gap between what the alert promises and what a Shopify store actually receives.
What an Ethoca alert actually is
Ethoca is Mastercard's product. Mastercard acquired the company in 2019 and runs Ethoca Alerts as, in its own words, a tool that "connects merchants, acquirers and issuers together to share fraud and dispute data," built to deal with a dispute "within hours, instead of days or weeks" rather than through the normal chargeback timeline (ethoca.com/ethoca-alerts, checked July 22, 2026).
There are two kinds of signal, not one. Ethoca's FAQ describes alerts as notifications for "confirmed fraud and customer disputes" (ethoca.com/faq, checked July 22, 2026). A confirmed-fraud alert means the issuer already validated the cardholder's claim. A customer-dispute alert means the cardholder called in, but the bank has not made that determination yet. Treating the two the same is a mistake on its own. A confirmed-fraud alert on an order that has not shipped is an easy refund. A customer-dispute alert on a package that was delivered and signed for is worth a look before you credit it.
The FAQ is specific about the clock too. It tells merchants to "issue a refund as soon as possible or stop settlement (objective is within 24 hours)" (ethoca.com/faq, checked July 22, 2026). That is a target, not a guarantee, and it is shorter than the 72-hour window Verifi quotes for its own CDRN product, covered in RDR and CDRN solve different chargeback problems.
How the signal actually reaches a Shopify store
Ethoca does not sell a Shopify app. It sells network access to acquirers, gateways, and platforms, who resell or embed it for the merchants underneath them. A Shopify store almost never talks to Ethoca directly. The alert arrives wherever your provider decided to put it: an email, a portal login, a dashboard, or, in Redo's case, a queue inside the merchant's own account.
That routing detail matters more than it looks, because of what Shopify itself does with it: nothing. Shopify's own chargeback documentation describes a workflow that begins only once a chargeback is formally filed, with a due date that "varies from 7 to 21 days after the chargeback or inquiry is filed" (Shopify Help Center, chargebacks-in-admin, checked July 22, 2026). There is no mention of Ethoca, Verifi, or any pre-dispute alert anywhere in it, because an alert that resolves successfully never becomes a chargeback for Shopify to record.
So the refund you issue on an alert is not a "chargeback resolved" event inside Shopify. It is a plain order refund, executed through the admin or the API, indistinguishable in your own reporting from a refund you gave because a customer asked nicely. If you want to know later how many disputes your alert program actually kept off your books, you have to tag or log that yourself at the moment you act, because Shopify will not have done it for you.
This is the layer Redo's pre-filing dispute deflection is built to sit on. The Ethoca connection itself runs through Disputely's certified integration rather than anything Redo built from scratch. What we add is matching the signal to the actual Shopify order, executing the refund through the API, and writing a record that survives past the refund receipt, so a deflected dispute is still countable as one later.
Where an Ethoca alert stops doing its job
Four failure modes account for most of the gap between what a vendor deck promises and what a store actually experiences.
| Failure mode | What actually happens | What to check |
|---|---|---|
| Duplicate alert | The same dispute resurfaces after you already refunded it, or while a representment on it is already in flight | Match on order ID or the acquirer reference, not amount and date alone |
| Loses the race | The issuer files the chargeback before, or during, the alert's open window | Time from alert arrival to your recorded decision, not just the network's stated window |
| Low-value order | The refunded principal plus the alert fee costs more than the chargeback fee it avoided | A value floor below which you decline rather than reflexively refund |
| Coverage gap | The cardholder's issuer never enrolled with Ethoca, or enrolled for only one of the two alert types | Signals received divided by disputes received, measured on your own book |
Duplicate alerts are the one most likely to cost you twice. Ethoca signals flow to whoever is enrolled to receive them, and if the same underlying dispute is also visible to a Verifi product on the Visa side, one order can generate more than one signal. Refund the second one without checking and you have credited the customer twice. The fix is a de-duplication key on the order or the acquirer reference number, checked before the refund fires, not after. If you are already running a Visa product alongside Ethoca, the overlap and the fix for it are the same one covered in Ethoca and Verifi are complements more than competitors.
Losing the race happens when the issuer files before the alert does its job, or before anyone acts on it. An alert that arrives at 6pm on a Friday and gets read Monday morning is an alert you paid for and a chargeback you also received. This is a staffing and automation problem more than a network one. How chargeback alerts work and what they cannot catch covers the four preconditions that have to line up before any alert reaches you at all, of which timing is only one.
Low-value orders break the arithmetic rather than the mechanism. A $28 order with a $19 alert cost and a full refund is not a win against a $20 chargeback fee, it is a loss with extra steps. Any serious Ethoca program needs a floor, a dollar amount below which you decline and accept the small risk of a chargeback rather than refund automatically.
Coverage gaps are the one no vendor can fix for you, because participation is an issuer decision, not a network one. Ethoca describes its reach as relationships with issuing banks, and which banks are in, for which alert type, is not published anywhere you can look up before you run it. You find out by measuring your own disputes against what actually arrives.
The honest part
I want to be specific about what this category cannot do. Nobody, Ethoca included, can tell you your coverage rate before you run it, because it depends on which banks your customers hold cards with. A published prevention statistic is a statement about somebody else's portfolio.
Refunding on an alert also means refunding some customers who would have dropped the dispute or lost it at their bank anyway. You will never learn which ones, because you already refunded them, so the true cost of the program is a number you can estimate but never measure exactly.
And the ratio benefit, the reason most merchants buy this at all, is conditional. Visa's exclusion for pre-dispute resolution is contingent on the timing of the data extract, so a deflection close to month end can still land in that month's count. Plan for the benefit to hold across a quarter, not for any single alert.
Frequently asked questions
Does Shopify show Ethoca alerts anywhere in the admin?
No. Shopify's chargeback documentation covers only the post-filing process, evidence, and a 7 to 21 day due date. An alert that resolves successfully never becomes a chargeback, so it never appears in that workflow. The refund you issue on an alert shows up as an ordinary order refund.
What happens if an Ethoca alert arrives for an order I already refunded?
You decline it rather than refund again. This is the most common expensive mistake in running an alert program, and the fix is checking the order's refund status before acting on any alert, matched by order ID or acquirer reference rather than amount and date.
How fast do I actually need to respond to an Ethoca alert?
Ethoca's own guidance targets a refund within about 24 hours of the alert reaching you. That is a target, not a guarantee, and issuers can file the underlying chargeback before or during that window regardless of what you do.
Does declining an Ethoca alert count against me?
Declining and later receiving the chargeback puts you back on the normal representment path, with the usual fee and evidence deadline. It does not carry a separate penalty beyond that. It is a legitimate choice on orders where you would rather defend the chargeback than refund automatically.
The test I would run before trusting any Ethoca number, yours or a vendor's: pull every alert you received last quarter and sort it into four piles, the ones you refunded that later filed anyway, the ones you refunded that would have evaporated on their own, the ones you declined that turned into a won chargeback, and the ones you declined that you lost. That split, not the deflection rate on a slide, is what tells you whether the program is doing what you are paying for.