# Set Up Dispute Alerts (Playbook)
Source: https://paymentsandrisk.com/docs/playbooks/setup-dispute-alerts

Last updated 4 November 2026.

TL;DR

-   **Week 1**: Enroll with Ethoca (Mastercard-owned) and Verifi CDRN (Visa-owned)
-   **Week 2**: Configure notifications and test refund rules against your costs and evidence
-   **Go live**: Confirm each service's response deadline, set an earlier internal target and track outcomes once late chargebacks have had time to arrive
-   **What to expect**: coverage varies. Compare chargebacks, refunds and alert fees before and after on the same enrolled segment
-   **The math**: in the worked example, a $30 alert avoids a $15 dispute fee. Fees alone lose money. Compare your quote, refunds and ratio impact before buying

Alerts can let you refund an eligible transaction before it turns into a chargeback. That gives the sale back, so compare it with what defending or accepting that case would cost. Get a quote from your provider or a reseller, then compare the fees, extra refunds and ratio impact on your covered disputes. This playbook gives you an enrollment and testing plan for Ethoca, Verifi CDRN and RDR. Confirm the actual launch date with your provider.

If you're reading this because your ratio is climbing, alerts can help but they won't fix the cause. Run this alongside [reduce chargebacks fast](https://paymentsandrisk.com/docs/playbooks/reduce-chargebacks-fast/), not instead of it.

## Workflow Overview

```mermaid
flowchart LR
    A[<b>WEEK 1</b><br/>Enrollment] --> B[<b>WEEK 2</b><br/>Integration] --> C[<b>GO LIVE</b><br/>Launch] --> D[<b>ONGOING</b><br/>Operate]

    style A fill:#3d5a80,color:#fff
    style B fill:#5e4b8b,color:#fff
    style C fill:#9a5b00,color:#fff
    style D fill:#1f6f4a,color:#fff
```

| Phase | Key Tasks |
| --- | --- |
| **Enrollment** | Choose approach (direct, processor, aggregator), enroll Ethoca + Verifi |
| **Integration** | Configure notifications (API or email), define auto-refund rules, test E2E |
| **Launch** | Enable alerts, monitor errors, track ROI |
| **Operate** | Daily pending alerts check, weekly metrics review, monthly ROI analysis |

**What you need on hand:** legal entity and bank docs, your [descriptors](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/) exactly as they print on statements, your processor MIDs, the ability to refund by API or by hand, your current ratio from [chargeback metrics](https://paymentsandrisk.com/docs/chargebacks/metrics/), and a written quote covering setup, minimums and per-event charges.

## Trigger Criteria

Run this playbook if:

-   Your chargeback ratio is climbing toward your processor's written limit or the [published program lines](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/)
-   You want to head off disputes rather than fight them
-   You're in a monitoring program, or close enough to worry
-   Customers are disputing charges they should recognize

* * *

## Understanding Alert Services

### The Three Services

| Service | Owner | How It Works | Check for Your Account |
| --- | --- | --- | --- |
| **Ethoca** | Mastercard-owned | Alerts on fraud and customer disputes. [Mastercard describes it as brand-agnostic](https://www.mastercard.com/us/en/business/cybersecurity-fraud-prevention/dispute-management/ethoca-alerts.html) | Enrolled issuers, brands and countries, plus actual arrival and response terms |
| **Verifi CDRN** | Visa-owned | Alert network with issuer participation. [Verifi advertises Visa and non-Visa reach](https://www.verifi.com/solutions-sellers/resolve-disputes.html) | The same |
| **Verifi RDR** | Visa-owned | Resolves qualifying Visa disputes on rules you set | Which of your Visa cases qualify |

Both networks own one of these now, so this isn't a third-party bolt-on any more. Who owns a service doesn't tell you which one suits you. Coverage still depends on which issuers participate and which descriptors and MIDs you enroll. Ask your provider which of your past disputes it could have covered.

### How Alerts Can Prevent Chargebacks

```text
Traditional path:
Customer disputes → Issuer files chargeback → You take the chargeback

With an eligible alert, resolved in time:
Customer disputes → Alert sent → You check credits and refund → A chargeback can be avoided
```

A case can already be charged back or refunded when the alert lands, so check first. Record what happens afterward, because a refund doesn't guarantee there's no chargeback, and it doesn't always remove a fraud report.

### Expected Results

| Metric | What to Check |
| --- | --- |
| Chargebacks prevented | Verifi claims CDRN can stop **up to 40%** of chargebacks. That's its product claim, with no sample or measurement period given on the page. VENDOR [Verifi FAQ](https://www.verifi.com/chargebacks-disputes-faq/what-are-credit-card-chargebacks.html), accessed 2026-10-22. Compare your own before-and-after rate on the same enrolled segment |
| Alert match rate | Ask for coverage of your issuer mix, descriptors and MIDs. Track unique matched transactions; don't assume a general rate |
| Response window | Confirm the service and reseller deadline. Verifi describes 72 hours to start a CDRN credit; Kount instructs its Ethoca users to respond within 24 hours. [CDRN](https://www.verifi.com/resolve-disputes.html), [Kount Ethoca guidance](https://support.kount.com/hc/en-us/articles/45534281508500-Manage-CDRN-Alerts-and-Ethoca-Alerts-in-Chargeback-Management), checked 22 October 2026 |
| ROI breakeven | Compare alert fees and extra refunds with avoided dispute costs on the same segment; there's no fixed payback period |

* * *

## Week 1: Enrollment

### Step 1: Choose Your Approach

| Option | What to Ask |
| --- | --- |
| **Direct enrollment** | How long activation takes, what you'd integrate, and the total price |
| **Through processor** | Which services it offers, how long activation takes, and its price and refund terms |
| **Through aggregator** | Which services one integration really covers, plus activation and price |

**The call:** compare them on activation, integration, coverage and total price for your account. If your processor bundles alerts and those terms hold up, that's a fair place to start.

### Step 2: Ethoca Enrollment

1.  Apply at Ethoca (or through processor/aggregator)
2.  Provide business documentation
3.  Submit your descriptor list (exactly as it appears on statements)
4.  Ask how alerts reach you on this route, and choose from what it offers
5.  Get the expected activation date in writing and verify coverage before relying on it

**Checkpoint:** Ethoca account active, descriptors registered.

### Step 3: Verifi CDRN Enrollment

1.  Apply at Verifi (or through processor/aggregator)
2.  Provide MID list and descriptors
3.  Ask which notification methods your route offers, and choose one
4.  Configure response workflow
5.  Get the expected activation date in writing and verify coverage before relying on it

**Checkpoint:** Verifi CDRN account active, connected to your MIDs.

### Step 4: Verifi RDR Setup (Optional)

RDR resolves the dispute for you, without anyone looking at it. That's the appeal and that's the risk, so start it small.

1.  Enroll in RDR through Verifi
2.  Test candidate resolution rules against your own losses and evidence. Set the dollar ceiling from your margin and dispute costs; digital goods or missing tracking alone don't establish that refunding is cheaper
3.  Test on one segment before you turn it on everywhere

An RDR resolution credits through your acquirer, so reconcile it there. It isn't the refund you issue after an Ethoca or CDRN alert. Verifi's Decision API also lets you host the decision logic yourself ([Verifi](https://www.verifi.com/solutions-sellers/resolve-disputes.html)).

**Checkpoint:** RDR rules configured and active.

* * *

## Week 2: Integration and Testing

### Step 1: Configure Notifications

Use your own provider's published workflow. These are general steps. Kount's [API guide](https://developer.kount.com/hc/en-us/articles/4411045463956-Receive-alerts-in-Chargeback-Management) and [alert guide](https://support.kount.com/hc/en-us/articles/45534281508500-Manage-CDRN-Alerts-and-Ethoca-Alerts-in-Chargeback-Management), read 3 November 2026, are one example, not what every provider offers.

#### API Integration (Recommended for Volume)

At any real volume you want a webhook, not an inbox:

1.  Create an endpoint on your server to receive alert notifications
2.  When an alert arrives, look up the original transaction
3.  Apply your auto-refund rules (see next section)
4.  Respond to the alert with your decision (refunded, declined, and so on)

**What to tell your developer:** "Check each alert against the order, existing credits and our approved refund rules. Record the service deadline and escalate early enough for a person to act before it expires."

#### Email/Portal (Lower Volume)

1.  Configure alert emails to operations inbox
2.  Set up monitoring for alert emails
3.  Set an internal response target before each service deadline, allowing for weekends and escalation
4.  Create manual refund workflow

### Step 2: Define Auto-Refund Rules

These are suggested rules to test, not guaranteed payback or dispute outcomes. Check refund status before creating a credit; don't separately refund an open chargeback or an RDR-resolved case.

| Condition | Recommended Action |
| --- | --- |
| Transaction under $50 | Test a refund rule against your actual alert fee, dispute cost and margin |
| Digital goods | Check access evidence and dispute reason before deciding |
| No tracking available | Check other evidence; lack of tracking doesn't decide every dispute |
| Subscription (canceled) | Stop future billing as required. Decide this charge from when the cancellation took effect, the dispute reason, credits already given and any refund right |
| Known friendly fraud pattern | Review before refund |
| High-value physical goods | Review, may have proof |

### Step 3: Test the Flow

1.  Process a test transaction
2.  Simulate an alert (if the provider has a test mode)
3.  Verify the notification arrives
4.  Process the refund
5.  Confirm the alert response went back
6.  Check that the transaction matched, the right credit and acknowledgment went through, and a duplicate is handled

A test can't show what an issuer does later, so watch real outcomes separately once they're old enough to read.

**Checkpoint:** End-to-end flow tested and working.

* * *

## Go Live Checklist

-   [ ]  Ethoca active and receiving alerts
-   [ ]  Verifi CDRN active and receiving alerts
-   [ ]  Notification workflow configured
-   [ ]  Auto-refund rules defined
-   [ ]  Manual review queue set up
-   [ ]  Internal response target and cover agreed for each service deadline
-   [ ]  Metrics tracking enabled

* * *

## Ongoing Operations

### Daily Tasks

1.  Check for pending alerts
2.  Work the manual review queue
3.  Confirm auto-refunds are actually completing

### Weekly Metrics

| Metric | Track |
| --- | --- |
| Alerts received | Volume trend |
| Match rate | Unique alerted transactions matched to an original order / unique alerted transactions received in the same period. De-duplicate Ethoca and CDRN; log unmatched cases separately |
| Response time | Average hours to respond |
| Alert-to-refund rate | Timely refunds / unique alerts received in the same period. Use the [shared definition](https://paymentsandrisk.com/docs/chargebacks/prevention/chargeback-alert-pricing/#analyst-layer-metrics-to-track) and separate cases that did not need a refund |
| Prevention rate | For mature, unique matched transactions, track timely resolutions and later chargebacks separately. A resolved alert alone doesn't prove a chargeback was prevented |

### Monthly Review

1.  Work out your actual ROI (chargebacks prevented against alert fees paid)
2.  Estimate margin forgone on defensible cases you refunded. Label the estimate; you can't observe what every refunded case would have become. Fraud metric definitions are in [Fraud Metrics](https://paymentsandrisk.com/docs/fraud/metrics/)
3.  Tune the auto-refund thresholds
4.  Check coverage. A new descriptor, account or route may need enrolling, so confirm how your provider matches them

* * *

## Success Criteria

You're done when:

-   [ ]  Both Ethoca and Verifi CDRN active
-   [ ]  Alerts being received and processed
-   [ ]  Alerts handled before their service deadlines
-   [ ]  Mature dispute outcomes compared on the same covered segment
-   [ ]  Avoided costs justify alert fees, extra refunds and operating work

* * *

## Scale Callout

| Volume | Approach |
| --- | --- |
| **Under $100k/mo** | Check whether a named person can meet each deadline using the portal or email |
| **$100k-$1M/mo** | Price API integration against actual queue work and missed deadlines |
| **Over $1M/mo** | Automate only tested rules; retain an owner and review exceptions |

These are planning bands. Alert counts, coverage and staffing decide the workflow, rather than sales volume alone.

* * *

## Where This Breaks

-   **Identifiers not registered.** Alerts may not match, depending on how your provider matches merchants and transactions. Confirm its identifiers, and audit them quarterly.
-   **Response too slow.** Missing the particular service deadline can leave you with both an alert fee and a chargeback. Confirm the clock for each service; don't give an Ethoca alert CDRN's response window.
-   **Auto-refunding everything.** Refund rules can be learned and abused. Keep thresholds and keep a review queue.
-   **Nobody tracking ROI.** It's easy to quietly overpay for years. Compare alert fees and extra refunds with the whole cost of the chargebacks they replace, including what the ratio headroom is worth to you. If alerts still cost more, stop.
-   **New MIDs not enrolled.** A new processor or MID may need enrolling. Ask your provider which identifiers and routes it matches ([Kount's merchant and transaction fields](https://developer.kount.com/hc/en-us/articles/4411045463956-Receive-alerts-in-Chargeback-Management)), and make that part of the launch checklist.

* * *

## Cost Analysis

### Typical Costs

| Item | What to Check |
| --- | --- |
| Ethoca per alert | Your reseller quote, including duplicate and unmatched alerts |
| Verifi CDRN per alert | Your reseller quote and any bundle terms |
| RDR per resolution | Your acquirer or reseller's rate and which cases are billable |
| Chargeback fee | Your processor agreement; [provider-fee table](https://paymentsandrisk.com/docs/payments/total-cost-model/#step-2-chargeback-costs-often-underestimated) |
| Chargeback ratio impact | Your processor's metric and the applicable program conditions |

### ROI Calculation

**Worked example, not a forecast.** Assume 10,000 transactions a month and 100 chargebacks, so a 1.00% simple chargeback-to-transaction ratio. Also assume alerts match 35 transactions that would otherwise become chargebacks, all 35 are resolved in time, each alert costs $30 and each avoided chargeback fee is $15:

```text
Alerts matched (assumed 35 of 100 baseline chargebacks): 35
Alert cost at $30 each:           $1,050

Chargebacks prevented:            35
Chargeback fees avoided at $15:   $525
Ratio: 100 -> 65 chargebacks,     1.00% -> 0.65%

Net on fees alone:                -$525
```

That model assumes a $15 dispute fee and a $30 alert. On fees alone, $525 avoided - $1,050 paid = **\-$525**. At a $30 dispute fee, 35 x $30 avoided - 35 x $30 paid = **$0**. Replace both rates with your quote and processor terms. Compare any reseller's claimed dispute fee with the [provider-fee table](https://paymentsandrisk.com/docs/payments/total-cost-model/#step-2-chargeback-costs-often-underestimated); don't assume a $60 or $100 fee applies to you.

What you're buying is fewer disputes reaching your ratio. In this example, it falls from 1.00% to 0.65%. That alone doesn't tell you whether you're in a program. Check your processor's limit and the [published program conditions](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/), including counts and exclusions, before deciding what the reduction is worth.

Two things the model leaves out. First, not every alert would have become a lost chargeback. Estimate extra refunds and forgone recoveries separately, and label it an estimate. Second, a refund need not remove a fraud report already counted by your acquirer. Check the [network counting rules](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/) and put both effects into your own comparison.

* * *

## Next Steps

Once alerts are running:

1.  **Tune the auto-refund rules.** Your real alert mix won't look like the table above
2.  **Check ROI monthly.** Count alert fees and extra refunds against the dispute costs you avoid and what the ratio headroom is worth to you
3.  **Recheck coverage.** After a product launch or billing change, confirm your identifiers and route are still covered
4.  **Consider RDR.** If your Visa volume is heavy, automated resolution is worth the look
5.  **Fix the root cause.** Alert data can show why people dispute. That's the part that actually lowers the ratio

* * *

## Related

-   [Playbooks](https://paymentsandrisk.com/docs/playbooks/): The playbooks hub
-   [Chargeback Alerts Deep Dive](https://paymentsandrisk.com/docs/chargebacks/prevention/alerts/): Detailed alert coverage
-   [Reduce Chargebacks Fast](https://paymentsandrisk.com/docs/playbooks/reduce-chargebacks-fast/): Crisis playbook
-   [Network Programs](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/): VAMP and ECM thresholds
-   [Chargebacks Overview](https://paymentsandrisk.com/docs/chargebacks/): Dispute fundamentals
-   [Chargeback Prevention](https://paymentsandrisk.com/docs/chargebacks/prevention/): Prevention hierarchy
-   [Chargeback Lifecycle](https://paymentsandrisk.com/docs/chargebacks/lifecycle/): Where alerts fit
-   [Chargeback Metrics](https://paymentsandrisk.com/docs/chargebacks/metrics/): Ratio tracking
-   [Chargeback Vendors](https://paymentsandrisk.com/docs/chargebacks/vendors/): Alert providers
-   [Chargeback Ratio Crisis](https://paymentsandrisk.com/docs/chargebacks/zero-point-nine-panic/): Crisis response
-   [Descriptors and Communication](https://paymentsandrisk.com/docs/chargebacks/prevention/descriptors-and-comms/): Billing clarity
-   [Friendly Fraud](https://paymentsandrisk.com/docs/fraud/types/friendly-fraud/): First-party abuse
-   [Alerts Configuration](https://paymentsandrisk.com/docs/operations/alerts-configuration/): Operations alert setup
