Assess whether to refer to law enforcement or keep civil after a customer
August 31, 2026
SITUATION Credit and Identity Fraud work in a mortgage correspondent channel now turns on to refer to law because a customer calling to reverse a 'authorized' card charge put synthetic identity application cluster in play. Payments-risk officer should say what synthetic identity application cluster proves.
DECISION Payments-risk officer in a mortgage correspondent channel must choose To refer to law enforcement / Keep civil using synthetic identity application cluster after a customer calling to reverse a 'authorized' card charge.
HYPOTHESES TO TEST 1. Authorize To refer to law enforcement now; synthetic identity application cluster already has the discriminator after a customer calling to reverse a 'authorized' card charge. 2. Keep Keep civil in force until synthetic identity application cluster is completed after a customer calling to reverse a 'authorized' card charge for payments-risk officer. 3. Treat synthetic identity application cluster as To refer to law enforcement because both readings appear after a customer calling to reverse a 'authorized' card charge. 4. Refuse a Fraud Detection close: payments-risk officer does not have the decision to refer to law turns on in synthetic identity application cluster.
ANALYSIS REQUIRED 1. Trace funds, counterparties, and reversals in synthetic identity application cluster through the window opened by a customer calling to reverse a 'authorized' card charge. 2. Quantify loss if the hold is released before synthetic identity application cluster 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 Credit and Identity Fraud file, read synthetic identity application cluster against a customer calling to reverse a 'authorized' card charge and write the one fact that would move to refer to law for payments-risk officer.
RECOMMENDATION Choose To refer to law enforcement / Keep civil on this Fraud Detection / Credit and Identity Fraud packet (synthetic identity application cluster after a customer calling to reverse a 'authorized' card charge). If synthetic identity application cluster cannot force a Fraud Detection label under Credit and Identity Fraud, stop. If synthetic identity application cluster after a customer calling to reverse a 'authorized' card charge cannot support To refer to law enforcement versus Keep civil on this Fraud Detection Credit and Identity Fraud close, payments-risk officer 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 synthetic identity application cluster, then the action for payments-risk officer - Hypothesis scorecard against synthetic identity application cluster: supported / rejected / untestable - Missing page in synthetic identity application cluster after a customer calling to reverse a 'authorized' card charge, if any - Regulatory or exam hook Credit and Identity Fraud would cite
Explore more
More Fraud Detection prompts
- SIU investigator must resolve whether linked accounts should be treated as
- Assess whether a SAR narrative is supportable today after a customer calling
- Card-issuing fraud analyst must resolve whether a claims ring exists
- Whether a SAR narrative is supportable today from check-kiting multi-bank
- Assess whether a SAR narrative is supportable today from account-takeover
Explore related decision areas
- Assess whether bonus triggers were gamed by cutoff (e272f6)Forensic Accounting
- Assess whether cyber controls claimed are actually in force after a brokerInsurance Underwriting
- Assess whether to quote, refer, or decline (67d6f6)Insurance Underwriting
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.

