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

Library · Chargebacks · How to run this

Abuse blocks can still chargeback

How to run thisChargebacks3 steps
CalculatorAbuse–CB overlap · Calculator lives in the articleOpen

Abuse tools block orders. Some of those still get a chargeback. Overlap % = CB-after-block ÷ blocks. False-positive % = good orders blocked ÷ blocks. Type blocks, CB-after-block, and false positives.

Pair: Abuse–CB overlap on Chargebacks. Who blocked: fraud block vs issuer. Alert decision: alert refund vs fight.

What you type

Blocks — abuse / fraud blocks in the window (tool decision, not issuer decline).

CB-after-block — chargebacks posted on orders that tool already blocked (matched export).

False positives — blocked orders you later marked good / released / should not have blocked.

Overlap % = CB-after-block ÷ blocks. FP % = false positives ÷ blocks. Tune rules when overlap or FP is material — do not invent a chip.

What not to do

Do not invent an overlap percent. Do not mix issuer soft declines into the block count. Do not treat “blocked” as CB-proof. Do not ignore false positives when the overlap looks fine.

Related: Chargebacks, fraud block vs issuer, alert refund vs fight, fraud review queue cost.

Procedure

  1. Type abuse / fraud block count.
  2. Type CBs matched to that blocked set and false positives.
  3. Tune rules when overlap or FP is high.

Failure modes

  • Inventing an overlap percent.
  • Mixing issuer declines into the block count.
  • Treating blocked as CB-proof.

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

Abuse–CB overlap
Chargebacks posted on orders an abuse / fraud tool already blocked. Overlap % = CB-after-block ÷ blocks.

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

FAQ

Is this fraud block vs issuer?
Related fork. [Fraud block vs issuer](/manuals/fraud-block-vs-issuer) splits who said no at auth. This page is CBs that still arrived after an abuse block.
Is this alert refund vs fight?
Related decision after the dispute. [Alert refund vs fight](/manuals/alert-refund-vs-fight) is fee EV. This page is overlap on the blocked set.
What overlap percent should I invent?
None. Type CB-after-block from the dispute export matched to the block list.