Alert · reviewed · open
The entity's first transfer, $704.16, above the program median, came 0.0 hours after verification.
- Detector
- rapid_onboarding
- Severity
- medium
- Program
- Harbor Marketplace Payouts (simulated)
- Subject
- transfer acht_sim_harb_29xx9l9b40n
- Transfer
- acht_sim_harb_29xx9l9b40n · $704.16 · ach outgoing
- Skoor at alert
- null unscored
- Hard signal
- no
- Policy
- policy-v1
- Opened
- 2026-09-17 19:30Z
- Closed
- —
- Decision clock
- none · due — no clock
- Escalated
- —
Draft narrative
What happened. Alert 5d5ec952-502e-4704-9ddd-0468ba3405f8 fired on rapid_onboarding logic for transfer acht_sim_harb_29xx9l9b40n, an outgoing ACH debit of $704.16 from entity Juniper LLC 121 under the Harbor Marketplace Payouts program. The detector flagged that this was the entity's first transfer, occurring 0.0 hours after verification, and that the amount exceeds the program median of $481.55.
What the evidence shows. The transfer has already settled, with no return code recorded. The entity is a VERIFIED US business with high_risk=false, pep=no, and no review reasons on file; it was last screened 2026-07-01. The alert's own scoring fields are unpopulated: skoor is null, band is unscored, confidence is null, and n=4, indicating a small sample size behind any statistical basis for this detector. The route reason given is 'detector not auto-closable' rather than any substantive risk finding. There are no prior dispositions on this entity or transfer.
What was checked. Reviewed the transfer record (status, amount, return code, counterparty), the entity verification and screening status, the program's declared volume and rails, and the alert's evidence block including scoring fields and threshold configuration. No prior alert history exists for cross-reference.
What is recommended. Close the alert. The transfer has settled cleanly with no return code, the entity is verified with no high-risk or PEP flags and no open review reasons, and the amount above median alone does not establish risk absent a scored model output. The detector's rapid-onboarding logic appears to have triggered on a first transaction pattern common to new legitimate entities rather than on a specific risk indicator. Confidence is limited because the underlying scoring is unpopulated (skoor null, unscored band, n=4), so this reflects the evidence as given rather than a validated risk score.
- Recommendation
- close
- Confidence
- 0.58
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:30Z
- Rationale
- Transfer status is SETTLED with return code none, so no reversible harm is pending and hold/release are not applicable.
- Entity is VERIFIED, high_risk=false, pep=no, with no review reasons and recent screening (2026-07-01).
- Alert scoring fields (skoor, band, confidence) are all null/unscored, and n=4 is a small sample, so the detector's statistical basis is thin.
- No prior dispositions or related alerts exist to suggest a broader pattern warranting escalation.
- The single fact driving the alert -- a first transfer above program median timed at 0 hours post-verification -- is consistent with normal onboarding behavior and not accompanied by any other risk indicator in the record.
Evidence
{
"n": 4,
"band": "unscored",
"skoor": null,
"typology": "rapid_onboarding",
"confidence": null,
"thresholds": {
"hours": 24
},
"medianCents": "48155",
"routeReason": "detector not auto-closable",
"hoursSinceVerification": 0
}
Decision
Sign in as an operator to decide. Operator sign-in →
Dispositions
No disposition yet.
Actions
Freeze, request to program, and suspend need a second, distinct approver. Clear hold, cancel, and pause execute on the requester's approval. Executed through the bank's own API with the tenant's sandbox key; a dry run when there is none.
No actions requested.