Use cases
Every use case below follows the same five-step shape. That is deliberate: one control path serves deposits, withdrawals, onboarding, treasury and investigation, on Bitcoin as well as account-based networks.
The real-world event that starts the case
What the platform checks, and against which data
The outcome under the policy version in force
What the institution then does operationally
What is retained and can be re-read later
Trigger
A customer sends Bitcoin or an account-based network asset to a bank-controlled deposit address.
Controls
Wallet ownership, source-of-funds tracing, Travel Rule status, banking policy.
Decision
Allow, hold, review, reject or escalate.
Outcome
Deposit accepted, held for review or rejected. Execution remains separately controlled.
Evidence
Policy version, triggered rules, tracing result, approval history.
Trigger
A customer requests a withdrawal to an external address.
Controls
Destination screening, destination-of-funds tracing, banking policy.
Decision
Allow, hold, review, reject or escalate.
Outcome
Withdrawal approved, held, or rejected pending further review.
Evidence
Destination attribution, exposure findings, decision record.
Trigger
A corporate customer registers an address or address cluster for ongoing use.
Controls
Beneficial ownership, ownership proof, prior-activity screening.
Decision
Approved, held for review, or rejected.
Outcome
Registration activated for use, or referred back to the customer or an analyst.
Evidence
Ownership proof record, screening result, registration decision.
Trigger
Recurring institutional treasury movement in stablecoins.
Controls
Standing policy thresholds, counterparty attribution, reconciliation.
Decision
Allow under standing policy, or escalate on deviation from the expected pattern.
Outcome
Routine movement proceeds under control; deviations are reviewed.
Evidence
Policy version applied, reconciliation record.
Trigger
An alert or manual case flags an address for origin review.
Controls
Multi-hop upstream tracing across output lineage or the account graph, entity attribution, confidence assessment.
Decision
Case outcome: cleared, escalated or referred for filing preparation.
Outcome
Investigation closed with a documented finding.
Evidence
Trace graph, attribution confidence, analyst notes, evidence package.
Trigger
A pending withdrawal requires destination risk clearance.
Controls
Downstream tracing, sanctioned, mixer and threat exposure checks.
Decision
Cleared, held, or rejected based on destination exposure.
Outcome
Withdrawal proceeds or is blocked pending resolution.
Evidence
Destination trace, exposure classification, decision record.
Trigger
A regulator or internal audit requests case history for a customer.
Controls
Case timeline reconstruction, evidence integrity verification.
Decision
Dossier prepared for authorized review.
Outcome
Regulatory dossier assembled; external filing remains a separate, human-authorized action.
Evidence
Full case timeline, evidence package, integrity hashes.
Trigger
A bank stands up a new digital-asset product line.
Controls
Dedicated deployment, policy configuration, role and permission setup.
Decision
Institution-specific policy and integration architecture agreed.
Outcome
Deployment scoped and configured ahead of go-live.
Evidence
Deployment and policy configuration record.
Map ChainGuard to your institution’s transaction, policy and evidence workflows.