Library · Chargebacks · How to run this
False-negative is not false-positive cost
Missed-fraud CBs ÷ reviewed orders make FN %. Type both.
Pair: False-negative CB rate on Chargebacks. FP cost: false-positive cost. Overlap: abuse vs chargeback overlap.
What you type
Missed-fraud CBs — chargebacks on orders the stack allowed / cleared that you label as fraud misses.
Reviewed orders — orders in the reviewed / decisioned set for that same window.
FN % = missed-fraud CBs ÷ reviewed × 100. Tighten allow rules when FN % is fat — do not invent an FN chip.
What not to do
Do not invent FN %. Do not mix friendly fraud into missed-fraud without splitting. Do not treat false-positive blocks as FN. Do not average every MID when one owns the hole.
Related: Chargebacks, false-positive cost, abuse vs chargeback overlap, fraud review queue cost.
Procedure
- Type missed-fraud CBs and reviewed orders.
- Read FN %.
- Tighten allow rules when FN % is material.
Failure modes
- Inventing FN %.
- Mixing friendly fraud into missed-fraud without splitting.
- Treating false-positive blocks as FN.
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
- False-negative CB %
- Missed-fraud chargebacks ÷ reviewed orders × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this false-positive cost?
- Sibling error. [False-positive cost](/manuals/forter-false-positive-cost) prices blocked good orders × AOV. This page is missed-fraud CBs ÷ reviewed orders.
- Is this abuse–CB overlap?
- Related signal. [Abuse vs chargeback overlap](/manuals/sift-abuse-chargeback-overlap) is score overlap. This page is false-negative CB rate on the reviewed set.
- What FN % should I invent?
- None. Type missed-fraud CBs and reviewed orders from the same Forter / CB window.