Library · Chargebacks · How to run this
Chargeflow AI-intake issuer-reply lane is not Kount score-gated issuer-reply rail
Run one Chargeflow AI-intake issuer-reply lane. Note when the network ask landed in intake. Note when the issuer answered. Keep case rows beside that lane. The difference is CF issuer-reply hours — Kount score-gated issuer-reply rails and Chargeflow auto-fight second-presentment reply queues never feed this AI-intake cut.
Pair: Issuer-reply lag under Chargebacks. Request twin: CF issuer-request. Second-presentment twin: CF second-presentment.
AI-intake issuer-reply stamps
Ask hour — Hour the network ask landed in intake on the AI-intake issuer-reply lane.
Answer hour — Hour the issuer answered on the same lane.
Cases — Chargeflow issuer-reply rows inside that ask → answer lane.
CF issuer-reply hours = answer hour − ask hour. When CF issuer-reply hours stretch, staff this AI-intake lane before you chase issuer-doc lag. Leave blank chips alone.
Hard stops
Skip inventing CF issuer-reply hours. Skip dumping issuer-doc CSVs, second-presentment stamps, or Kount score-gated rail hours into ask/answer boxes. Skip folding CF pack-hole % into answer hours. Skip fusing MIDs when one Chargeflow AI-intake issuer-reply lane owns the stack.
Related: Chargebacks, CF issuer-request, CF second-presentment, CF pre-arb pack.
Procedure
- Type ask hour, answer hour, and cases.
- Read CF issuer-reply hours.
- Staff the AI-intake issuer-reply lane when CF issuer-reply hours stretch.
Failure modes
- Inventing CF issuer-reply hours.
- Dumping issuer-doc CSVs, second-presentment stamps, or Kount score-gated rail hours into ask/answer boxes.
- Folding CF pack-hole % into answer hours.
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 issuer-reply hours
- Answer hour − ask hour on one Chargeflow AI-intake issuer-reply lane.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Kount issuer-reply lag?
- Chargeflow AI-intake issuer-reply lane vs Kount score-gated issuer-reply rail. [Issuer-reply lag](/manuals/kount-issuer-reply-lag) stays on Kount. Ask → answer hours for Chargeflow belong on this AI-intake lane.
- Is this Chargeflow issuer-request lag?
- AI-intake issuer-reply lane vs AI-intake issuer-doc lane. [Issuer-request lag](/manuals/chargeflow-issuer-request-lag) clocks intake → handoff. Here you only score answer hour − ask hour on the issuer-reply lane.
- What CF issuer-reply hours should I invent?
- None. Pull ask hour, answer hour, and Chargeflow case rows from the same AI-intake issuer-reply lane.