Library · Chargebacks · How to run this
Decision latency is not challenge abandon
How far p95 score reply ms sits past your SLA ms is over-SLA %. Over-SLA % = max(0, (p95 − SLA) ÷ SLA × 100). Type both.
Pair: Decision-latency p95 on Chargebacks. Challenge: challenge-abandon rate. Review $: manual review lag.
What you type
p95 score reply ms — 95th-percentile Sift score reply time in the export window.
Your SLA ms — the SLA you hold the score call to in that same window.
Over-SLA % = max(0, (p95 − SLA) ÷ SLA × 100). Trim rules or raise timeout when over-SLA % is fat — do not invent an SLA chip.
What not to do
Do not invent over-SLA %. Do not fold challenge abandons into score reply ms. Do not treat review-queue hours as score latency. Do not blend every MID when one seat owns the spike.
Related: Chargebacks, challenge-abandon rate, manual review lag, auto-block overturn rate.
Procedure
- Type p95 decision ms and timeout ms.
- Read over-threshold %.
- Fix queue / rules when over-threshold % is material.
Failure modes
- Inventing over-threshold %.
- Mixing challenge abandons into p95 ms.
- Treating review lag hours as decision latency.
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
- Decision-latency p95
- max(0, (p95 − timeout) ÷ timeout × 100).
Work with us — We run this job on your accounts. Services
FAQ
- Is this challenge-abandon rate?
- Sibling prevention grain. [Challenge-abandon rate](/manuals/kount-challenge-abandon-rate) is abandons ÷ challenges. This page is how far Sift score reply p95 sits past your SLA.
- Is this manual review lag?
- Related Sift queue $. [Manual review lag](/manuals/sift-manual-review-lag) prices lag × AOV. This page is score-reply over-SLA % only.
- What over-SLA % should I invent?
- None. Type p95 score reply ms and your SLA ms from the same Sift export.