Assess whether to refer to law enforcement or keep civil (eb485e)
August 31, 2026
SITUATION A fintech that just hit $2B payments volume cannot treat a mule account receiving 14 unrelated payrolls in a week as incidental context on account-takeover device-fingerprint graph. Card-issuing fraud analyst must close to refer to law from that extract under Fraud Detection / Claims and Benefits Fraud.
DECISION Card-issuing fraud analyst in a fintech that just hit $2B payments volume must choose To refer to law enforcement / Keep civil using account-takeover device-fingerprint graph after a mule account receiving 14 unrelated payrolls in a week.
HYPOTHESES TO TEST 1. Authorize To refer to law enforcement now; account-takeover device-fingerprint graph already has the discriminator after a mule account receiving 14 unrelated payrolls in a week. 2. Keep Keep civil in force until account-takeover device-fingerprint graph is completed after a mule account receiving 14 unrelated payrolls in a week for card-issuing fraud analyst. 3. Treat account-takeover device-fingerprint graph as To refer to law enforcement because both readings appear after a mule account receiving 14 unrelated payrolls in a week. 4. Refuse a Fraud Detection close: card-issuing fraud analyst does not have the decision to refer to law turns on in account-takeover device-fingerprint graph.
ANALYSIS REQUIRED 1. Trace funds, counterparties, and reversals in account-takeover device-fingerprint graph through the window opened by a mule account receiving 14 unrelated payrolls in a week. 2. Quantify loss if the hold is released before account-takeover device-fingerprint graph is complete. 3. Test a one-off dispute against the first edge of a scheme around to refer to law. 4. For this Fraud Detection Claims and Benefits Fraud file, read account-takeover device-fingerprint graph against a mule account receiving 14 unrelated payrolls in a week and write the one fact that would move to refer to law for card-issuing fraud analyst.
RECOMMENDATION Choose To refer to law enforcement / Keep civil on this Fraud Detection / Claims and Benefits Fraud packet (account-takeover device-fingerprint graph after a mule account receiving 14 unrelated payrolls in a week). If account-takeover device-fingerprint graph cannot force a Fraud Detection label under Claims and Benefits Fraud, stop. If account-takeover device-fingerprint graph after a mule account receiving 14 unrelated payrolls in a week cannot support To refer to law enforcement versus Keep civil on this Fraud Detection Claims and Benefits Fraud close, card-issuing fraud analyst must do not infer a control or scheme beyond the transaction and entitlement evidence.
COMMAND RETURNS - Bottom-line Fraud Detection option on to refer to law, then the evidence in account-takeover device-fingerprint graph, then the action for card-issuing fraud analyst - Hypothesis scorecard against account-takeover device-fingerprint graph: supported / rejected / untestable - Missing page in account-takeover device-fingerprint graph after a mule account receiving 14 unrelated payrolls in a week, if any - Regulatory or exam hook Claims and Benefits Fraud would cite
Explore more
More Fraud Detection prompts
- Assess whether occupancy was misrepresented at origination (c88355)
- Assess whether to refer to law enforcement or keep civil (949fe6)
- Assess whether occupancy was misrepresented at origination (98be94)
- Assess whether to freeze, monitor, or close the account (389248)
- Assess whether a payment hold survives a customer complaint (c0804a)
Explore related decision areas
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

