Scorechain

Asset managers and wealth offices adding digital assets to their portfolios face a compliance gap that traditional AML tools cannot close: those tools have no visibility into on-chain activity. Scorechain, headquartered in Luxembourg and operating since 2015, addresses this directly with a blockchain analytics and AML monitoring platform built specifically for institutions entering or operating in crypto markets. The firm explicitly targets asset and wealth managers as a client segment alongside banks, custodians, and crypto businesses.

For a family office or asset manager with cryptocurrency holdings, the practical workflow involves screening wallet addresses before transacting, monitoring ongoing fund flows for sanctions exposure, and generating audit-ready documentation for regulators. Scorechain supports that workflow through:

• Real-time wallet screening against OFAC, FATF, and EU sanctions lists
• Know Your Transaction (KYT) and Know Your Address (KYA) reports for due diligence documentation
• Fund flow tracing across 21+ blockchains including Bitcoin, Ethereum, stablecoins, and BNB Chain
• A VASP directory covering over 2,700 virtual asset service providers for counterparty due diligence
• Customisable risk scoring models that can be calibrated to internal compliance policies
• API-first integration into existing compliance or case management stacks

Scorechain differentiates from black-box analytics tools by making its risk scoring logic transparent and configurable, a meaningful distinction when compliance teams must explain decisions to regulators. The platform is EU-hosted on a private cloud, which matters for offices operating under GDPR or MiCA obligations. Pricing is not disclosed publicly, and the platform skews toward compliance and operations teams rather than investment teams making allocation decisions. Offices without existing crypto compliance infrastructure will find the broadest utility; those seeking portfolio-level performance analytics across traditional and digital assets will need to combine this with a separate reporting layer.