Skip to main content

Set Up Dispute Alerts (Playbook)

TL;DR
  • Week 1: Enroll with Ethoca (Mastercard-owned) and Verifi CDRN (Visa-owned)
  • Week 2: Configure notifications by API or email, then write your auto-refund rules (under $50, digital goods, no tracking)
  • Go live: Respond inside 24 hours, track match rate and prevention rate
  • What to expect: 20-40% fewer chargebacks, 30-50% of disputes matched by an alert
  • The math: $20-40 per alert against a $15 chargeback fee at most processors. On fees alone that loses money. You're buying the ratio, not the fee saving

Alerts let you refund a transaction before it turns into a chargeback. You still lose the sale either way, so the thing you're actually buying is the fee and the ratio, and for most merchants that's worth $20-40 a head. This playbook gets you connected to Ethoca, Verifi CDRN and RDR in one to two weeks, and most of that time is just waiting on approvals.

If you're reading this because your ratio is climbing, alerts will help but they won't fix the cause. Run this alongside reduce chargebacks fast, not instead of it.

Workflow Overview​

PhaseKey Tasks
EnrollmentChoose approach (direct, processor, aggregator), enroll Ethoca + Verifi
IntegrationConfigure notifications (API or email), define auto-refund rules, test E2E
LaunchEnable alerts, monitor errors, track ROI
OperateDaily pending alerts check, weekly metrics review, monthly ROI analysis

What you need on hand: legal entity and bank docs, your descriptors exactly as they print on statements, your processor MIDs, the ability to refund by API or by hand, your current ratio from chargeback metrics, and a budget of $20-40 per alert.

Trigger Criteria​

Run this playbook if:

  • Your chargeback ratio is above 0.5% and still climbing
  • 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​

ServiceNetworkHow It WorksBest For
EthocaMastercard-ownedAlert when cardholder initiates disputeFraud disputes, faster notification
Verifi CDRNVisa-ownedAlert network with issuer participationVisa-heavy merchants
Verifi RDRVisaAuto-resolve disputes based on rulesHigh-volume, automated resolution

Both networks own one of these now, so this isn't a third-party bolt-on any more. Coverage still depends on which issuers participate, which is why the match rate lands around a third rather than everything.

How Alerts Prevent Chargebacks​

Traditional path:
Customer disputes → Issuer files chargeback → You lose

With alerts:
Customer disputes → Alert sent → You refund → No chargeback filed

Expected Results​

MetricTypical Impact
Chargebacks prevented20-40% reduction
Alert match rate30-50% of disputes
Response window24-72 hours
ROI breakeven1-2 months typically

Week 1: Enrollment​

Step 1: Choose Your Approach​

OptionProsCons
Direct enrollmentLower per-alert costMore integration work
Through processorFaster setupHigher per-alert cost
Through aggregatorSingle integration for allHighest per-alert cost

The call: if your processor bundles alerts, start there. You'll pay a bit more per alert and you'll be live weeks earlier, and being live is what saves you money. Move to direct enrollment later if the volume justifies it.

Step 2: Ethoca Enrollment​

  1. Apply at Ethoca (or through processor/aggregator)
  2. Provide business documentation
  3. Submit descriptor list (exactly as it appears on statements)
  4. Configure notification endpoint or email
  5. Wait for approval (3-7 business days)

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. Choose notification method (API, email, portal)
  4. Configure response workflow
  5. Wait for approval (3-7 business days)

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. Define resolution rules:
    • Always refund under $X
    • Always refund if digital goods
    • Always refund if no tracking
  3. Set liability acceptance threshold
  4. Test on one segment before you turn it on everywhere

Checkpoint: RDR rules configured and active.

Week 2: Integration and Testing​

Step 1: Configure Notifications​

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: "Set up a webhook endpoint for Ethoca and Verifi. When an alert comes in, check it against our auto-refund rules and process it. We have to respond inside 24 hours."

