Library · Chargebacks · How to run this
Forter velocity block is not ATO block
From one Forter prevention cut, divide velocity blocks by auth attempts. That ratio is block %.
Pair: Velocity-block share on Chargebacks. ATO twin: ATO-block share. Other stack: Kount velocity-override.
What you type
Velocity blocks — Forter hard blocks tagged to velocity rules in the cut.
Auth attempts — Auth attempts in that same Forter cut.
Block % = velocity blocks ÷ auth attempts × 100. Fat block % usually means a hot velocity rule — tune that path; never invent a block chip.
What not to do
Never invent block %. Never fold ATO blocks into velocity counts. Never paste a Kount override export into Forter fields. Never blend MIDs when one seat owns the spike.
Related: Chargebacks, ATO-block share, step-up vs block mix, Kount velocity-override.
Procedure
- Type velocity blocks and auth attempts.
- Read block %.
- Tune velocity rules when block % is material.
Failure modes
- Inventing block %.
- Folding ATO blocks into velocity counts.
- Pasting a Kount override export into Forter fields.
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
- Velocity-block share %
- Velocity blocks ÷ Auth attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this ATO-block share?
- Sibling Forter door. [ATO-block share](/manuals/forter-ato-block-share) is account-takeover blocks. This page is velocity-rule hard blocks ÷ auth attempts.
- Is this Kount velocity-override share?
- Different prevention stack. [Velocity-override share](/manuals/kount-velocity-override-share) reads Kount. Here you only count Forter velocity blocks.
- What block % should I invent?
- None. Use velocity blocks and auth attempts from the same Forter cut.