RedHub AIRedHub AI
Tool Gate · How it works

How the gate works

How the Chargeback-Proof Order Evidence gate works

This tool grades the evidence you have against the reason code the bank actually filed - the one decisive item that code turns on can force the case to DON'T FIGHT even when everything else scores well. It scores 5 weighted controls into a 0–100 number — then a gate that can only make the verdict worse.

The 5 weighted controls

01Proof of delivery to the cardholder's address (carrier tracking DELIVERED, signature where available)gate · decisive - absent forces DON'T FIGHTwt 38
02Shipping address matches the AVS-verified billing addresswt 22
03Order confirmation / itemized receipt with transaction and fulfillment detailswt 16
04Carrier record of expected vs actual delivery date within the promised windowwt 14
05Customer communications acknowledging receipt or trackingwt 10
SUBMIT-READY
score 75+
STRENGTHEN
score 40+
DON'T FIGHT
below floor
Decisive-item gate · worsen-only

Every reason code has one dispositive evidence item. If it's absent - or the response window has already closed - the verdict is forced to DON'T FIGHT no matter how the other items score.

62/100
DON'T FIGHT

Why: Completeness scores 62/100 for a Merchandise/Services Not Received dispute - the AVS match, order receipt, carrier record, and customer comms are all present, which alone would read STRENGTHEN. But proof of delivery - the one decisive item this reason code turns on - is absent, so the gate overrides the score and forces DON'T FIGHT: a high score on everything else still loses without it.

Fix firstGet proof of delivery to the cardholder's address (carrier tracking showing DELIVERED) - the decisive item for a Not Received dispute; nothing else can substitute for it.

A high score didn’t save it. The score is context; the gate is the answer — and it names the one thing to fix first. Grades the evidence and reason code you enter - a planning aid, not legal advice; confirm reason-code requirements with your own processor.