Email/Portal (Lower Volume)​

  1. Configure alert emails to operations inbox
  2. Set up monitoring for alert emails
  3. Define SLA for response (under 24 hours)
  4. Create manual refund workflow

Step 2: Define Auto-Refund Rules​

ConditionRecommended Action
Transaction under $50Auto-refund (ROI positive)
Digital goodsAuto-refund (hard to prove delivery)
No tracking availableAuto-refund (can't win dispute anyway)
Subscription (canceled)Auto-refund
Known friendly fraud patternReview before refund
High-value physical goodsReview, 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. Confirm no chargeback follows

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
  • Response SLA defined (under 24 hours)
  • 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​

MetricTrack
Alerts receivedVolume trend
Match rateAlerts / Total disputes
Response timeAverage hours to respond
Refund rate% of alerts refunded
Prevention rateChargebacks avoided

Monthly Review​

  1. Work out your actual ROI (chargebacks prevented against alert fees paid)
  2. Check your false positive rate, meaning good sales you refunded for nothing
  3. Tune the auto-refund thresholds
  4. Check descriptor coverage. New product, new billing name, new gap

Success Criteria​

You're done when:

  • Both Ethoca and Verifi CDRN active
  • Alerts being received and processed
  • Response time under 24 hours
  • Chargeback ratio trending down
  • ROI positive (cost vs prevented chargebacks)

Scale Callout​

VolumeApproach
Under $100k/moManual email alerts are usually enough; a processor bundle gets you live fastest
$100k-$1M/moAPI integration; written auto-refund rules; check ROI weekly
Over $1M/moFull automation; RDR for volume resolution; someone who owns alert ops

Where This Breaks​

  • Descriptors not registered. The alerts won't match anything and you'll pay for a service that does nothing. Audit descriptors quarterly.
  • Response too slow. Past 72 hours the chargeback gets filed anyway and you've paid for the alert on top. Set a tight SLA and mean it.
  • Auto-refunding everything. Fraudsters work out what you're doing faster than you'd think. Keep thresholds and keep a review queue.
  • Nobody tracking ROI. It's easy to quietly overpay for years. If the alert costs more than the chargeback would have, stop.
  • New MIDs not enrolled. Add a processor or a MID and it's outside coverage until somebody enrolls it. Make that part of the launch checklist.

Cost Analysis​

Typical Costs​

ItemCost Range
Ethoca per alert$20-40
Verifi CDRN per alert$20-40
RDR per resolution$15-25
Chargeback fee$0-30, typically $15
Chargeback ratio damageNot billed to you directly, but it's what pushes you into a monitoring program

ROI Calculation​

Assume 10,000 transactions a month and 100 chargebacks, so a 1.00% ratio:

Alerts matched (35% of disputes): 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 uses $15, the fee most US processors publish. On fees alone alerts lose money, and it isn't close. $30 is the highest published US figure, and even there you only break even. Nobody publishes $60. If a reseller shows you ROI built on a $60 or $100 chargeback fee, ask which processor charges it, because none of the ones verified here do.

What you're buying is the ratio. Going from 1.00% to 0.65% is the difference between sitting in a monitoring program and not, and that's worth more than $525 a month. Buy alerts for the ratio. Treat the fee savings as change.

Two things the model above leaves out, and you should put them back in with your own numbers. First, you refund the sale on every alert you accept, including the ones that would never have become chargebacks. That's your false positive cost and it's real money. Second, ask your acquirer whether alert-resolved transactions still count toward your fraud-based program ratios, because a dispute the cardholder already reported as fraud may have been counted before your refund ever landed. See network programs for how the counting works.

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. Alert cost has to stay under the chargeback cost you're avoiding
  3. Add new descriptors. Every product launch and billing change opens a coverage gap
  4. Consider RDR. If your Visa volume is heavy, automated resolution is worth the look
  5. Fix the root cause. Alert data tells you why people dispute. That's the part that actually lowers the ratio
Last updated on