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

Library · Chargebacks · How to run this

Forter fight share is not Chargeflow fight share

How to run thisChargebacks3 steps
CalculatorForter alert-to-fight share · Calculator lives in the articleOpen

FT fight % is the slice of Forter risk-intake alerts that the desk puts into a dispute packet in one risk window. Fought desk rows count. Every Forter risk-intake alert sits under.

Pair: Alert-to-fight share on Chargebacks. Pack twin: Chargeflow alert-to-fight. Repeat twin: duplicate-alert.

What you type

Alerts fought — Forter risk-intake alerts the desk sent into a dispute packet in the window.

Alerts — Every Forter risk-intake alert in that same risk window.

FT fight % = fought ÷ alerts × 100. A fat FT fight % usually means the refund default on that Forter seat is too loose — write it before you staff more packets. Never invent an FT fight chip.

What not to do

Do not invent FT fight %. Do not load a Chargeflow pack or Chargebacks911 intake file into Forter fields. Do not count duplicate alerts or false-positive CBs as fights. Do not blend networks when Forter alone owns the packet pile.

Related: Chargebacks, Chargeflow alert-to-fight, duplicate-alert, false-positive CB.

Procedure

  1. Type alerts fought and alerts.
  2. Read FT fight %.
  3. Tighten the refund fork when FT fight % is material.

Failure modes

  • Inventing FT fight %.
  • Dumping a Chargeflow or Chargebacks911 fight file into Forter fields.
  • Counting duplicate alerts or false-positive CBs 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

FT fight %
Alerts fought ÷ Alerts × 100.

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

FAQ

Is this Chargeflow alert-to-fight share?
Pack console vs risk desk. [Chargeflow alert-to-fight](/manuals/chargeflow-alert-to-fight-share) scores Chargeflow representment packs. Here both counts are Forter risk-intake rows.
Is this Forter duplicate-alert share?
Repeat rows vs fight decisions. [Duplicate-alert share](/manuals/forter-duplicate-alert-share) is repeats ÷ alerts. This page is fought ÷ alerts.
What FT fight % should I invent?
None. Export fought Forter alerts and total alerts from one Forter risk window.