Library · Chargebacks · How to run this
Chargebacks911 reason-code match desk is not issuer-request reply desk
Work one Chargebacks911 reason-code match desk. Count cases where the network reason code does not match the merchant fight reason. Divide by cases that desk scored. Multiply by 100 for C9 reason-code-mismatch %. Issuer-request reply desks and pack-build lanes never feed this match cut.
Pair: Reason-code mismatch share under Chargebacks. Reply twin: C9 issuer-request. Pre-arb twin: C9 pre-arb miss.
Reason-code match columns
Mismatched cases — Chargebacks911 cases where network reason ≠ merchant fight reason on the reason-code match desk.
Cases scored — Chargebacks911 fight cases that match desk scored in the same window.
C9 reason-code-mismatch % = mismatched cases ÷ cases scored × 100. A fat C9 reason-code-mismatch % chip means remap fight reasons on that desk — leave blank chips alone.
Guardrails
Do not invent C9 reason-code-mismatch %. Do not fold issuer-request lag hours or pack-build holes into the mismatched tally. Do not paste Ethoca/Verifi reason exports or C9 deadline-miss CSVs into case boxes. Do not blend MIDs when one Chargebacks911 reason-code match desk owns the mismatch pile.
Related: Chargebacks, C9 issuer-request, C9 pre-arb miss, C9 pack-build.
Procedure
- Type mismatched cases and cases scored.
- Read C9 reason-code-mismatch %.
- Remap fight reasons when C9 reason-code-mismatch % is material.
Failure modes
- Inventing C9 reason-code-mismatch %.
- Folding issuer-request lag hours or pack-build holes into the mismatched tally.
- Pasting Ethoca/Verifi reason exports or C9 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
- C9 reason-code-mismatch %
- Mismatched cases ÷ cases scored × 100 on one Chargebacks911 reason-code match desk.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Chargebacks911 issuer-request lag?
- Reason-code match desk vs issuer-request reply desk. [Issuer-request lag](/manuals/chargebacks911-issuer-request-lag) clocks reply hour − request hour. Here you only score cases where network reason ≠ merchant fight reason.
- Is this Chargebacks911 pre-arb miss share?
- Reason mismatch vs unanswered pre-arb. [Pre-arb miss share](/manuals/chargebacks911-pre-arb-miss-share) tallies missed pre-arb packets. Here the chip is reason-code mismatch on the match desk.
- What C9 reason-code-mismatch % should I invent?
- None. Source mismatched cases and cases scored from the same Chargebacks911 reason-code match desk.