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

Library · Chargebacks · How to run this

Chargeflow evidence seat clock to bank decision

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

Open one Chargeflow evidence-seat board. Subtract evidence-sent day from bank-decision day. That integer is CF lag days. Win or loss does not stretch the clock.

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

Board columns

Evidence-sent day — Day the Chargeflow evidence pack left the seat board.

Bank-decision day — Day the issuer / network marked that Chargeflow case decided.

CF lag days = bank-decision day − evidence-sent day. A fat CF lag days reading means chase evidence pack or issuer queue on that Chargeflow MID — blank chips stay blank.

Stops

Never invent CF lag days. Never drop alert-to-fight at-risk $ into sent/decision columns. Never paste Forter contested-case CSVs into Chargeflow boxes. Never fuse MIDs when one Chargeflow seat owns the open evidence pile.

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

Procedure

  1. Type filed day and closed day.
  2. Read CF lag days.
  3. Chase evidence / issuer queue when CF lag days are material.

Failure modes

  • Inventing CF lag days.
  • Loading alert-to-fight at-risk $ into filed/closed boxes.
  • Folding Forter lag into Chargeflow 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

CF lag days
Closed day − filed day on one Chargeflow representment cut.

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

FAQ

Is this Forter representment lag days?
Chargeflow evidence-seat board vs Forter contested-case ledger. [Representment lag days](/manuals/forter-representment-lag-days) stays on Forter. Sent / decision days never leave Chargeflow here.
Is this Chargeflow alert-to-fight lag?
Evidence-seat clock vs desk-wait dollars. [Alert-to-fight lag](/manuals/chargeflow-alert-to-fight-lag) scores cases × AOV at-risk $. Here you only score bank-decision − evidence-sent days.
What CF lag days should I invent?
None. Read evidence-sent day and bank-decision day from the same Chargeflow evidence-seat board.