Results that compliance teams measure.
AML compliance clients are under NDA. We describe outcomes by institution type and scale — the results are documented and verifiable with pilot clients during evaluation.
Consumer neobank with 500,000+ accounts
Growing challenger bank offering checking and savings accounts to millennial consumers. Primary payment rails: ACH push, debit card, and Zelle. Compliance team of three full-time BSA analysts.
The challenge
The bank had been running a legacy AML platform calibrated for traditional community bank transaction patterns. With a consumer neobank customer base — high-frequency small-dollar ACH transactions, P2P splits, recurring bill pay — the rule engine was generating a 94% false-positive rate. Two of three BSA analysts were spending the majority of their time clearing noise.
A scheduled FinCEN examination in Q2 2025 had identified the high false-positive rate as a program weakness. The examiner's management response requested a documented remediation plan within 90 days.
The approach
The bank ran a 60-day pilot of Riftbeacon's transaction monitoring against their live transaction stream, parallel to their existing platform. During the pilot, Riftbeacon's neobank rule library ran against 45 days of historical transactions to establish the baseline false-positive rate differential.
The integration used Riftbeacon's REST API connected to the bank's Modern Treasury ledger. No professional services engagement required — their engineering team handled the integration in 12 business days.
"Our false-positive alert volume dropped by 58% in the first 30 days. Same transaction volume, half the noise. The two analysts who were clearing false alarms now have time to work the actual suspicious activity queue." — BSA Officer, consumer neobank
B2B payments platform processing $1.8B annually
Early-stage payments fintech enabling ACH, same-day ACH, and wire payments for small business clients. Registered MSB with direct FinCEN SAR obligations. Sponsor bank relationship with formal quarterly BSA program review.
The challenge
The platform was using a spreadsheet-based alert tracking system that had worked at $200M annual volume but was breaking down at $1.8B. SAR filing was taking an average of four days per case — an analyst-hours problem compounded by an approval workflow managed by email. The sponsor bank's BSA officer had flagged the manual process as a program risk.
The multi-rail complexity (ACH batch, same-day ACH, wire) meant a single-rail monitoring tool would miss cross-rail structuring patterns. No existing lightweight solution addressed all three rails with the sponsor bank documentation requirements.
The approach
Implementation through Riftbeacon's Dwolla connector (pre-built for their ledger model). Multi-rail rules configured for their specific ACH batch timing and wire volume thresholds. Sponsor bank reporting template configured to match the quarterly review format.
"Legacy vendors quoted us 9-month implementations. Riftbeacon had us live in 5 weeks. Our sponsor bank's BSA officer described our Q3 compliance report as the most thorough she'd seen from a fintech of our size." — Head of Compliance, B2B payments platform
Why we don't publish client names
AML compliance clients operate in a regulated environment where their program details — alert rates, SAR volumes, filing timelines — are sensitive. Disclosing which institutions use a specific AML vendor can inadvertently signal information about their monitoring approach to sophisticated bad actors.
We describe outcomes by institution type and anonymized scale. During a pilot evaluation, we can connect you with existing clients for reference conversations under NDA. We don't do surprise introductions.
Request Pilot AccessSee what the numbers look like on your data
Request a pilot and we'll run Riftbeacon's monitoring engine against your transaction history. Compare false-positive rates side by side before committing.