Library · Chargebacks · How to run this
Kount vel-hard block is not Forter velocity block
Divide vel-hard blocks by auth attempts on one Kount velocity cut. That ratio is KT vel-hard %.
Pair: Velocity-block share on Chargebacks. Forter twin: velocity block. Override twin: velocity-override.
What you type
Velocity blocks — Kount hard blocks tagged to velocity rules in the cut.
Auth attempts — Auth attempts in that same Kount velocity cut.
KT vel-hard % = velocity blocks ÷ auth attempts × 100. Fat KT vel-hard % usually means a hot velocity rule — tune that path; never invent a KT vel-hard chip.
What not to do
Skip inventing KT vel-hard %. Skip dumping a Forter velocity-block file into Kount fields. Skip folding velocity-override counts into hard blocks. Skip blending MIDs when one seat owns the spike.
Related: Chargebacks, Forter velocity block, velocity-override, rule false-positive.
Procedure
- Type velocity blocks and auth attempts.
- Read KT vel-hard %.
- Retune velocity rules when KT vel-hard % is material.
Failure modes
- Inventing KT vel-hard %.
- Dumping a Forter velocity-block file into Kount fields.
- Folding Kount velocity-override counts into hard blocks.
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
- KT vel-hard %
- Velocity blocks ÷ Auth attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Forter velocity-block share?
- Different prevention stack. [Velocity-block share](/manuals/forter-velocity-block-share) counts Forter velocity blocks. Here you only divide Kount vel-hard blocks by Kount auth attempts.
- Is this Kount velocity-override share?
- Sibling Kount door on overrides, not hard blocks. [Velocity-override share](/manuals/kount-velocity-override-share) is overrides ÷ decisions. This page is velocity hard blocks ÷ auth attempts.
- What KT vel-hard % should I invent?
- None. Pull velocity blocks and auth attempts from the same Kount velocity cut.