The Outlier Lab

Fraud Risk Assessment

How to run a product- and flow-level transaction fraud risk assessment: scheme inventory by money path, likelihood × impact scoring, control evaluation, residual risk, and appetite-based action.

Core components

The money path as the unit of assessment

Assess at the level where decisions happen. A money path is a specific way value enters, moves or leaves:

  • Money in: card funding, ACH funding, check deposit, wire in, P2P receive, ACATS in, receipt or offer submission, purchase
  • Money moves: trades, internal transfers, reward accrual, balance conversion
  • Money out: withdrawal by rail, payout to card or wallet, P2P send, reward redemption, refund, gift card cash-out, ACATS out

Use the Payment Rails Map and Customer Lifecycle Map to build the list. Product-level assessments roll up from money paths.

Steps

Diagram: 1. Scope money paths, 2. Identify schemes per path, 3. Rate inherent risk (L x I), 4. Map & test controls, 5. Rate residual risk, 6. Within appetite?, Monitor, Action plan or formal acceptance
  1. Scope. List money paths, volumes, values and customer segments.
  2. Identify schemes. For each path, list relevant mechanisms by actor type: third-party, first-party, organized ring, insider, victim-authorized (see the vault's mechanism notes and Mechanism to Control Matrix).
  3. Rate inherent risk (before controls): likelihood × impact.
  4. Map controls to each scheme, and assess design and operating effectiveness.
  5. Rate residual risk after controls.
  6. Compare to appetite. Act, accept or monitor.

How to build it

Rating scales (illustrative, calibrate to your organization)

Likelihood

ScoreLabelGuidance
5Almost certainActively seen against us now, or against close peers on the same rail
4LikelySeen against us in the last 12 months, or widely reported in our sector
3PossibleKnown in industry; we have the exposure; not seen recently
2UnlikelyPlausible, but requires unusual capability or access
1RareTheoretical for our product

Impact. Score the highest applicable dimension.

ScoreFinancial (per year, illustrative)Customer harmRegulatory / partnerReputational
5Above X% of annual fraud budgetWidespread loss of customer fundsEnforcement or partner termination likelyNational press
4LargeSignificant losses to many customersFormal partner or regulator actionTrade press, viral social
3ModerateLosses to some customers, remediablePartner warning, monitoring programLocalized complaints
2MinorInconvenienceInquiryMinimal
1NegligibleNoneNoneNone

Inherent risk = likelihood × impact (1–25). Bands: 15–25 high, 8–14 medium, 1–7 low.

Control effectiveness

RatingMeaning
StrongDesigned for the scheme; tested; operating as designed; monitored with metrics
AdequateDesigned for the scheme; operating, with minor gaps; some monitoring
WeakPartially addresses the scheme, or untested, or known gaps
NoneNo control specifically addresses the scheme

COSO's three-part test is a good discipline. Identify the controls tied to each inherent risk. Confirm they are implemented and working as designed. Judge whether they're adequate for the risk. Evidence for "operating as designed" can come from QA results, rule performance reviews, model monitoring, incident history and sample testing.

Residual risk

A simple matrix:

Inherent \ ControlStrongAdequateWeakNone
HighMediumMedium–HighHighHigh
MediumLowMediumMedium–HighHigh
LowLowLowLow–MediumMedium

Appetite and action

ResidualDefault action
HighAction plan with owner and date; or formal acceptance by the executive risk owner, with rationale and a review date
MediumAction plan or acceptance; monitor KRIs
LowMonitor; reassess at the next cycle

Express appetite in measurable terms where possible: net loss bps by money path, maximum single-event exposure, maximum good-customer friction rate. See Fraud Metrics and KPIs.

Cadence and triggers

Who does what

StepFraud strategyProduct ownerFraud opsAnalyticsCompliance / 2LExec risk owner
ScopeA/RCCCI
Scheme identificationA/RCRCC
Likelihood and impactA/RCCRC (challenge)
Control mapping and testingA/RCRRC
Residual ratingA/RCC (challenge)I
Acceptance of residual riskCRCA
Action plansARRRII

Artifacts and templates

Risk register columns (copy)

ColumnExample
Risk IDFRA-WD-03
Money pathWithdrawals: instant push-to-card
MechanismPayout Redirection following Account Takeover (ATO)
ActorThird-party
ScenarioAttacker gains account access, adds a new debit card, withdraws the balance instantly
Likelihood (1–5)4
Impact (1–5)4
Inherent16 (high)
ControlsStep-up on new payout instrument; cooling-off after contact change; withdrawal scoring
Control ratingAdequate
EvidenceRule review Q3; QA results; incident history
ResidualMedium–High
Appetite statusOutside appetite
Action / acceptanceAdd a hold on first push-to-card withdrawal to a new instrument for accounts with recent changes; owner; date
KRIsLoss bps on instant withdrawals; share of withdrawals within N days of a contact change
Next reviewDate

Scheme identification prompts per money path

  • Who could misuse it: outsider with stolen credentials or instruments, the account holder, a ring, an employee, a deceived customer?
  • What reversibility gap exists between when we give value and when inbound funds are final?
  • What multiplies: accounts, devices, instruments, identities, referrals, receipts?
  • What changes right before money-out: contact details, devices, payout destinations?
  • What can support override?
  • What has happened to peers on the same rail or product type?

Assessment report outline

  1. Scope and method
  2. Heat map: residual risk by money path × mechanism
  3. Top 10 residual risks with actions or acceptances
  4. Changes since the last assessment
  5. Control gaps by family (see Controls Index)
  6. Emerging risks to watch
  7. Sign-offs

Metrics

MetricWhy
Money paths with a current assessment (within 12 months)Coverage
High residual risks without an action plan or acceptanceGovernance gap
Action plans past dueExecution
Incidents on risks rated lowCalibration check: was the assessment wrong?
Time from trigger to reassessmentResponsiveness

Pitfalls

  • Company-level ratings. "Fraud risk: medium" is useless. Assess money paths.
  • Inherent risk inflated to justify budget, or deflated to avoid work. Calibrate with a second reviewer (see Three Lines of Defense).
  • Control ratings without evidence. "We have a rule" isn't "the rule works." Use QA and performance data.
  • Ignoring first-party and victim-authorized actors. Many assessments only model outside attackers.
  • The annual binder. The risk register goes unopened between refreshes. Connect it to launch review and intel triggers.
  • Acceptance without a name. Every accepted residual risk needs an owner senior enough to own it, and a review date.

Sources and further reading