Know if your payment accountis on a termination path.

No. It computes where your ratio sits against the thresholds you confirm and tells you honestly whether you're in headroom, approaching, or over the line — and it names what to fix first. It files nothing, contacts no acquirer, and moves no money. The hard truth it's built around: winning a representment does not lower a counted chargeback. The event still counts toward your ratio. Only pre-dispute deflection (RDR / Compelling Evidence 3.0) and proactive refunds remove events from the count, which is exactly why the tool separates your ratio position from your prevention posture instead of blending them.

Because they're dated, regional, and change by bulletin, and a hard-coded number would quietly go wrong. The kit ships the verified defaults effective April 1, 2026 — Visa VAMP merchant Excessive at 1.5% (down from 2.2%), monitored at 1,500+ combined events; Mastercard ECP at 1.5% with 100+ disputes a month. But US, Canada, EU and APAC sit at 1.5% while CEMEA is 2.2%, and the widely-repeated 0.9% Visa merchant figure isn't in Visa's published documentation at all. You confirm your current numbers against your acquirer statement and the live network bulletins and edit four cells; the engine computes against whatever you enter.

VAMP ratio = (TC40 fraud reports + TC15 disputes) divided by total card-not-present settled transactions. It counts card-not-present only, and a single disputed transaction can count twice — once as a TC40 fraud alert and once as a TC15 dispute — which is why your acquirer's number is usually higher than your internal dashboard shows. Mastercard's ECP works differently: current-month chargebacks over prior-month transactions, chargebacks only. The kit computes each network separately, because a blended figure hides which network is actually your exposure.

Visa excludes merchants with fewer than 1,500 combined fraud-and-dispute events per month from VAMP monitoring; Mastercard's program needs 100+ disputes. So a small storefront can run a ratio above the threshold and still not be enrolled, because the network isn't counting it yet. The kit flags that account 'below monitoring floor' rather than reading it OVER THE LINE — but it's a warning, not an all-clear: the month you cross the floor while over the ratio, you flip straight to OVER THE LINE.

No — and that's the whole point of the design. Prevention is scored as a separate read (HARDENED / SOFT / EXPOSED) and it never averages into the ratio verdict. You can have every control in place and still be OVER THE LINE, because your controls reduce how many disputes you get going forward but can't remove one that's already been counted. The shipped sample makes this concrete: the Main storefront scores a perfect 100 / HARDENED on prevention and still reads OVER THE LINE on a 1.58% Visa ratio. Believe the ratio.

Not instantly. To exit a monitoring program you have to stay under the threshold for three consecutive months, and a single spike resets the clock. That's why the fix-first for an over-the-line account is always the fastest way to cut counted events right now — turn on pre-dispute deflection and refund flagged orders — rather than fighting disputes after they've posted. Run the kit monthly so you catch an approaching ratio while headroom is still cheap to protect.