Skip to article
ecomservices.io
Chargebacks · How to run this
MatchingNot on this page yetPricingCalculatorIntakeCalculatorReason codesCalculatorRepresentmentCalculatorThresholdsCalculatorAllocationCalculatorOptimisationCalculatorPrevention stackCalculatorProviders

Library · Chargebacks · How to run this

Kount dispute-queue reason-code match desk is not Ethoca Clarity reason-code match rail

How to run thisChargebacks3 steps
CalculatorKount reason-code mismatch share · Calculator lives in the articleOpen

Open one Kount dispute-queue reason-code match desk. Tally fight rows where the queue reason disagrees with the merchant representment reason. Put that tally over fights the desk scored. The quotient × 100 is KT reason-code-mismatch %. Ethoca Clarity rails, Midigator alert-rail cuts, and Kount issuer-doc clocks stay off this dispute-queue book.

Pair: Reason-code mismatch share under Chargebacks. Ethoca twin: ET reason-code mismatch. Midigator twin: MG reason-code mismatch.

Dispute-queue match math

Mismatched cases — Kount dispute-queue fights whose queue reason ≠ merchant representment reason on the reason-code match desk.

Cases scored — Kount dispute-queue fights that desk scored in the same export window.

KT reason-code-mismatch % = mismatched cases ÷ cases scored × 100. Climbing KT reason-code-mismatch % means realign queue fight reasons on that desk — blank chips stay blank.

Hard stops

Skip inventing KT reason-code-mismatch %. Skip folding issuer-doc lag hours or score-gate timeouts into the skew tally. Skip dumping Ethoca Clarity rail or Midigator alert-rail CSVs into Kount case boxes. Skip blending MIDs when one Kount dispute-queue reason-code match desk owns the skew pile.

See also: Chargebacks, ET reason-code mismatch, MG reason-code mismatch, KT issuer-request.

Procedure

  1. Type mismatched cases and cases scored.
  2. Read KT reason-code-mismatch %.
  3. Realign queue fight reasons when KT reason-code-mismatch % is material.

Failure modes

  • Inventing KT reason-code-mismatch %.
  • Folding issuer-doc lag hours or score-gate timeouts into the skew tally.
  • Pasting Ethoca Clarity rail or Midigator alert-rail CSVs into Kount case 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

KT reason-code-mismatch %
Mismatched cases ÷ cases scored × 100 on one Kount dispute-queue reason-code match desk.

Work with us — We run this job on your accounts. Services

FAQ

Is this Ethoca reason-code mismatch share?
Kount dispute-queue reason-code match desk vs Ethoca Clarity reason-code match rail. [Reason-code mismatch share](/manuals/ethoca-reason-code-mismatch-share) stays on Ethoca. Skew / scored fights for Kount belong on this dispute-queue desk.
Is this Midigator reason-code mismatch share?
Dispute-queue desk vs alert-rail cut. [Reason-code mismatch share](/manuals/midigator-reason-code-mismatch-share) stays on Midigator. Here both counts come from the Kount dispute-queue reason-code match desk.
What KT reason-code-mismatch % should I invent?
None. Export reason skew rows and fights scored from the same Kount dispute-queue reason-code match desk.