Library · Chargebacks · How to run this
Midigator fight wins are not Kount fight wins
Pull one Midigator alert-rail fight export. Count won rows. Divide by contested rows. The quotient × 100 is MG win %.
Pair: Representment win rate on Chargebacks. Kount twin: Kount win. Forter twin: Forter win.
Export fields
Won rows — Midigator fights the alert-rail closed as merchant-won in the export window.
Contested rows — Midigator fights you filed on that same alert-rail (exclude auto-accepts).
MG win % = won rows ÷ contested rows × 100. Thin MG win % usually means the evidence pack or reason pick on that rail — fix that path; leave blank chips alone.
Guardrails
Skip inventing MG win %. Skip pasting Kount or Forter fight exports into Midigator fields. Skip parking auto-accepts in the won pile. Skip merging Midigator rails when one MID owns the loss rate.
Related: Chargebacks, Kount win, Forter win, alert-to-fight lag.
Procedure
- Type closed wins and disputes fought.
- Read MG win %.
- Repair evidence pack / reason selection when MG win % is thin.
Failure modes
- Inventing MG win %.
- Loading Kount or Forter fight files into Midigator boxes.
- Counting auto-accepts as wins.
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
- MG win %
- Won rows ÷ contested rows × 100 on one Midigator alert-rail fight export.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Kount representment win rate?
- Midigator alert-rail vs Kount dispute queue. [Representment win rate](/manuals/kount-representment-win-rate) stays on Kount. Won / contested rows never leave Midigator here.
- Is this Forter representment win rate?
- Separate CE book. [Representment win rate](/manuals/forter-representment-win-rate) stays on Forter. Midigator owns every count on this page.
- What MG win % should I invent?
- None. Source won rows and contested rows from the same Midigator alert-rail fight export.