Structuring Pattern Flag Checker
Screen actual caller linked ledger for repeated sub-ceiling aggregate review pattern, does not infer intent, criminal structuring or evasion; no advice on avoiding reports. Caller independently verifies edition, jurisdiction, applicability and one currency; screening does not establish legal compliance, coverage or bank approval.
Description
A transaction-pattern screen depends on verified grouping and explicit review thresholds.
A transaction-pattern screen depends on verified grouping and explicit review thresholds.1
A review flag is a prompt for assessment rather than proof of unlawful structuring or intent. Use Structuring Pattern Flag Checker to evaluate the supplied inputs under the model explained below.
When to use Structuring Pattern Flag Checker
Use Structuring Pattern Flag Checker to evaluate the supplied inputs under the model explained below. Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
How to use Structuring Pattern Flag Checker and understand its results
- Establish the currency and minor-unit convention, measurement period and applicable transaction or institution context.
- Enter Observed transaction minor, Observed caller linked group ids, Caller single transaction ceiling minor, Caller aggregate review floor minor, Caller minimum linked count using the field table and validation rules below, then run the tool.
- Read Pattern review group ids, Review group aggregate minor; interpret the units, signs, ordering and unknown-value placeholders described below.
- Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| observedTransactionMinor | Observed transaction minor | array of number | Required; constraints below |
| observedCallerLinkedGroupIds | Observed caller linked group ids | array of string | Required; constraints below |
| callerSingleTransactionCeilingMinor | Caller single transaction ceiling minor | number | Required; constraints below |
| callerAggregateReviewFloorMinor | Caller aggregate review floor minor | number | Required; constraints below |
| callerMinimumLinkedCount | Caller minimum linked count | number | Required; constraints below |
Enter aligned nonempty nonnegative integer transaction amounts no greater than 1000000000000 and nonblank exact linked-group IDs of at most 128 UTF-16 code units. Supply ceiling and aggregate floor in the same monetary range and an integer minimum linked count from 2 to 128. For each group require enough records, every individual amount strictly below ceiling and aggregate at least floor. Return review-group IDs and aligned totals in first-appearance order. The caller establishes linkage and thresholds; a screen does not establish intent, file a report or infer related parties.
review(group)=count≥minimum and every amount<ceiling and sum≥aggregateFloor Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| patternReviewGroupIds | Pattern review group ids | array of string |
| reviewGroupAggregateMinor | Review group aggregate minor | array of number |
{
"input": {
"observedTransactionMinor": [
400,
400,
400
],
"observedCallerLinkedGroupIds": [
"a",
"a",
"a"
],
"callerSingleTransactionCeilingMinor": 500,
"callerAggregateReviewFloorMinor": 1000,
"callerMinimumLinkedCount": 3
},
"output": {
"patternReviewGroupIds": [
"a"
],
"reviewGroupAggregateMinor": [
1200
]
}
}Limitations and assumptions
A review flag is a prompt for assessment rather than proof of unlawful structuring or intent. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use Wire Recall Gpi Stop and Recall Success Realities Note for a related task: A wire-recall request and reversal of a completed transfer are different events.
Use Zelle Scams Versus Frauds Reimbursement Policy Debate Lookup for a related task: A scam-induced authorized payment and an unauthorized transfer raise different fact and policy questions.
References
-
Structuring Pattern Flag Checker — tool.io
Similar or alternative tools
- Wire Recall Gpi Stop and Recall Success Realities Note
A wire-recall request and reversal of a completed transfer are different events.
- Zelle Scams Versus Frauds Reimbursement Policy Debate Lookup
A scam-induced authorized payment and an unauthorized transfer raise different fact and policy questions.