Library · Chargebacks · How to run this
Kount score-gated issuer-doc rail is not Midigator network-reply issuer-ask bay
Grab one Kount score-gated issuer-doc rail. Note when the issuer document ask arrived inbound. Note when Kount sent outbound. Keep request rows beside that span. The difference is KT issuer-request hours — Midigator network-reply issuer-ask bays and Kount pre-arb packet desks never feed this score-gated rail.
Pair: Issuer-request lag under Chargebacks. Midigator twin: MG issuer-request. Pre-arb twin: KT pre-arb pack.
Score-gated issuer-doc stamps
Inbound hour — Hour Kount logged the issuer document ask on the score-gated issuer-doc rail.
Outbound hour — Hour Kount posted the issuer-doc answer on that same rail.
Requests — Kount score-gated issuer-doc rows inside the inbound → outbound slice.
KT issuer-request hours = outbound hour − inbound hour. Fat KT issuer-request hours means clear the score-gated issuer-doc pile before you chase pre-arb packs — blank chips stay blank.
Refuse these shortcuts
Refuse inventing KT issuer-request hours. Refuse dumping Midigator network-reply issuer-ask CSVs, Kount pre-arb packet boards, or first-seen ack stamps into inbound/outbound boxes. Refuse folding KT pack-hole % into outbound-hour fields. Refuse blending MIDs when one score-gated issuer-doc rail owns the ask pile.
See also: Chargebacks, MG issuer-request, KT pre-arb pack, KT pack-build.
Procedure
- Type inbound hour, outbound hour, and requests.
- Read KT issuer-request hours.
- Clear the score-gated issuer-doc pile when KT issuer-request hours are material.
Failure modes
- Inventing KT issuer-request hours.
- Dumping Midigator network-reply issuer-ask or Kount pre-arb packet CSVs into inbound/outbound boxes.
- Folding KT pack-hole % into outbound-hour fields.
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-request hours
- Outbound hour − Inbound hour on one Kount score-gated issuer-doc rail.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Midigator issuer-request lag?
- Kount score-gated issuer-doc rail vs Midigator network-reply issuer-ask bay. [Issuer-request lag](/manuals/midigator-issuer-request-lag) stays on Midigator. Inbound / outbound hours for Kount issuer document asks belong on this score-gated rail.
- Is this Kount pre-arb pack lag?
- Issuer-doc turnaround vs score-gated pre-arb packet build. [Pre-arb pack lag](/manuals/kount-pre-arb-pack-lag) clocks pack open to ready. Here you only score issuer-doc outbound − inbound.
- What KT issuer-request hours should I invent?
- None. Pull inbound hour, outbound hour, and request rows from the same Kount score-gated issuer-doc rail.