Assess whether linked accounts should be treated as one case after a new

SITUATION In a credit-card issuer during a holiday-authorization spike, ACH return-reason code R10 spike is the evidence after a new device from a different metro on a 2am login. Account-opening quality reviewer has to pick Remove access or reverse the item or Temporary compensating control for this Fraud Detection Credit and Identity Fraud close using ACH return-reason code R10 spike.

DECISION Account-opening quality reviewer in a credit-card issuer during a holiday-authorization spike must choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold using ACH return-reason code R10 spike after a new device from a different metro on a 2am login.

HYPOTHESES TO TEST 1. Authorize Remove access or reverse the item now; ACH return-reason code R10 spike already has the discriminator after a new device from a different metro on a 2am login. 2. Keep Temporary compensating control in force until ACH return-reason code R10 spike is completed after a new device from a different metro on a 2am login for account-opening quality reviewer. 3. Treat ACH return-reason code R10 spike as Approve a documented exception because both readings appear after a new device from a different metro on a 2am login. 4. Refuse a Fraud Detection close: account-opening quality reviewer does not have the decision linked accounts should be turns on in ACH return-reason code R10 spike.

ANALYSIS REQUIRED 1. Quantify loss if the hold is released before ACH return-reason code R10 spike is complete. 2. Test a one-off dispute against the first edge of a scheme around linked accounts should be. 3. Check mule or round-trip markers in ACH return-reason code R10 spike. 4. For this Fraud Detection Credit and Identity Fraud file, read ACH return-reason code R10 spike against a new device from a different metro on a 2am login and write the one fact that would move linked accounts should be for account-opening quality reviewer.

RECOMMENDATION Choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold on this Fraud Detection / Credit and Identity Fraud packet (ACH return-reason code R10 spike after a new device from a different metro on a 2am login). The follow-on Credit and Identity Fraud action is what account-opening quality reviewer does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Fraud Detection option on linked accounts should be, then the evidence in ACH return-reason code R10 spike, then the action for account-opening quality reviewer - Hypothesis scorecard against ACH return-reason code R10 spike: supported / rejected / untestable - Credit and Identity Fraud finding in ACH return-reason code R10 spike that a second reviewer can re-perform - Missing page in ACH return-reason code R10 spike after a new device from a different metro on a 2am login, if any