Library · Chargebacks · How to run this
Verifi CDRN packet age is not Midigator case-close span
On one Verifi CDRN packet ledger, VF lag days equals closed day minus filed day. Outcome does not age the packet.
Pair: Representment lag days on Chargebacks. Midigator twin: Midigator lag. Win twin: representment win.
Packet ledger fields
Filed day — Day Verifi recorded the CDRN representment packet as filed.
Closed day — Day that CDRN packet flipped closed on the Verifi ledger.
VF lag days = closed day − filed day. Fat VF lag days usually means chase CDRN evidence or issuer reply on that Verifi seat — never invent a VF lag chip.
What not to do
Skip inventing VF lag days. Skip dumping alert-to-fight at-risk $ into filed/closed fields. Skip pasting Midigator case-close CSVs into Verifi boxes. Skip blending CDRN seats when one Verifi MID owns the open packet pile.
Related: Chargebacks, Midigator lag, representment win, alert-to-fight lag.
Procedure
- Type filed day and closed day.
- Read VF lag days.
- Chase evidence / CDRN close when VF lag days are material.
Failure modes
- Inventing VF lag days.
- Loading alert-to-fight at-risk $ into filed/closed boxes.
- Folding Midigator lag into Verifi 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
- VF lag days
- Closed day − filed day on one Verifi CDRN fight export.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Midigator representment lag days?
- CDRN packet ledger vs Midigator case-close board. [Representment lag days](/manuals/midigator-representment-lag-days) stays on Midigator. Filed / closed days never leave Verifi here.
- Is this Verifi representment win rate?
- Packet age vs win mix. [Representment win rate](/manuals/verifi-representment-win-rate) scores closed wins ÷ fought. Here you only score closed − filed days.
- What VF lag days should I invent?
- None. Source filed day and closed day from the same Verifi CDRN packet ledger.