Library · Chargebacks · How to run this
Open-to-loss lag is not deadline miss
Loss day − open day make lag days. Type both plus disputes.
Pair: Dispute open-to-loss lag on Chargebacks. Deadline: deadline miss rate. Pack: evidence pack hours.
What you type
Open day — day index when the dispute opened (window clock).
Loss day — day index when that cohort lost / closed as loss.
Disputes — disputes in that same open-to-loss cohort.
Lag days = loss day − open day. Fix fight cadence when lag days are fat — do not invent a lag chip.
What not to do
Do not invent lag days. Do not mix processor-response skew into day indexes. Do not treat wins as losses. Do not average every MID when one owns the lag.
Related: Chargebacks, deadline miss rate, evidence pack hours, processor response skew, representment packet minimum.
Procedure
- Type open day, loss day, and disputes.
- Read lag days.
- Fix fight cadence when lag days are material.
Failure modes
- Inventing lag days.
- Mixing processor-response skew into day indexes.
- Treating wins as losses.
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
- Dispute open-to-loss lag days
- Loss/closed day − open day for the typed dispute cohort.
Work with us — We run this job on your accounts. Services
FAQ
- Is this deadline miss rate?
- Sibling fight clock. [Deadline miss rate](/manuals/chargeflow-deadline-miss-rate) is late fights ÷ total. This page is loss day − open day on Braintree.
- Is this evidence pack hours?
- Related labor. [Evidence pack hours](/manuals/chargeflow-evidence-pack-hours) is pack build time. This page is dispute open-to-loss lag.
- What lag days should I invent?
- None. Type open day, loss day, and disputes from the same Braintree window.