Notifications
Clear all
Topic starter
19/08/2026 3:24 pm
TL;DR: Fraud teams are being pushed to justify their work in revenue, conversion, and customer experience terms rather than loss prevention alone, according to Sift’s Blueprint session. The shift matters because fraud now influences growth decisions, cross-functional planning, and the way organisations allocate budget and headcount.
NHIMG editorial — based on content published by Sift: How Fraud Teams Can Have a Seat at the Revenue Table
By the numbers:
- The average person now has 200+ apps on their phone, which expands identity-touching entry points and increases the fraud attack surface.
Questions worth separating out
Q: How should fraud teams prove their value to leadership?
A: They should show how fraud controls affect revenue, customer experience, and operating cost, not just losses blocked.
Q: Why do fraud and identity teams need shared context?
A: Because fraud decisions depend on whether an identity, account, or session is trusted across multiple touchpoints.
Q: What do organisations get wrong about fraud metrics?
A: They often report only blocks, chargebacks, and losses prevented, which tells leadership what was stopped but not what was enabled.
Practitioner guidance
- Reframe fraud reporting in business terms Translate one core fraud metric into revenue, conversion, or customer experience language before the next executive review.
- Create a shared signal model with adjacent teams Work with support, payments, product, and finance to share the identity and behaviour signals that influence approval decisions.
- Tie fraud controls to joint OKRs Set at least one joint objective with another business function so fraud success contributes to a second team’s outcome, such as turnaround time or conversion.
What's in the full article
Sift's full article covers the operational detail this post intentionally leaves for the source:
- The specific cross-functional OKR examples that show how fraud teams can align with growth, support, and finance.
- The session discussion points behind the revenue-table framing, including the language executives are most likely to respond to.
- The practical ways fraud leaders can translate loss prevention into protected revenue and reduced customer friction.
- The audience polling detail on where fraud should sit organisationally and why reporting line matters less than rapport.
👉 Read Sift’s analysis of how fraud teams can tie prevention work to revenue outcomes →
Fraud measurement is shifting to revenue impact, not blocks?
Explore further
19/08/2026 4:09 pm
Fraud governance is becoming identity governance by another name. The article shows that fraud teams are now expected to manage trust decisions across onboarding, login, payment, and customer support. Those are identity questions, not just fraud questions, because every approval and rejection depends on how a person or account is verified in context. Practitioners should stop treating fraud as a separate metric silo and start governing it as part of the identity decision chain.
A question worth separating out:
Q: Who should own fraud outcomes inside the business?
A: Fraud ownership should sit with the team that can coordinate decisions across support, product, payments, finance, and security. The reporting line matters less than whether the programme has enough cross-functional authority to share signals and reduce friction. A mature fraud model behaves like a trust function, not a siloed review desk.
👉 Read our full editorial: Fraud teams need revenue metrics, not just loss prevention
