TL;DR: Chargeback losses at two luxury brands that paused in-store fraud reviews rose to $1.3M+ and $800K+ within six months, then returned to near zero after protection was reinstated, according to Riskified. The lesson for practitioners is that suppressed fraud can look invisible until controls are removed, at which point the operational and financial exposure becomes measurable fast.
NHIMG editorial — based on content published by Riskified: in-store fraud protection and chargeback losses in leased-register retail
By the numbers:
- Brand B saw more than $800K in chargeback losses over six months after fraud protection was paused.
- Brand A achieved a reported 1600% ROI from reinstated fraud protection.
- Brand B achieved a reported 600% ROI from reinstated fraud protection.
Questions worth separating out
Q: What breaks when in-store fraud review is removed from a leased-register model?
A: When in-store fraud review is removed, suspicious transactions pass through the same checkout flow that would normally suppress them, so chargebacks become the first visible signal of risk.
Q: Why can low in-store fraud loss rates be misleading for merchants?
A: Low loss rates can simply mean the fraud control is working well enough that the merchant never sees the avoided cases.
Q: How do security teams know whether a fraud control is actually working?
A: A fraud control is working when prevented loss, avoided chargebacks, and reduced dispute volume move in the right direction together, while legitimate approval rates remain stable.
Practitioner guidance
- Model the cost of removing fraud reviews Run a counterfactual analysis using historical approvals, previously declined transactions, and known fraud patterns so business owners can see projected chargeback exposure before any control is paused.
- Separate loss ownership from checkout ownership Define which party owns dispute handling, reimbursement, and escalation in leased-register or franchise-style operating models so no team assumes another control layer is absorbing the risk.
- Track suppressed fraud as a governance metric Report blocked transactions, avoided chargebacks, and dispute workload alongside realised losses so leadership sees the full effect of fraud controls rather than only the residual incidents.
What's in the full article
Riskified's full article covers the operational detail this post intentionally leaves for the source:
- Individual brand-level projections showing expected chargeback costs if in-store fraud protection is removed
- The leasing-model decision point that shifted fraud protection cost from the host retailer to partner brands
- The post-reinstatement comparison between protected and unprotected periods, including the before-and-after loss pattern
- The commercial framing of how the chargeback guarantee affects who bears the loss and who manages disputes
👉 Read Riskified’s analysis of in-store fraud protection and chargeback losses →
In-store fraud protection and chargeback guarantees: what changed?
Explore further
Visible loss is a poor proxy for fraud exposure: when a control works, it suppresses the very evidence teams use to judge whether it is needed. That makes in-store fraud look smaller than it is, especially where card-present assumptions and network protections create a false sense of safety. Practitioners should treat blocked transactions and forecasted loss as core governance inputs, not secondary metrics.
A question worth separating out:
Q: Who is accountable when partner brands opt out of in-store fraud protection?
A: Accountability belongs to whichever party owns the financial loss, dispute process, and decision rights in the operating model. If the host retailer controls the register environment but the brand chooses whether to fund protection, both sides need explicit ownership for reviews, chargebacks, and exception handling before the control is changed.
👉 Read our full editorial: In-store fraud protection is a visibility problem, not a checkout problem