Skip to content

Add Traditional Finance Integration Guide for Crypto AML Alerts #7

@matheusybsen

Description

@matheusybsen

I'm an AML analyst at a financial institution exploring crypto services. OpenAML's ML
models are excellent at detecting illicit stablecoin activity, but there's no guidance
on how to integrate these crypto alerts into our existing AML case management systems
(like Actimize, NICE, or even Marble).

When OpenAML flags a wallet as "Sanctioned" or "Hack/Phishing," we need to:

  • Create a case in our traditional AML system
  • Link it to the customer's fiat banking activity
  • File SARs that combine on-chain + off-chain evidence
  • Track disposition for regulatory reporting

Right now there's no documentation on how to do this integration.

Solution

Add documentation and examples for integrating OpenAML with traditional AML workflows:

  1. API Integration Guide

    • How to export OpenAML risk scores to traditional AML systems
    • Sample API calls for case creation
    • Field mapping (wallet address → customer ID)
  2. SAR Filing Guidance

    • How to write SAR narratives for crypto alerts
    • Required fields for FinCEN crypto SAR filing
    • Examples of combining on-chain + off-chain evidence
  3. Workflow Templates

    • Decision tree: When to escalate crypto alerts
    • SLA recommendations for different risk levels
    • Investigation checklists for crypto cases

Alternatives

  • Manual export: Copy/paste wallet addresses into our AML system - error-prone
  • Build custom integration: Too complex and time-consuming
  • Separate crypto monitoring: Creates compliance gaps between fiat and crypto

Additional context

Why this matters:

  • Most financial institutions have existing AML infrastructure
  • Crypto services are being added to traditional banks/fintechs
  • Regulators expect unified AML programs (crypto + fiat together)

Regulatory drivers:

  • FinCEN expects crypto SARs to follow same format as fiat SARs
  • FATF "Travel Rule" requires linking crypto and fiat identities
  • EU MiCA regulations require integrated compliance programs

Business value:

  • Makes OpenAML easier to adopt for traditional FIs
  • Reduces integration time from months to weeks
  • Demonstrates how OpenAML fits existing compliance stacks

I can help provide:

  • Sample SAR narratives for crypto alerts
  • Integration requirements from traditional AML teams
  • Feedback on what compliance officers need to see

This would make OpenAML much more accessible to the financial institutions
FINOS serves!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions