Library · Chargebacks · How to run this
Sift ATO stop rate is not Forter ATO block
Divide ATO stops by auth attempts in one Sift decision cut. That ratio is stop %.
Pair: ATO-block share on Chargebacks. Forter twin: ATO-block. Abuse twin: payment-abuse.
What you type
ATO blocks — Sift account-takeover stops raised in the decision cut.
Auth attempts — Auth attempts in that same Sift decision cut.
Stop % = ATO stops ÷ auth attempts × 100. Fat stop % usually means credential-stuffing heat — retune ATO rules; never invent a stop chip.
What not to do
Skip inventing stop %. Skip dumping a Forter ATO file into Sift fields. Skip treating payment-abuse blocks as ATO stops. Skip blending MIDs when one seat owns the stop pile.
Related: Chargebacks, ATO-block, payment-abuse, auto-block overturn.
Procedure
- Type ATO blocks and auth attempts.
- Read ATO %.
- Retune ATO rules when ATO % is material.
Failure modes
- Inventing ATO %.
- Dumping a Forter ATO file into Sift fields.
- Treating payment-abuse blocks as ATO stops.
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
- ATO-block share %
- ATO blocks ÷ Auth attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Forter ATO-block share?
- Different prevention book. [ATO-block share](/manuals/forter-ato-block-share) reads Forter. Here you only divide Sift ATO stops by auth attempts.
- Is this Sift payment-abuse share?
- Sibling Sift door. [Payment-abuse share](/manuals/sift-payment-abuse-share) is payment-abuse blocks. This page is ATO stops ÷ auth attempts.
- What stop % should I invent?
- None. Pull ATO stops and auth attempts from the same Sift decision cut.