Chargeback Alerts Explained: Ethoca, CDRN and Visa RDR

What a chargeback alert is

A chargeback starts when a cardholder contacts their bank. Normally, the merchant hears about it only after the bank has opened a dispute and pulled the money back. By then the dispute exists, it counts against the merchant, and the only remaining option is to fight it.

A chargeback alert moves that moment earlier. When a participating issuer receives a fraud report or a dispute, it shares the case through an alert network before, or instead of, filing a chargeback. The merchant gets a short window to respond. The usual response is a refund. If the refund lands in time, the case closes and no chargeback follows.

That is the whole idea. Alerts do not win disputes. They let you choose to refund a case that you would probably lose anyway, on your terms, before it becomes a dispute on your record.

The three alert networks

Three programs do most of this work today. They overlap, but they are not the same.

Ethoca Alerts (Mastercard). Ethoca is owned by Mastercard. Its alerts cover two types of case: confirmed fraud, where the issuer has identified the transaction as fraudulent, and customer dispute, where the cardholder has started a dispute with the issuer. Alerts come from participating card issuers. Mastercard describes them as near real time and lists Visa, American Express and Discover alongside Mastercard as supported brands. The merchant stops fulfillment and refunds, then sends the outcome back through Ethoca so the issuer knows not to raise a chargeback.

Verifi CDRN (Visa). Verifi is Visa's company. Its Cardholder Dispute Resolution Network is described by Verifi as a manual, card brand agnostic solution. When a case comes in, the dispute is paused and posted in Verifi's portal for 72 hours. The merchant decides whether to accept it and issue a credit, or let the dispute proceed.

Visa Rapid Dispute Resolution (RDR). RDR works like CDRN but is automated. The merchant sets rules in advance, and disputes that match are resolved at the pre-dispute stage. Verifi says the resolution is sent to the acquirer, which returns the funds to the customer, and that RDR stops a chargeback from ever happening. Verifi describes the resolutions as complete and final.

	Ethoca Alerts	Verifi CDRN	Visa RDR
Operator	Mastercard (Ethoca)	Visa (Verifi)	Visa (Verifi)
Source of the case	Participating issuers	Participating issuers	Visa issuers, at pre-dispute
Decision	Merchant decides per alert	Merchant decides per case	Pre-set merchant rules decide
Window	Near real time; act fast	Case paused for 72 hours	Resolved automatically when rules match
Money movement	Merchant issues the refund	Merchant issues the credit	Credit routed through the acquirer

Coverage numbers for each network vary by source, and most published figures come from resellers rather than from Mastercard or Visa. Treat any single coverage percentage with caution. What is safe to say: participation depends on the issuer, so no network sees every card.

Timing windows

Every alert has a clock. Missing it means the issuer can go ahead and file the chargeback, and you end up paying for both the refund you did not issue and the dispute you could not avoid.

• CDRN: 72 hours, per Verifi. Treat it as wall-clock time, not business days.
• Ethoca: Mastercard describes alerts as near real time and frames them as a window to stop fulfillment before a chargeback is filed. Mastercard's public developer pages do not state one fixed response deadline, so the safe working rule is to decide within hours, not days.
• RDR: The decision is made by your rules at the moment the case arrives. The timing question moves to setup. Your rules need to be right before the case comes in.

Speed also matters for physical goods. A confirmed fraud alert on an order that has not shipped yet is the best case. You cancel, refund, and keep the product.

Refund versus chargeback economics

The case for alerts is arithmetic. Compare what happens to the same order on two paths.

If the order becomes a chargeback on Shopify Payments, the cardholder's bank takes the disputed amount from you right away, plus a chargeback fee. Shopify shows the fee for your country in its help center; in the United States it lists $15 USD. If you win, you get the amount back and Shopify returns the fee. If you lose, you are out the order value, the fee, the product if it shipped, and the time spent building evidence. In both cases, the dispute counts toward your chargeback rate and network monitoring programs.

If the same order is refunded through an alert, you lose the order value and whatever the alert costs. Alert pricing is set by the network or your provider and differs by product, so check your own contract rather than relying on published estimates. You keep the case out of your dispute count, and you skip the evidence work.

The decision rule that follows:

• Refund on alert when you would probably lose the dispute, when the product has not shipped, or when your rate is near a threshold.
• Consider letting a case proceed when you hold strong, specific evidence, the order value is high, and your rate has room to absorb one more dispute.

For a store near a monitoring threshold, or inside Shopify's Network Dispute Resolution Program, the count matters more than any single order. That tilts the rule hard toward refunding.

Why matching alerts to the exact order matters

An alert does not arrive with your order number on it. It carries card network data: things like a partial card number, amount, currency, transaction date, an acquirer reference, and the billing descriptor. Ethoca's own data model includes a "not found" outcome for alerts with no matching transaction. That outcome exists because matching is a real problem.

Getting it wrong is expensive in both directions.

• No match. The alert expires. The issuer files the chargeback. You paid for an alert and got nothing.
• Wrong match. You refund a different customer's order. The real disputed order still becomes a chargeback, and you have now paid twice.
• Duplicate refund. The customer already got a refund through support, and you refund again on the alert. Ethoca has a specific outcome for this, "resolved previously refunded", which tells the issuer the case is already settled without moving money twice.

Good matching uses several fields at once: amount and currency, date within a tolerance, card last four, and the acquirer reference where the platform exposes it. It also checks the order's refund history before acting. Partial refunds, split payments and currency conversion all make exact amount matching harder, so the logic needs to handle them.

What alerts cannot cover

Alerts are a card network tool. That sets their limits.

• Non-participating issuers. If the cardholder's bank does not take part in a network, no alert is sent. The dispute arrives as a normal chargeback.
• PayPal disputes and claims. A buyer who opens a dispute in PayPal's Resolution Center is using PayPal's process, not the card issuer's. PayPal describes chargebacks as a separate process run through the buyer's card issuer. A Resolution Center case is not a card network dispute, so card alerts do not see it.
• Cases filed before the alert can be acted on. If the issuer files straight away, or the alert window passes, you are back to representment.
• Partial outcomes. Some vendors report that RDR does not support partial refunds. Check your provider's terms if you often settle disputes for part of the order.

Plan on alerts reducing disputes, not eliminating them.

How alerts pair with representment

Alerts and representment answer different questions. Alerts ask: is this case worth refunding before it becomes a dispute? Representment asks: now that it is a dispute, can we prove the charge was valid? A sound setup uses both, with one decision process.

1. Connect the alert networks that cover your card mix: Ethoca, CDRN and, for Visa, RDR.
2. Set RDR rules carefully. Start narrow, for example low-value orders with reasons you rarely win, and widen once you see results.
3. Match every Ethoca and CDRN alert to an order the same day, and check for earlier refunds first.
4. Refund when the case is weak or the product has not shipped. Stop fulfillment if it has not left the warehouse.
5. Let strong cases through only on purpose, and have the evidence ready before the dispute arrives.
6. For disputes that arrive without an alert, build a response from delivery scans, customer messages, policies the customer accepted, and payment risk signals, and file before the deadline.
7. Review monthly: alerts received, matched, refunded, expired, and disputes won and lost by reason. Adjust rules from that.

Where Recoup fits

Recoup matches Ethoca, RDR and CDRN alerts to the exact order and refunds inside the window. The disputes that still get through are fought with evidence pulled from the store, carrier tracking, risk signals and customer conversations, filed automatically or after your approval.