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