Skip to content

Digital-asset compliance & evidence · EU-focused

The system of record for digital‑asset compliance.

Screen addresses, monitor risk and document investigations in one workspace. Keep the sources, recorded sanctions-list state and review decisions behind every finding.

For banks, payment institutions, custodians, trading venues and CASPs, and the institutional teams investigating digital assets.

Explainable findings. Recorded reviews. Signed report data.

ChainEvidenceIllustrative data

Screening record

Counterparty address

REVIEW

0x7f9a00…0c214

Ethereum · ETH

Risk score

32 / 100

Sanctions result
No recorded match
Risk finding
Reported scam addressSource: ScamSniffer feed
Recorded list state
OFAC SDN · EU · UNRefreshed 06.10.2026

Review history

  1. Screening recorded

    09:41 UTC · Compliance analyst

  2. Review disposition: approved

    10:12 UTC · A. Meyer · original verdict: REVIEW

Signed report dataEd25519 · SHA-256
Composed product preview. The address, score, list dates and reviewer are illustrative; this is not a live result.

From an address to a documented decision

A workflow your team can explain.

Bring screening, follow-up investigation and human review into the same workspace, with reports to share the recorded findings.

  1. 01

    Screen

    Check addresses against imported sanctions lists and scam feeds. Apply your risk policy to receive an ACCEPT, REVIEW or REJECT verdict.

  2. 02

    Monitor

    Re-screen watched addresses on a schedule for sanctions and risk changes. Review alerts in the portal or receive signed webhooks.

  3. 03

    Investigate

    Examine the signals, source labels and fund-flow analysis for each network. Analysis depth follows the network and the lookup services you enable.

  4. 04

    Document

    Record a review decision alongside the original screening verdict. Export screening history and compliance summaries as signed PDF reports.

Monitoring runs as scheduled re-screening. Screening, monitoring and investigation each keep their own record.

Built for the people making the decision

Practical tools for your compliance team.

01 / Trading venues & CASPs

Screen before you proceed.

For payment providers, on-ramps, OTC desks, custodians and CASPs managing customer and counterparty addresses.

  • Screen at onboarding or before a withdrawal
  • Set risk thresholds and review flagged results
  • Monitor watched addresses on a schedule
Explore screening

02 / Banks & financial institutions

Make the investigation reviewable.

For teams that need a clear record of what was found, which sources contributed and who reviewed the screening decision.

  • Inspect findings and their cited sources
  • Keep the original verdict and review disposition
  • Export screening history and summary reports
Discuss your workflow

03 / Vendors & integrators

Put screening inside your product.

For compliance software vendors and developers embedding address screening and monitoring into their existing applications.

  • Call the authenticated screening API
  • Read verdicts, typologies and skipped checks
  • Verify signatures on webhook deliveries
Read the API reference

Already use an address-intelligence provider? We will walk through your evidence workflow in a briefing.

Evidence & auditability

A score is the start. The record is what matters.

Give reviewers the context behind a finding and a clear account of the decision that followed.

01

Explain the finding

Screening results include score breakdowns and structured risk typologies with named sources.

02

Record the sanctions-list state

Each screening stores the list names, refresh dates, entry counts and freshness flags available at the time of the check.

03

Keep the human decision

A screening review preserves the original REVIEW verdict, the approval or rejection, reviewer and timestamp. Audit history records selected team and configuration changes.

04

Verify the signed record

Institutional PDFs carry Ed25519 attestations and SHA-256 hashes. The public verifier checks the signed record and its headline figures.

Anyone holding a report can confirm its signed record and its issuer.

Open report verification

Network coverage

Different networks. Different capabilities.

Address-list screening is broader than tracing or service attribution. Here is what the screening workflow supports on each network.

Network capabilities: sanctions screening, scheduled monitoring, attribution and tracing
NetworkSanctions screeningMonitoringService attributionFund-flow analysis
BitcoinBTCListed-address matchingScheduled re-screeningBTC classification¹BTC outgoing fund-flow trace¹
EthereumETHListed-address matchingScheduled re-screeningSelected EVM labelsETH outflow clustering¹
BNB ChainBSCListed-address matchingScheduled re-screeningSelected EVM labels—
SolanaSOLListed-address matchingScheduled re-screening——
TRONTRXListed-address matchingScheduled re-screening——

Sanctions sources. Imported OFAC SDN digital-currency addresses and the addresses named on EU and UN lists, at the recorded feed freshness.

¹ Requires lookup services. BTC classification and tracing, and ETH outflow clustering, use lookup services your organisation enables. External lookups are off by default.

Attribution draws on selected public labels and the lookup signals you configure. Findings name the sources behind them.

Deployment

Where your data is processed.

Know where the platform runs and which services receive data.

Available

Hosted platform

Shared infrastructure with organisation-scoped records. Servers and databases run in the Netherlands (EU).

Logical tenant separation for every organisation.

Briefing

Your hosting requirements

Discuss isolation, hosting and contractual requirements for your institution with us.

Bring your security questionnaire to the briefing.

Each third-party lookup service you enable is listed with its operator and processing location. See data recipients and locations

For developers & integrators

One request. An inspectable result.

Screen an address against your organisation's risk policy. Read the verdict and the signals behind it, then decide how your application should handle the result.

POST/api/org/screening/screen

Request · use your organisation's API key

curl https://chainevidence.net/api/org/screening/screen \
  -H "Authorization: Bearer $CE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "address": "0x7f9a00000000000000000000000000000000c214",
    "chain": "ETH"
  }'

Illustrative response · selected fields

{
  "data": {
    "verdict": "REVIEW",
    "score": 32,
    "sanctioned": false,
    "matchedLists": [],
    "riskTypologies": [
      {
        "code": "SCAM_REPORTED",
        "severity": "high",
        "label": "Reported scam address",
        "source": "ScamSniffer"
      }
    ],
    "skippedChecks": [
      "evm_outflows"
    ]
  },
  "meta": {
    "requestId": "req_example"
  }
}

A useful response schema

The data object contains the persisted screening result: verdict, score, matchedLists, breakdown, riskTypologies, sanctionsSnapshot and skippedChecks. The meta object includes a request ID and billing fields.

Limits depend on the endpoint

POST /api/org/screening/screen/batch accepts up to 1,000 items. The portal screening batch also accepts 1,000. POST /api/v1/sanctions/check accepts up to 100 addresses.

Signed event delivery

Screening and monitoring events can be delivered to registered webhooks with HMAC signatures. Verify the signature before your system acts on the payload.

Create an organisation account to obtain an API key, then use the documented endpoint. API use is subject to your balance, rate limits and plan.

Try the screening APIView the endpoint reference ↗

The sample values are illustrative, not a result for the displayed address. The actual response also includes record identifiers, timestamps, list-state metadata and billing fields.

Details for your security and compliance review
Audit history
Key identity, team, screening-review and configuration events are recorded with actor and timestamp.
Review controls
Portal screening reviews can require a reviewer other than the initiating user.
Data-subject tools
Email-verified export and deletion cover individual investigation data.
Encryption scope
Stored API keys and configured MFA/SSO secrets are encrypted with AES-256-GCM.
Retention
Retention settings per record class, scheduled purging and an organisation-wide legal hold.
Report languages & exports
Website and portal in English and German. Institutional screening and compliance PDFs in English.
Travel Rule data
IVMS101 originator and beneficiary records for Travel Rule data.

See how it fits

Bring a real workflow to the briefing.

Tell us which addresses you screen, how your team reviews findings and what evidence you need to retain. We will walk through how ChainEvidence fits.