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

Library · Chargebacks · How to run this

Chargeflow auto-fight pack queue is not Forter dispute-workspace rail

How to run thisChargebacks3 steps
CalculatorChargeflow representment pack lag · Calculator lives in the articleOpen

Grab a Chargeflow auto-fight pack queue. Clock assembly from start to ready. Park packs next to that span. Label the span CF pack-build hours — Forter dispute-workspace rails never feed this queue.

Pair: Representment pack lag under Chargebacks. Forter twin: FT pack-build. Day twin: CF lag days.

Queue assembly fields

Start hour — Hour Chargeflow began building the evidence pack on the auto-fight queue.

Ready hour — Hour Chargeflow marked that pack complete on the same queue.

Packs — Chargeflow pack rows inside the start → ready slice.

CF pack-build hours = ready hour − start hour. When CF pack-build hours fatten, clear the Chargeflow assembly pile on that MID — empty chips stay empty.

What not to do

Skip inventing CF pack-build hours. Skip loading Forter dispute-workspace or Ethoca alert-desk pack CSVs into Chargeflow start/ready boxes. Skip folding CF pack-hole % into ready-hour fields. Skip fusing MIDs when one Chargeflow auto-fight pack queue owns the pack stack.

Related: Chargebacks, FT pack-build, CF lag days, CF pack-hole.

Procedure

  1. Type start hour, ready hour, and packs.
  2. Read CF pack-build hours.
  3. Clear assembly pile when CF pack-build hours are material.

Failure modes

  • Inventing CF pack-build hours.
  • Loading Forter dispute-workspace or Ethoca alert-desk pack CSVs into Chargeflow boxes.
  • Folding CF pack-hole % into ready-hour 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

CF pack-build hours
Ready hour − Start hour on one Chargeflow auto-fight pack queue.

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

FAQ

Is this Forter representment pack lag?
Chargeflow auto-fight pack queue vs Forter dispute-workspace pack rail. [Representment pack lag](/manuals/forter-representment-pack-lag) stays on Forter. Start / ready hours belong on this Chargeflow queue.
Is this Chargeflow representment lag days?
Pack assembly hours vs evidence-sent→bank-decision days. [Representment lag days](/manuals/chargeflow-representment-lag-days) ends when the bank decides. Here the clock ends when the evidence pack is ready.
What CF pack-build hours should I invent?
None. Pull start hour, ready hour, and packs from the same Chargeflow auto-fight pack queue.