Skip to article
ecomservices.io
Chargebacks · How to run this
MatchingNot on this page yetPricingCalculatorIntakeCalculatorReason codesCalculatorRepresentmentCalculatorThresholdsCalculatorAllocationCalculatorOptimisationCalculatorPrevention stackCalculatorProviders

Library · Chargebacks · How to run this

Ethoca intake wait is not Midigator fight stall

How to run thisChargebacks3 steps
CalculatorEthoca alert-to-fight lag · Calculator lives in the articleOpen

Multiply open cases by AOV $ on an Ethoca Clarity export. That product is ET fight-clock at-risk $. Hold lag hours next to it so the wait stays visible.

Pair: Alert-to-fight lag on Chargebacks. Midigator twin: Midigator lag. Forter twin: Forter lag.

Inputs

Lag hours — Mean hours from Ethoca Clarity intake to fight / refund decision.

Cases — Ethoca alerts still open on that Clarity export.

AOV $ — Average order dollars on those Ethoca alerts.

ET fight-clock at-risk $ = cases × AOV. When lag stretches and ET fight-clock at-risk $ is material, chase the Ethoca fight seat — leave blank chips alone.

Hard stops

Leave ET fight-clock at-risk $ blank rather than invent. Keep Midigator or Forter lag files out of Ethoca boxes. Keep fight-share % out of the dollar burn. Keep one Ethoca MID per run when that seat owns the wait.

Related: Chargebacks, Midigator lag, Forter lag, alert-to-refund.

Procedure

  1. Type lag hours, cases, and AOV $.
  2. Read ET fight-clock at-risk $.
  3. Chase fight desk when ET fight-clock at-risk $ is material with fat lag.

Failure modes

  • Inventing ET fight-clock at-risk $.
  • Dumping Midigator or Kount lag files into Ethoca boxes.
  • Treating fight-share % as dollar burn.

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

ET fight-clock at-risk $
Cases × AOV $ on one Ethoca intake fight-clock export; lag hours held beside.

Work with us — We run this job on your accounts. Services

FAQ

Is this Midigator alert-to-fight lag?
Clarity intake vs Midigator alert-rail. [Alert-to-fight lag](/manuals/midigator-alert-to-fight-lag) prices Midigator. Ethoca alone owns cases, AOV $, and lag hours here.
Is this Forter alert-to-fight lag?
Different fraud book. [Alert-to-fight lag](/manuals/forter-alert-to-fight-lag) stays on Forter. No Forter rows enter Ethoca fields.
What ET fight-clock at-risk $ should I invent?
None. Pull lag hours, cases, and AOV $ from one Ethoca Clarity export.