Assess whether the typology is bust-out, first-party, or third-party (6695ae)
August 31, 2026
SITUATION Synthetic-identity detection manager in a fintech that just hit $2B payments volume has one working extract — first-party friendly-fraud dispute pack — after a customer calling to reverse a 'authorized' card charge. If first-party friendly-fraud dispute pack cannot support the typology is bust-out,, the only defensible Fraud Detection output is hold.
DECISION Synthetic-identity detection manager in a fintech that just hit $2B payments volume must choose The typology is bust-out, first-party, / Third-party using first-party friendly-fraud dispute pack after a customer calling to reverse a 'authorized' card charge.
HYPOTHESES TO TEST 1. A customer calling to reverse a 'authorized' card charge is noise around an already-controlled Credit and Identity Fraud process in a fintech that just hit $2B payments volume, given first-party friendly-fraud dispute pack. 2. A customer calling to reverse a 'authorized' card charge is the event in first-party friendly-fraud dispute pack that forces The typology is bust-out, first-party, for synthetic-identity detection manager under Fraud Detection. 3. First-party friendly-fraud dispute pack shows a one-file miss after a customer calling to reverse a 'authorized' card charge, not a Credit and Identity Fraud program failure. 4. First-party friendly-fraud dispute pack cannot decide the typology is bust-out, yet after a customer calling to reverse a 'authorized' card charge; hold is the only Fraud Detection close a fintech that just hit $2B payments volume can defend.
ANALYSIS REQUIRED 1. Trace funds, counterparties, and reversals in first-party friendly-fraud dispute pack through the window opened by a customer calling to reverse a 'authorized' card charge. 2. Quantify loss if the hold is released before first-party friendly-fraud dispute pack is complete. 3. Test a one-off dispute against the first edge of a scheme around the typology is bust-out,. 4. For this Fraud Detection Credit and Identity Fraud file, read first-party friendly-fraud dispute pack against a customer calling to reverse a 'authorized' card charge and write the one fact that would move the typology is bust-out, for synthetic-identity detection manager.
RECOMMENDATION Choose The typology is bust-out, first-party, / Third-party on this Fraud Detection / Credit and Identity Fraud packet (first-party friendly-fraud dispute pack after a customer calling to reverse a 'authorized' card charge). If first-party friendly-fraud dispute pack cannot force a Fraud Detection label under Credit and Identity Fraud, stop. Do not invent missing evidence a fintech that just hit $2B payments volume does not have.
COMMAND RETURNS - Bottom-line Fraud Detection option on the typology is bust-out,, then the evidence in first-party friendly-fraud dispute pack, then the action for synthetic-identity detection manager - Hypothesis scorecard against first-party friendly-fraud dispute pack: supported / rejected / untestable - Credit and Identity Fraud finding in first-party friendly-fraud dispute pack that a second reviewer can re-perform - Missing page in first-party friendly-fraud dispute pack after a customer calling to reverse a 'authorized' card charge, if any
Explore more
More Fraud Detection prompts
- Account-opening quality reviewer must resolve whether a payment hold survives
- Assess whether the typology is bust-out, first-party, or third-party (b1bf2f)
- Whether to refer to law enforcement or keep civil from first-party
- Whether a SAR narrative is supportable today from straw-buyer occupancy file
- Whether linked accounts should be treated as one case from mule-account
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.

