The entity's first transfer, $1,273.27, above the program median, came 0.0 hours after verification.

What happened. The rapid_onboarding detector fired on the entity's first transfer, an ACH debit of $1,273.27, initiated 0.0 hours after verification, which is above the 24-hour threshold used by the detector and above the program median of $568.88. What the evidence shows. The transfer acht_sim_meri_afxrry0i9r7 settled with no return code. The entity Alder Co 20 is VERIFIED, not high risk, not PEP, has no review reasons on file, and was screened on 2026-06-21. The only contributing signal is counterparty.first_time (+10). The transfer skoor is null with n=0 and confidence null, meaning there is not yet enough transaction history to score this entity, not that risk was detected. The counterparty's country is unknown, which is a data gap rather than a positive risk indicator. There are no prior dispositions on this entity. What was checked. Reviewed the alert evidence block, the transfer record and its settlement status, the program's declared volume and rails, the entity's verification and screening status, and prior dispositions. No hard signal was present, and the route reason recorded is 'detector not auto-closable' rather than any elevated risk finding. What is recommended. The transfer has already settled, so there is no held transfer to release or hold. Given verified identity, no high-risk or PEP flags, no adverse screening, no return code, and a single low-weight signal (first-time counterparty), no further action is needed on this alert. If the entity generates additional rapid or high-value transfers shortly after onboarding, those should be reviewed together as a pattern.

{
  "n": 0,
  "band": "unscored",
  "skoor": null,
  "typology": "rapid_onboarding",
  "confidence": null,
  "thresholds": {
    "hours": 24
  },
  "medianCents": "56888",
  "routeReason": "detector not auto-closable",
  "hoursSinceVerification": 0
}