Library · Chargebacks · How to run this
Kount device-mismatch block is not Sift device mismatch
Put device-mismatch blocks over auth attempts in one Kount prevention cut. The quotient is mismatch %.
Pair: Device-mismatch share on Chargebacks. Other stack: Sift device-mismatch. Fingerprint twin: device-fingerprint miss.
What you type
Device-mismatch blocks — Kount hard blocks tagged to device / account mismatch in the cut.
Auth attempts — Auth attempts in that same Kount cut.
Mismatch % = device-mismatch blocks ÷ auth attempts × 100. Fat mismatch % usually means a hot device rule — tune that path; never invent a mismatch chip.
What not to do
Do not invent mismatch %. Do not paste a Sift mismatch export into Kount fields. Do not fold fingerprint misses into mismatch blocks. Do not blend MIDs when one seat owns the skew.
Related: Chargebacks, Sift device-mismatch, device-fingerprint miss, proxy-hit share.
Procedure
- Type device-mismatch blocks and auth attempts.
- Read mismatch %.
- Tune device rules when mismatch % is material.
Failure modes
- Inventing mismatch %.
- Pasting a Sift mismatch export into Kount fields.
- Folding fingerprint misses into mismatch 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
- Device-mismatch share %
- Device-mismatch blocks ÷ Auth attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Sift device-mismatch share?
- Different prevention stack. [Device-mismatch share](/manuals/sift-device-mismatch-share) reads Sift. Here you only put Kount device-mismatch blocks over Kount auth attempts.
- Is this Kount device-fingerprint miss rate?
- Sibling Kount door. [Device-fingerprint miss rate](/manuals/kount-device-fingerprint-miss-rate) is fingerprint misses. This page is hard blocks tagged device-mismatch.
- What mismatch % should I invent?
- None. Pull device-mismatch blocks and auth attempts from the same Kount cut.