Transfer-Fraud Screen

Screen payment facts for funds-transfer fraud and response urgency.

Description

A transfer-fraud screen combines supplied payment indicators with verification and recovery flags.

A transfer-fraud screen combines supplied payment indicators with verification and recovery flags. A transferred payment determines incident status before the score threshold.1

Screen payment facts for funds-transfer fraud and response urgency.

When to use Transfer-Fraud Screen

Use this tool to screen payment facts for funds-transfer fraud and response urgency.

Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.

How to use Transfer-Fraud Screen and understand its results

  1. Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
  2. Enter executiveImpersonation, paymentInstructionChanged, outOfBandVerified, fundsTransferred, recoveryAttempted using the field table and calculation rules, then run the tool.
  3. Read riskScore, status, urgentAction. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
Input fieldMeaningValue type; see rules belowRequirement
executiveImpersonationExecutive impersonationbooleanRequired
paymentInstructionChangedPayment instructions changedbooleanRequired
outOfBandVerifiedOut-of-band verification completedbooleanRequired
fundsTransferredFunds transferredbooleanRequired
recoveryAttemptedRecovery attemptedbooleanRequired

Enter five booleans. Return score, status and urgent flag. Transferred funds yield incident-response if recovery was attempted, otherwise incident and urgentAction=true. Without transfer, score≥3 labels blocked, otherwise low-risk.

score=max(0,3impersonation+2changedInstruction+3transferred−3verified−recoveryAttempted)

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output fieldMeaningValue type
riskScoreTransfer-fraud risk scoreinteger; minimum: 0
statusTransfer-fraud statusstring; one of "low-risk", "blocked", "incident", "incident-response"
urgentActionUrgent action recommendedboolean
json
{
  "input": {
    "executiveImpersonation": true,
    "paymentInstructionChanged": true,
    "outOfBandVerified": false,
    "fundsTransferred": true,
    "recoveryAttempted": false
  },
  "output": {
    "riskScore": 8,
    "status": "incident",
    "urgentAction": true
  }
}

Limitations and assumptions

No fraud is detected, payment blocked, bank contacted or funds recovered. Status labels are heuristic outputs.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.

Alternative or Complementary methods

Use Social Engineering Coverage Gap: Compare caller-supplied expected and observed records for social engineering coverage gap. For a complementary task, use Rescission Screen: Screen supplied application and claim facts for rescission review.

References

  1. Transfer-Fraud Screen — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies