Skip to main content

FINANCIAL INTELLIGENCE FOR REGULATED INSTITUTIONS

Turn blockchain activity into defensible financial decisions.

Trace source and destination of funds, identify entities, apply your policies, and generate regulator-ready evidence.

Multi-chain
coverage
7+ blockchains
Institutional grade
compliance
AML, sanctions, risk
Audit-ready
evidence
For regulators
  • Multi-chain intelligenceEthereum, Polygon, BSC, Base…
  • Sanctions screeningOpenSanctions & OFAC lists
  • Policy engineCustomizable to your risk appetite
  • Audit-ready evidenceRegulator-friendly reports
  • API-firstIntegrate with your systems
01Decision architecture

One record, progressively enriched.

Blockchain activity becomes an attributable, governed and provable financial decision without leaving the control path.

  1. 01
    Trace

    Reconstruct source or destination of funds across the bounded graph available to the institution.

    IN
    1.84 BTC · bc1q…7f2d
    OUT
    4 hops · 1 trace break
  2. 02
    Identify

    Resolve wallets and clusters to entities, customers, owners and counterparties with stated confidence.

    IN
    5 references on path
    OUT
    Exchange 92% · 1 unattributed
  3. 03
    Decide

    Combine risk, customer context and versioned banking policy into a canonical outcome.

    IN
    Risk + customer + policy v4.2
    OUT
    REVIEW · 2 rules matched
  4. 04
    Explain

    Show the facts, inferences, missing data and rules that produced the decision.

    IN
    Facts, inferences, gaps
    OUT
    5 typed statements
  5. 05
    Prove

    Retain evidence, approval history, trace path, hashes and timeline for later review.

    IN
    Decision + approval history
    OUT
    sha256 9f4c…a17b
02Investigation

Follow value. Resolve who is behind it.

The transaction graph, entity attribution and customer record occupy one investigation plane. Unknown data remains visibly unknown.

Explore flow intelligence
Financial flow intelligenceIllustrative example · sanitized data
Illustrative source-of-funds flow for a Bitcoin depositSanitized example. Funds reach the customer deposit address through one intermediate hop. One upstream path is attributed to a regulated exchange at 92 percent confidence. A second path passes a cross-chain bridge where trace continuity breaks, back to a cluster that remains unattributed at 21 percent. The deposit address is linked to its customer record: enhanced due diligence, restricted status.HOP 3HOP 2HOP 1SUBJECTCUSTOMERUnattributed clusterbc1q…9a04 · 21%Regulated exchangebc1q…0b9a · 92%Cross-chain bridge0x8b70…21af · 74%Intermediate hopbc1q…e41c · 64%Deposit addressbc1q…7f2d[DEMO] Aurora ImportsEDD · restrictedcontinuity breaks
  • Attributed
  • Trace break
  • Unattributed
  • Subject / customer
Trace ledger
0bc1q…7f2dSubject addressRegisteredCustomer deposit address
1bc1q…e41cIntermediate hop64%Unspent-output lineage
2bc1q…0b9aRegulated exchange92%Attributed cluster
20x8b70…21afCross-chain bridge74%Trace continuity breaks
3bc1q…9a04Unattributed cluster21%Stated as unknown
Address → entity → customer → compliance context
bc1q…7f2dREGISTERED WALLET[DEMO] Aurora Imports LtdEDD · RESTRICTED
03Decision control

Policy turns intelligence into one governed outcome.

Observed facts, attributed risk and customer context converge under the exact institution-controlled policy version.

01 / factObserved facts

Deposit credited, 3 confirmations, four upstream hops

02 / inferenceRisk context

Indirect exposure to a high-risk cluster

03 / contextCustomer context

Enhanced due diligence, restricted status

04 / policyVersioned policy

deposit-policy v4.2, maker/checker required

POLICY deposit-policy v4.2

VELOCITY_24HMATCH

UNVERIFIED_SOURCEMATCH

SANCTIONS_DIRECTCLEAR

Canonical outcomeREVIEW

Manual review required

Pending checker approval
Decision explanationFACTS → INFERENCE → GAPS → RULE → OUTCOME
  1. 01Observed factTransaction observed

    1.84 BTC credited to a customer deposit address

  2. 02System inferenceEntity / source attributed

    Upstream exchange cluster at 92%; one cluster unattributed

  3. 03Missing dataRisk finding recorded

    Indirect exposure; trace completeness partial past a bridge

  4. 04Policy evaluationPolicy rule applied

    deposit-policy v4.2: VELOCITY_24H, UNVERIFIED_SOURCE

  5. 05Final decisionDecision issued

    REVIEW, pending checker approval; no funds moved

Evidence package
Policy version
deposit-policy v4.2
Triggered rules
2 rules
Source facts
On-chain and customer record
Trace path
4 hops, 1 break
Approval history
Maker recorded, checker pending
Timeline
Chronological, append-only
Content hash
sha256 9f4c…a17b
04Compliance operations

A live operating surface, not a reporting card.

Demo records
5
Pending human review
2
Partial evidence
3
Illustrative operational view · synthetic demo data, not production customers
ReferenceTransaction / customerAmountDecisionOperational stateEvidenceConfidence
demo-dep-auroraDeposit[DEMO] Aurora Imports Ltd184,250.00USDTDecision: REVIEWReview requiredPARTIAL78%
demo-dep-northstarDeposit[DEMO] Northstar Treasury75,000.00USDCDecision: ALLOWReleasedCOMPLETE96%
demo-dep-atlasDeposit[DEMO] Atlas Interactive420,000.00USDTDecision: HOLDHeldPARTIAL91%
demo-wd-auroraWithdrawal[DEMO] Aurora Imports Ltd92,000.00USDTDecision: ESCALATEReview requiredPARTIAL83%
demo-wd-atlasWithdrawal[DEMO] Atlas Interactive210,000.00USDTDecision: REJECTHeldCOMPLETE94%
Decision: ALLOWDecision: HOLDDecision: REVIEWDecision: REJECTDecision: ESCALATE
05Integration plane

Intelligence moves through controlled interfaces.

Illustrative request shape, provider hand-off and supported ledger models share the same integration surface.

ILLUSTRATIVE REQUEST
POST /v1/transactions/analyse
{
  "reference": "DEMO-DEP-0184",
  "network": "bitcoin",
  "customer_ref": "DEMO-ACC-AURORA"
}

→ decision: REVIEW
→ evidence: sha256 9f4c…a17b
Network coverage / ledger model

BitcoinUTXONative flow lineage

EthereumAccountTokens and contracts

PolygonAccountTokens and contracts

ArbitrumAccountTokens and bridges

OptimismAccountTokens and bridges

BaseAccountTokens and contracts

Payload shape only · not a live endpoint or published schema. Operational execution remains separately controlled.

06Security and governance

Controls remain visible at the system edge.

MFA / RBACENFORCED

Maker / checkerREQUIRED

Audit recordsAPPEND-ONLY

Dedicated deploymentAVAILABLE

Fail-closedCONTROLLED

Review security and governance

Private deployment review

Make every digital-asset financial decision explainable.

Map ChainGuard to your institution’s transaction, policy and evidence workflows.