Library · Chargebacks · How to run this
Verifi fight share is not Ethoca fight share
VF fight % asks how often Verifi CDRN sends a case into representment instead of refund in one CDRN window. Fought rows go on top. All Verifi alerts sit under.
Pair: Alert-to-fight share on Chargebacks. Ethoca twin: alert-to-fight. Chargeblast twin: alert-to-fight.
What you type
Alerts fought — Verifi CDRN alerts sent to a fight / represent path in the window.
Alerts — Every Verifi alert in that same CDRN window.
VF fight % = fought ÷ alerts × 100. When VF fight % climbs, write a refund-default rule before you staff more representment. Never invent a VF fight chip.
What not to do
Skip inventing VF fight %. Skip loading Ethoca or Chargeblast fight exports into Verifi boxes. Skip counting CDRN timeouts or unmatched OI as fights. Skip blending Visa and Mastercard when Verifi alone owns the fight pile.
Related: Chargebacks, Ethoca alert-to-fight, Chargeblast alert-to-fight, CDRN-timeout.
Procedure
- Type alerts fought and alerts.
- Read VF fight %.
- Tighten the refund fork when VF fight % is material.
Failure modes
- Inventing VF fight %.
- Dumping an Ethoca fight-share or Chargeblast fight file into Verifi fields.
- Counting CDRN timeouts or OI misses as fights.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- VF fight %
- Alerts fought ÷ Alerts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Ethoca alert-to-fight share?
- Mastercard rail vs Visa CDRN. [Ethoca alert-to-fight](/manuals/ethoca-alert-to-fight-share) stays on Ethoca rows. Here both counts are Verifi only.
- Is this Verifi CDRN timeout share?
- Timeout is not fight. [CDRN-timeout share](/manuals/verifi-cdrn-timeout-share) is timed-out CDRN ÷ enrollments. This page is fought ÷ alerts.
- What VF fight % should I invent?
- None. Export fought alerts and total alerts from one Verifi CDRN window.