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

Library · Chargebacks · How to run this

Midigator alert-rail reason-code match cut is not Verifi CDRN reason-code match bay

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

Work one Midigator alert-rail reason-code match cut. Count cases where the alert-rail reason code does not match the merchant fight reason. Divide by cases that cut scored. Multiply by 100 for MG reason-code-mismatch %. Verifi CDRN match bays and Midigator issuer-ask reply bays never feed this alert-rail match cut.

Pair: Reason-code mismatch share under Chargebacks. Verifi twin: VF reason-code mismatch. Reply twin: MG issuer-request.

Alert-rail reason-code match columns

Mismatched cases — Midigator cases where alert-rail reason ≠ merchant fight reason on the alert-rail reason-code match cut.

Cases scored — Midigator alert-rail fight cases that match cut scored in the same window.

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

Guardrails

Do not invent MG reason-code-mismatch %. Do not fold issuer-request lag hours or alert-rail clock-outs into the mismatched tally. Do not paste Verifi CDRN match-bay or Midigator deadline-miss CSVs into case boxes. Do not blend MIDs when one Midigator alert-rail reason-code match cut owns the mismatch pile.

Related: Chargebacks, VF reason-code mismatch, MG issuer-request, ET reason-code mismatch.

Procedure

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

Failure modes

  • Inventing MG reason-code-mismatch %.
  • Folding issuer-request lag hours or alert-rail clock-outs into the mismatched tally.
  • Pasting Verifi CDRN match-bay or Midigator 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

MG reason-code-mismatch %
Mismatched cases ÷ cases scored × 100 on one Midigator alert-rail reason-code match cut.

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

FAQ

Is this Verifi reason-code mismatch share?
Midigator alert-rail reason-code match cut vs Verifi CDRN reason-code match bay. [Reason-code mismatch share](/manuals/verifi-reason-code-mismatch-share) stays on Verifi. Mismatched / scored totals for Midigator belong on this alert-rail cut.
Is this Midigator issuer-request lag?
Reason mismatch vs network-reply issuer-ask clock. [Issuer-request lag](/manuals/midigator-issuer-request-lag) clocks answered − asked. Here you only score cases where alert-rail reason ≠ merchant fight reason.
What MG reason-code-mismatch % should I invent?
None. Source mismatched cases and cases scored from the same Midigator alert-rail reason-code match cut.