Library · Chargebacks · How to run this
Sift device mismatch is not watchlist hit
Device mismatches ÷ auth attempts is the Sift mismatch %. Type both from one decision window.
Pair: Device-mismatch share on Chargebacks. Watchlist: watchlist-hit share. Fingerprint: device-fingerprint miss rate.
What you type
Device mismatches — Auths where Sift flagged device / account mismatch in the cut.
Auth attempts — Auth attempts in that same Sift cut.
Mismatch % = device mismatches ÷ auth attempts × 100. Fat mismatch % means retune device rules — do not invent a mismatch chip.
What not to do
Do not invent mismatch %. Do not paste watchlist hits into the mismatch field. Do not treat Kount fingerprint misses as Sift mismatches. Do not blend MIDs when one MID owns the skew.
Related: Chargebacks, watchlist-hit share, device-fingerprint miss rate, identity-challenge share.
Procedure
- Type device mismatches and auth attempts.
- Read mismatch %.
- Retune device rules when mismatch % is material.
Failure modes
- Inventing mismatch %.
- Dumping watchlist hits into the mismatch field.
- Treating Kount fingerprint misses as Sift mismatches.
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
- Device-mismatch share %
- Device mismatches ÷ auth attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this watchlist-hit share?
- Different Sift door. [Watchlist-hit share](/manuals/sift-watchlist-hit-share) is list hits. Here you type device mismatches over auth attempts.
- Is this Kount device-fingerprint miss rate?
- Different vendor grain. [Device-fingerprint miss rate](/manuals/kount-device-fingerprint-miss-rate) is fingerprint misses. This page is Sift device-mismatch share.
- What mismatch % should I invent?
- None. Pull device mismatches and auth attempts from the same Sift cut.