Payment Fraud Velocity Rules Card Hour Tool

Audit actual observed per-card transaction velocity in explicit (as-of−lookback, as-of] window under caller inclusive count threshold; labels are pseudonymous caller IDs, threshold flags are review candidates rather than proof of fraud or permission to block.

Description

Transaction velocity counts events within a declared trailing interval for each card ID.

Transaction velocity counts events within a declared trailing interval for each card ID. The interval excludes its lower boundary and includes the as-of time.^[1]

The returned values include Observed window card ids, Observed window transaction counts, Threshold flagged card ids, Counted window transaction indices. The How section below explains the calculation, input rules and interpretation.

When to use Payment Fraud Velocity Rules Card Hour Tool

Use Payment Fraud Velocity Rules Card Hour Tool when you need to evaluate the supplied records under the calculation and evidence rules below. No proof of fraud, blocking permission or universal one-hour threshold is supplied.

Prepare observed financial records and verified caller terms. Use one currency for integer minor-unit money and preserve leading zeros in identifier text. One basis point is 0.01 percentage points. Resolve dates, local clocks, counting rules and evidence flags as specified.

How to use Payment Fraud Velocity Rules Card Hour Tool and understand its results

Prepare observed financial records and verified caller terms. Use one currency for integer minor-unit money and preserve leading zeros in identifier text. One basis point is 0.01 percentage points. Resolve dates, local clocks, counting rules and evidence flags as specified.
Enter observedCardIds, transactionMinutes, asOfMinute, callerLookbackMinutes, callerInclusiveCountThreshold using the field table and calculation rules, then run the tool.
Read observedWindowCardIds, observedWindowTransactionCounts, thresholdFlaggedCardIds, countedWindowTransactionIndices. The explanation below defines the units, signs, ordering and any flags or placeholder values.
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 field	Meaning	Value type; see rules below	Requirement
observedCardIds	Observed card ids	list of string	Required
transactionMinutes	Transaction minutes	list of number	Required
asOfMinute	As of minute	number	Required
callerLookbackMinutes	Caller lookback minutes	number	Required
callerInclusiveCountThreshold	Caller inclusive count threshold	number	Required

Enter aligned nonempty nonblank pseudonymous card IDs and nonnegative safe-integer nondecreasing event minutes no later than a safe-integer as-of minute. Enter integer lookback 1–10080 and threshold 1–10000. Return cards in first counted appearance order, counts, inclusively flagged IDs and zero-based counted event indexes. Repeated IDs are allowed.

window=(asOf−lookback,asOf]; flagCard when count≥threshold

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

Output field	Meaning	Value type
observedWindowCardIds	Observed window card ids	list of string
observedWindowTransactionCounts	Observed window transaction counts	list of number
thresholdFlaggedCardIds	Threshold flagged card ids	list of string
countedWindowTransactionIndices	Counted window transaction indices	list of number

json

{
  "input": {
    "observedCardIds": [
      "A",
      "A",
      "B",
      "A"
    ],
    "transactionMinutes": [
      0,
      30,
      35,
      60
    ],
    "asOfMinute": 60,
    "callerLookbackMinutes": 60,
    "callerInclusiveCountThreshold": 2
  },
  "output": {
    "observedWindowCardIds": [
      "A",
      "B"
    ],
    "observedWindowTransactionCounts": [
      2,
      1
    ],
    "thresholdFlaggedCardIds": [
      "A"
    ],
    "countedWindowTransactionIndices": [
      1,
      2,
      3
    ]
  }
}

Limitations and assumptions

No proof of fraud, blocking permission or universal one-hour threshold is supplied.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Alert Backlog Aging Checker: Backlog aging reviews unresolved alerts against a caller threshold. An absent unresolved subset needs an explicit unavailable oldest age. For a complementary task, use Positive Pay Issue Mismatch Checker: Positive-pay matching compares check ID, amount and payee against the issue ledger. Distinct mismatch witnesses explain a failed aggregate match.

References

Payment Fraud Velocity Rules Card Hour Tool — tool.io

Similar or alternative tools

Alert Backlog Aging Checker
Backlog aging reviews unresolved alerts against a caller threshold. An absent unresolved subset needs an explicit unavailable oldest age.
Positive Pay Issue Mismatch Checker
Positive-pay matching compares check ID, amount and payee against the issue ledger. Distinct mismatch witnesses explain a failed aggregate match.