Catching the right signal, not just more of it, is what separates a strong risk program from a noisy one. This month's release sharpens exactly that. Screening now checks aliases and trade names alongside the name on file, and crypto risk monitoring flags a real shift in a wallet's risk instead of re-checking every transaction. FinCEN 314(a) processing also moves entirely inside Sardine, so a request that used to route through a separate vendor now runs from start to finish in one place.
Here's what shipped in July.
The highlights:
- FinCEN 314(a) Screening Hub. Upload, match, and audit 314(a) lists directly in Sardine.
- Clearer alias and business name matches. Review the exact alias or DBA behind a sanctions, PEP, or adverse media match, with the context preserved in the audit trail.
- Risk level override history. A single, timestamped record of every manual risk-level change on CDD and BCDD profiles: reason, reviewer, expiration.
- Crypto delta-detection rules. Trigger monitoring on real change in a wallet's risk, not on every transaction.
- Expanded blockchain network coverage. Batch crypto screening now covers 126 networks, up from 48, full parity with the real-time API.
- Embedded workflow analytics. Execution volume, outcome distribution, and latency, all inside the workflow editor, plus a new badge marking alerts triggered by a workflow.
- Issuing Transaction Aggregations. Streaming aggregations replace live database lookups for issuing risk rules, with new lookback windows and category-level views.
AML Compliance: Stronger screening coverage, fewer false positives
FinCEN 314(a) Screening Hub
The 314(a) Screening Hub runs list uploads, matching, and audit history for FinCEN 314(a) requests directly inside Sardine. Upload a list once, and it matches against aliases, SSNs, phone numbers, addresses, and transaction counterparties, not just a primary name, which is a real jump in accuracy over name-only matching. Each file submission is a one-time screening event against your customer and transaction data in scope of your obligations.
A Latest Results view shows who uploaded a file and when, lets you download the original list, export audit results, upload a new batch, and filter matches by entity type, individual or business. Audit History keeps a running, chronological log of every list you've processed, with a status (active, completed, failed, or processing), record counts, and match counts, filterable by date. When an examiner asks about a specific cycle, that's one lookup inside the dashboard.
Clearer alias and business name matches
Alias and business name matches are now easier to review in the screening experience. In the dashboard, the screening widget breaks out submitted aliases directly in the customer header, and a dedicated Matched Name column shows reviewers which name triggered the match. Alias details are also captured in the audit trail alongside the screening result.
For API users, individual aliases can be passed through customer.aliases, while business trade names or DBAs can be passed through business.names.
Risk-level override history
Customer Due Diligence (CDD) and Business Customer Due Diligence (BCDD) subject pages now include a dedicated Override History panel, visible to anyone with CDD viewing permissions. Every manual risk-level change gets logged as an unchangeable record, newest first, with the action type, the stated reason, the reviewer, and any expiration date. Color-coded badges for SET, CHANGE, and RESET make a customer's risk history easy to scan, so when an examiner asks why a risk level changed, the answer is one panel away instead of a search through general review history.
Crypto Monitoring: Fewer alerts, more signal
We’ve enhanced crypto monitoring to reduce alert noise and make meaningful risk changes easier to spot.
Crypto delta-detection features
New delta features compare a wallet’s current risk state with its last known state, so teams can act on meaningful changes rather than re-evaluating the wallet’s full risk profile on every transaction. These features capture changes such as a jump in volume (TotalVolumeUsdDelta), a shift in counterparty risk category (CounterpartyRiskDelta.HasChanged), or a change in total risk instance counts. They can be used in rules and other workflows to focus reviews on wallets where something actually changed.
Expanded blockchain network coverage
Batch (CSV) screening now covers 126 networks, up from 48. This matches the coverage already available through the real-time API and includes every blockchain our screening provider supports. That's 78 additions, including Near, Sui, TON, Sei, Flow, and Fantom. Bulk screening jobs now get the same reach as real-time checks across whatever chains your customers actually use, and the public API reference has been updated to document every supported network.
Platform: More visibility across workflows and issuing rules
The last set of changes moves away from screening entirely, toward seeing what your workflows and rules are actually doing while they're doing it, instead of piecing it together after the fact. It's its own version of separating signal from noise: knowing which rule actually fired, and why, is the difference between reacting to an alert and understanding it.
Embedded workflow analytics
Embedded Analytics is now available directly in the workflow editor, showing real-time node latency and the percentage of times each rule fired on the workflow diagram. A new Workflows Overview chart brings execution volume, decision outcomes, and p50/p95/p99 latency together over time.
Alerts created by a workflow action node now also carry a Workflow badge in the alert list. From Alert Details, analysts can view the full execution trail to see exactly what produced an automated alert without leaving the page.
Issuing transaction aggregations
Issuing risk rules now draw on streaming aggregations, computed continuously in the background rather than calculated live on every check. That also opens up lookback windows that weren't practical before: a new 90-day window across all views, 12-hour and 14-day customer views, and brand-new category-level aggregations by MCC. For issuers running high transaction volume, precomputed aggregations mean rule evaluation no longer competes with live traffic for the same lookups during volume spikes.
Want to see any of this in action? Get in touch for a demo. Current customers can find the full details, including this month's access management updates, SDK changes, and data migration items, in our release notes and changelog.
