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

Library · Chargebacks · How to run this

Forter dispute-packet file gap is not Ethoca alert-packet hole

How to run thisChargebacks3 steps
CalculatorForter evidence-upload miss share · Calculator lives in the articleOpen

Open one Forter dispute-packet desk. Tally gap uploads. Divide by uploads started. The chip is FT mid-upload % — leave Ethoca alert-packet pages alone.

Pair: Evidence-upload miss share on Chargebacks. Ethoca twin: ET mid-upload. Deadline twin: deadline-miss.

Dispute-packet fields

Gap uploads — Forter evidence uploads that omitted at least one required dispute-packet file.

Uploads started — Evidence uploads begun in that same Forter dispute-packet window.

FT mid-upload % = gap uploads ÷ uploads started × 100. A fat chip usually means dispute-packet checklist drift on that Forter MID — staff the dispute desk; blank chips stay blank.

Hard stops

Do not invent FT mid-upload %. Do not load Ethoca holey-upload exports into Forter boxes. Do not fold deadline-miss tallies into gap uploads. Do not dump false-positive CB rows into Forter upload fields.

Related: Chargebacks, ET mid-upload, deadline-miss, false-positive CB.

Procedure

  1. Type gap uploads and uploads started.
  2. Read FT mid-upload %.
  3. Chase dispute-packet coverage when FT mid-upload % is material.

Failure modes

  • Inventing FT mid-upload %.
  • Pasting an Ethoca holey-upload export into Forter boxes.
  • Dumping deadline-miss rows into gap / started fields.

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 mid-upload %
Gap uploads ÷ Uploads started × 100 on one Forter dispute-packet desk.

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

FAQ

Is this Ethoca evidence-upload miss share?
Forter dispute-packet desk vs Ethoca alert-packet desk. [Evidence-upload miss share](/manuals/ethoca-evidence-upload-miss-share) stays on Ethoca. Gap uploads / started never leave Forter here.
Is this Forter deadline-miss share?
Packet file coverage vs late-file clock. [Deadline-miss share](/manuals/forter-deadline-miss-share) ratios late files. Here you only ratio gap uploads against uploads started.
What FT mid-upload % should I invent?
None. Pull gap uploads and uploads started from the same Forter dispute-packet desk.