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

Library · Chargebacks · How to run this

Refund-seat bank wait is not fight-seat bank wait

How to run thisChargebacks3 steps
CalculatorDisputifier alert-to-CB lag · Calculator lives in the articleOpen

On a Disputifier refund-seat cut, DF refund-seat bank-lag days equal the distance from alert day to bank CB day. Hold alerts that became CB next to that distance so the cut stays sized.

Pair: Alert-to-CB lag on Chargebacks. Fight-seat twin: Chargeflow lag. Slip twin: alert-escape.

What you type

Alert day — Refund-seat stamp Disputifier wrote when the alert fired.

CB day — Stamp when that refund-seat alert posted as a bank CB.

Alerts that became CB — Refund-seat alerts in the cut that later posted as CB.

DF refund-seat bank-lag days = CB day − alert day. Fat DF refund-seat bank-lag days usually mean auto-refund / fight lag on that seat — chase that path; never invent a DF refund-seat bank-lag chip.

What not to do

Skip inventing DF refund-seat bank-lag days. Skip dumping a Chargeflow fight-seat or Chargeblast bank-CB file into Disputifier refund fields. Skip folding escape % into day stamps. Skip blending MIDs when one refund seat owns the hole.

Related: Chargebacks, Chargeflow lag, alert-escape, alert-to-refund.

Procedure

  1. Type alert day, CB day, and alerts that became CB.
  2. Read DF refund-seat bank-lag days.
  3. Chase refund-seat bank response when DF refund-seat bank-lag days are material.

Failure modes

  • Inventing DF refund-seat bank-lag days.
  • Loading a Chargeflow or Chargeblast clock into Disputifier boxes.
  • Folding alert-escape % into day indexes.

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

DF refund-seat bank-lag days
CB day − alert day on one Disputifier refund-seat bank-CB cut.

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

FAQ

Is this Chargeflow alert-to-CB lag?
Fight-seat book vs refund-seat book. [Alert-to-CB lag](/manuals/chargeflow-alert-to-cb-lag) stays on Chargeflow. Refund-seat stamps never leave Disputifier here.
Is this Disputifier alert-escape rate?
Slip share vs wait days. [Alert-escape rate](/manuals/disputifier-alert-escape-rate) divides refund-seat slips by alerts. Here the readout is day-index distance.
What DF refund-seat bank-lag days should I invent?
None. Source alert day, CB day, and alerts that became CB from one Disputifier refund-seat export.