Cowrie Research

marketguard

4 min read

MarketGuard

  • Name: MarketGuard
  • URL: https://marketguard.io/
  • Category: crypto compliance workspace operator / AML-KYC-KYT workflow company / VASP onboarding and case-management operator
  • Summary: MarketGuard belongs in companies/, not projects/, because the useful question is not whether there is a standalone MarketGuard protocol. The practical leverage sits with the named company that packages customer onboarding, identity-verification method choice, AML risk profiling, KYT thresholds, case handling, reporting workflow, and API-backed transaction ingestion into one compliance operating shell. That company boundary matters more than the product label because downstream teams may treat MarketGuard’s dashboard state, rule configuration, and review queues as authorization truth before customers or transfers proceed.
  • What it does:
    • Operates onboarding workflow for retail and business customers, including company, shareholder, and identity-verification intake for VASPs and other blockchain businesses
    • Packages multiple identity-verification methods such as SMS, video identification, video selfie, and photo selfie inside one review shell
    • Runs ongoing sanctions, PEP, watchlist, and shareholder monitoring rather than stopping at one-time onboarding checks
    • Lets compliance teams author AML quizzes, assign risk levels, and apply customer-specific monitoring thresholds that shape later transaction review
    • Runs KYT monitoring and case-management workflow that can escalate activity based on volume limits, blockchain-risk scores, country-risk checks, and related policy inputs
    • Exposes API surfaces for transaction ingestion and retrieval while keeping the actual compliance workflow anchored in the MarketGuard-operated dashboard and case system
  • Key claims:
    • The homepage calls MarketGuard a Plug-and-play AML & KYC solution for VASPs and CASPs and says it was Created by a financial institution for financial institutions, which is explicit company-and-workflow framing rather than neutral protocol framing
    • The homepage highlights KYC and KYB onboarding, transaction monitoring, integrated banks and custodians, secure data storage, customizable workflows, and regulatory reporting, showing the product is an operations shell rather than a narrow point feature
    • The help-center overview says MarketGuard covers onboarding, ongoing monitoring, risk profiling, transaction monitoring, case management, and regulatory reporting, which makes the workflow boundary easy to identify
    • The client-onboarding docs say the system collects company and shareholder data, supports wallet verification, supports custom statuses, and can integrate external KYC providers such as SumSub, which means MarketGuard can sit above multiple underlying verification providers while still owning the operator shell
    • The client-risk-profiling docs say compliance officers can create separate AML quizzes for business and retail clients, score answers automatically, assign normal, medium, or high risk levels, and set customer-specific limits, which is exactly the sort of company-authored policy layer that can shape who clears review
    • The KYT docs say high-risk cases can be triggered by daily limits, rolling 30-day limits, blockchain-risk scores from a third-party provider, country-risk checks, and payment-country checks, reinforcing that MarketGuard becomes a rule-and-escalation operator rather than a passive data feed
    • The public transaction API docs expose POST /api/v1/transactions and GET /api/v1/transactions, while the OpenAPI spec points at api.finchguard.com, suggesting a product-lineage / backend-continuity story that matters more as company infrastructure than as a standalone protocol surface
    • The onboarding docs note that some legal-entity forms, specifically trusts and foundations, are not supported in the documented workflow, which is another reminder that company-authored product policy determines what kinds of institutions fit through the pipe
  • Whitepaper: No classic standalone company whitepaper is the point here. The strongest primary materials remain the official site, help-center docs, workflow pages, and the linked OpenAPI spec already captured in ../whitepapers/marketguard-primary-sources-2026-05-01.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • There is not a useful standalone MarketGuard protocol boundary doing most of the analytical work.
  • Keep marketguard only as an alias for legacy links and filename continuity.
  • This company note is the real analytical object: the named operator packages onboarding, verification methods, risk-profiling logic, KYT thresholds, case workflow, reporting, and API-backed ingestion into one compliance shell that downstream teams can start treating as operational truth.

Control surface

  • Practical leverage sits in onboarding workflow design, supported legal-entity types, choice and packaging of identity-verification methods, wallet-verification handling, AML quiz design, risk-score interpretation, monitoring thresholds, case-escalation rules, reporting workflow, and which dashboard or API states downstream teams treat as authoritative.

  • MarketGuard does not matter because it owns a settlement rail or neutral protocol. It matters because it can become the company-run workflow that decides who gets onboarded, which customers look risky, and which transfers get escalated or cleared.

  • Read MarketGuard as a compliance-operations company, not as a protocol primitive.

  • Last reviewed: 2026-08-11 UTC

Graph View

Backlinks