Library · Chargebacks · How to run this
Forter identity challenge is not ATO block
Open one Forter cut. Put identity challenges over auth attempts. That is the challenge %.
Pair: Identity-challenge share on Chargebacks. ATO: ATO-block share. Mix: step-up vs block mix.
What you type
Identity challenges — Forter identity / verify challenges raised in the cut.
Auth attempts — Auth attempts in that same Forter cut.
Challenge % = identity challenges ÷ auth attempts × 100. When challenge % is fat, retune identity rules — never type a fake challenge %.
What not to do
Skip inventing a challenge %. Skip dumping ATO blocks into the challenge field. Skip treating Kount abandons as Forter challenges. Skip blending MIDs when one MID owns the skew.
Related: Chargebacks, ATO-block share, step-up vs block mix, challenge-abandon rate.
Procedure
- Type identity challenges and auth attempts.
- Read challenge %.
- Retune identity rules when challenge % is material.
Failure modes
- Inventing challenge %.
- Dumping ATO blocks into the challenge field.
- Treating Kount abandons as Forter challenges.
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
- Identity-challenge share %
- Identity challenges ÷ auth attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this ATO-block share?
- Different Forter door. [ATO-block share](/manuals/forter-ato-block-share) is hard ATO blocks. Here you type identity challenges over auth attempts.
- Is this Kount challenge-abandon rate?
- Different vendor grain. [Challenge-abandon rate](/manuals/kount-challenge-abandon-rate) is abandons ÷ challenges. This page is Forter identity-challenge share.
- What challenge % should I invent?
- None. Pull identity challenges and auth attempts from the same Forter cut.