White Paper: From Risk Score Release Decision

Achieving a 360-degree overview of stablecoin transactions with Lukka and CryptoSwift

Every crypto-asset transfer a bank or Virtual Asset Service Provider (VASP) processes raises two fundamental questions: is the money risky, and who is behind it?

Historically, compliance teams have relied on fragmented tools to find the answers. Blockchain analytics sees addresses, flows, and the risk level of the funds, but it doesn’t reveal the identity of the transacting customer. Conversely, Travel Rule messaging exchanges the required originator and beneficiary identities, but says nothing about where the funds have been historically.

With MiCA fully in force and the EU AML Regulation arriving in July 2027, regulators expect institutions to have a unified, 360-degree visibility into each transaction. They also expect compliance teams to clearly evidence how they reached each release/pause/block decision.

To help compliance professionals navigate this, CryptoSwift has partnered with Lukka to publish a new joint white paper: “From Risk Score to Release Decision.” The paper provides a detailed overview of the methodology behind Lukka’s blockchain analytics tool, helping compliance people make sense of on-chain risk scores.

What Makes a Score Defensible?
A risk score that blocks a withdrawal or triggers a Suspicious Activity Report (SAR) must be defendable to an examiner. The white paper dives deep into Lukka’s blockchain analytics methodology, outlining the six dimensions of a defensible risk score, covering aspects from multi-hop exposure logic to the transparent explainability of the C-Score. It provides AML teams at banks with a robust framework to understand exactly how on-chain risk is calculated.

The CryptoSwift Rule Engine: The 360-Degree View
A defensible score is the starting point, but it must be operationalized. CryptoSwift serves as the compliance orchestration hub, bringing all critical data points into a single, automated authorization workflow.

Before a transfer is authorized, the CryptoSwift Rule Engine evaluates:

    • On-Chain Risk: Leveraging Lukka’s analytics to assess the risk of the funds and the wallet.

    • Payment Counterparty Data: Using our native Travel Rule capabilities and Know Your Wallet (KYW) tools to verify counterparty VASP or self-hosted wallet identities.

    • AML Screening: Running the Travel Rule data through sanctions, PEP, and adverse media screening.

By unifying Personally Identifiable Information (PII), financial data, AML screening results, and on-chain risk scores, CryptoSwift gives compliance officers a complete transaction overview. Instead of toggling between isolated platforms, compliance policies are configured directly into the Rule Engine. Transactions are automatically released, held for manual review, or escalated for Enhanced Due Diligence (EDD) based on your institution’s risk appetite.