Alert · reviewed · open
The entity's first transfer, $1,265.56, above the program median, came 0.0 hours after verification.
- Detector
- rapid_onboarding
- Severity
- medium
- Program
- Lantern Lending (simulated)
- Subject
- transfer acht_sim_lant_9lsxrgz8cjx
- Transfer
- acht_sim_lant_9lsxrgz8cjx · $1,265.56 · 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. The rapid_onboarding detector fired on entity Birch Holdings 313's first transfer, an outgoing ACH debit of $1,265.56, initiated 0.0 hours after the entity's verification was completed. The amount is above the program's median transfer size of $1,258.18.
What the evidence shows. The transfer acht_sim_lant_9lsxrgz8cjx settled with no return code. The entity is BUSINESS-type, VERIFIED, not flagged high risk, not PEP, with no review reasons on file, last screened 2026-07-06. The only signal present is counterparty.first_time (+10). The transfer and entity skoor are both unscored (n=0, confidence null), so no model-based risk score supports or contradicts the detector's finding. There are no prior dispositions on this entity.
What was checked. Verified transfer status (SETTLED, no return code), entity verification status and risk flags, program declared volume ($900,000.00/month) against the transfer size, the median comparison cited in the evidence, and prior disposition history (none found).
What is recommended. No adverse indicators beyond the timing pattern itself (transfer immediately following verification) and a single first-time-counterparty signal. The transfer has already settled, so no funds are pending action. Given the verified entity status, absence of high-risk or PEP flags, clean screening history, and lack of any hard signal, this alert does not require further review at this time. Close the alert.
- Recommendation
- close
- Confidence
- 0.68
- Model
- claude-sonnet-5
- Drafted
- 2026-09-17 19:30Z
- Rationale
- Transfer status is SETTLED with no return code, so no funds are in a holdable state.
- Entity is VERIFIED, not high risk, not PEP, with no review reasons and no prior dispositions.
- Only one signal present (counterparty.first_time), which is expected for a first transfer and not independently indicative of risk.
- Transfer amount ($1,265.56) is only marginally above the program median ($1,258.18), not a large outlier.
- hard_signal is false and skoor is unscored (n=0), meaning no scoring model flags this transfer as concerning, though this also means confidence in a fully clean bill of health is limited by thin scoring data.
Evidence
{
"n": 0,
"band": "unscored",
"skoor": null,
"typology": "rapid_onboarding",
"confidence": null,
"thresholds": {
"hours": 24
},
"medianCents": "125818",
"routeReason": "detector not auto-closable",
"hoursSinceVerification": 0
}
Skoor signals
| Signal | Weight | Hard | Detail |
|---|---|---|---|
| counterparty.first_time | +10 | first transfer with this counterparty |
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.