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

Library · Chargebacks · How to run this

Midigator case close span is not Kount queue wait

How to run thisChargebacks3 steps
CalculatorMidigator representment lag days · Calculator lives in the articleOpen

Pull one Midigator case-close board. Take close day. Subtract file day. That integer is MG lag days. Outcome chips do not stretch the span.

Tool: Representment lag days under Chargebacks. Neighbor on Kount: Kount lag. Dollar counterpart: alert-to-fight lag.

Case-close columns

File day — Day the Midigator representment packet was filed on the case-close board.

Close day — Day the issuer / network marked that Midigator case closed.

MG lag days = close day − file day. A fat MG lag days reading means chase packet prep or network close on that Midigator MID — blank chips stay blank.

Stops

Never invent MG lag days. Never drop alert-to-fight at-risk $ into file/close columns. Never paste Kount issuer-queue CSVs into Midigator boxes. Never fuse MIDs when one Midigator seat owns the open fight pile.

Related: Chargebacks, Kount lag, alert-to-fight lag, representment win.

Procedure

  1. Type filed day and closed day.
  2. Read MG lag days.
  3. Chase evidence / network close when MG lag days are material.

Failure modes

  • Inventing MG lag days.
  • Loading alert-to-fight at-risk $ into filed/closed boxes.
  • Folding Kount lag into Midigator boxes.

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 lag days
Closed day − filed day on one Midigator representment cut.

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

FAQ

Is this Kount representment lag days?
Midigator case-close board vs Kount issuer-queue export. [Representment lag days](/manuals/kount-representment-lag-days) stays on Kount. File / close days never leave Midigator here.
Is this Midigator alert-to-fight lag?
Case-close span vs desk-wait dollars. [Alert-to-fight lag](/manuals/midigator-alert-to-fight-lag) scores cases × AOV at-risk $. Here you only score close − file days.
What MG lag days should I invent?
None. Read file day and close day from the same Midigator case-close board.