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

Library · Chargebacks · How to run this

Ethoca Clarity reason-code match rail is not Chargebacks911 reason-code match desk

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

Work one Ethoca Clarity reason-code match rail. Count cases where the Clarity reason code does not match the merchant fight reason. Divide by cases that rail scored. Multiply by 100 for ET reason-code-mismatch %. Chargebacks911 match desks and Ethoca issuer-request reply rails never feed this Clarity match cut.

Pair: Reason-code mismatch share under Chargebacks. Chargebacks911 twin: C9 reason-code mismatch. Reply twin: ET issuer-request.

Clarity reason-code match columns

Mismatched cases — Ethoca cases where Clarity reason ≠ merchant fight reason on the Clarity reason-code match rail.

Cases scored — Ethoca Clarity fight cases that match rail scored in the same window.

ET reason-code-mismatch % = mismatched cases ÷ cases scored × 100. A fat ET reason-code-mismatch % chip means remap Clarity fight reasons on that rail — leave blank chips alone.

Guardrails

Do not invent ET reason-code-mismatch %. Do not fold issuer-request lag hours or Clarity clock-outs into the mismatched tally. Do not paste Chargebacks911 match-desk or Ethoca deadline-miss CSVs into case boxes. Do not blend MIDs when one Ethoca Clarity reason-code match rail owns the mismatch pile.

Related: Chargebacks, C9 reason-code mismatch, ET issuer-request, ET Clarity timeout.

Procedure

  1. Type mismatched cases and cases scored.
  2. Read ET reason-code-mismatch %.
  3. Remap Clarity fight reasons when ET reason-code-mismatch % is material.

Failure modes

  • Inventing ET reason-code-mismatch %.
  • Folding issuer-request lag hours or Clarity clock-outs into the mismatched tally.
  • Pasting Chargebacks911 match-desk or Ethoca deadline-miss CSVs into 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

ET reason-code-mismatch %
Mismatched cases ÷ cases scored × 100 on one Ethoca Clarity reason-code match rail.

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

FAQ

Is this Chargebacks911 reason-code mismatch share?
Ethoca Clarity reason-code match rail vs Chargebacks911 reason-code match desk. [Reason-code mismatch share](/manuals/chargebacks911-reason-code-mismatch-share) stays on Chargebacks911. Mismatched / scored totals for Ethoca belong on this Clarity rail.
Is this Ethoca issuer-request lag?
Reason mismatch vs Clarity issuer-request reply clock. [Issuer-request lag](/manuals/ethoca-issuer-request-lag) clocks reply stamp − request stamp. Here you only score cases where Clarity reason ≠ merchant fight reason.
What ET reason-code-mismatch % should I invent?
None. Source mismatched cases and cases scored from the same Ethoca Clarity reason-code match rail.