Sumsub

• Name: Sumsub
• URL: https://sumsub.com/
• Category: compliance-and-identity orchestration company / Travel Rule workflow operator / crypto-monitoring and case-management company
• Summary: Sumsub belongs in companies/, not projects/, because the durable dependency here is a named operator that decides dashboard roles, verification levels, rule bundles, protocol-routing behavior, screening-provider composition, case workflow, and webhook/reporting truth across onboarding, transaction monitoring, and Travel Rule review. The useful question is not just can this VASP do Travel Rule? but which company controls the review graph, counterparty-data exchange path, and evidence surface the VASP inherits by default?
• What it does:
  • Operates a unified dashboard and API surface for user verification, business verification, transaction monitoring, fraud prevention, AML checks, and Travel Rule workflow
  • Packages Travel Rule checks inside its broader transaction-monitoring stack rather than as a standalone neutral transport rail
  • Routes counterparty-data exchange through Sumsub’s own API path when both VASPs are clients, through connected protocols such as TRP, CODE, GTR, or Sygna Bridge when available, and through email fallback when the counterparty is outside known networks
  • Screens wallets and transactions using blockchain analytics, entity attribution, sanctions data, ready-made rule bundles, dashboard review flows, and API-delivered results
  • Supports unhosted-wallet verification flows, including digital-signature verification and microtransaction-style ownership checks, as part of Travel Rule compliance workflow
  • Extends the same operator shell into case management, workflow builder, AI-assisted review, analytics, FIU reporting, and risk scoring
• Key claims:
  • The homepage frames Sumsub as AI-powered trust infrastructure for compliance operations at scale and positions identity, fraud, AML, transaction, and case data as one decision layer rather than a narrow point solution
  • The docs overview says customers verify users, businesses, and transactions all from a single Dashboard, then recommends a company-controlled setup path through user access management, role assignment, verification-level creation, customization, testing, and SDK-or-API go-live
  • The Travel Rule docs say the checks are part of Sumsub’s Transaction Monitoring solution, include multi-level risk evaluation, use the most popular data-exchange protocols under the hood, support VASP attribution, and can automatically choose the quickest or easiest path for obtaining counterparty data
  • The same Travel Rule docs say the product supports 8,000+ virtual assets and surfaces wallet scoring, sanctions screening, adverse-media checks, and interoperability handling inside one workflow shell
  • The protocol-selection docs say Sumsub routes data directly by its own API when both VASPs are clients, uses TRP when both parties support it, can interoperate via CODE, GTR, or Sygna Bridge, and otherwise attempts email notification or even offers the counterparty a free account for data exchange
  • The Crypto Monitoring docs say Sumsub screens counterparty wallets before transfers, screens confirmed transactions after broadcast, uses provider blockchain analytics and entity-attribution data, and exposes outcomes through ready-made rule bundles plus the Dashboard and API
  • The unhosted-wallet-verification docs say the feature is enabled through Sumsub support / customer-success workflow and then governed by installed rule bundles, which is a concrete reminder that self-hosted-wallet checks are part of a company-managed policy surface rather than a neutral protocol primitive
• Whitepaper: No classic standalone company whitepaper is the important artifact here. The strongest primary materials are the current homepage and docs for overview, Travel Rule, protocol routing, crypto monitoring, and unhosted-wallet verification.
• Sources:
  • https://sumsub.com/
  • https://docs.sumsub.com/docs/overview
  • https://docs.sumsub.com/docs/travel-rule-overview
  • https://docs.sumsub.com/docs/protocols
  • https://docs.sumsub.com/docs/crypto-monitoring
  • https://docs.sumsub.com/docs/unhosted-wallet-verification
  • https://docs.sumsub.com/reference/get-started-with-api

Internal linkages

• Project-layer alias preserved for old links: sumsub.
• Closest adjacent company note in the same compliance-routing cluster: notabene.
• Transport-and-directory baseline beneath any one vendor shell: trisa.
• Useful data-provider companions whose outputs can become part of Sumsub-managed review flow: chainalysis, trm-labs, elliptic, and crystal-intelligence.

Protocol / company boundary

• There is not a very useful standalone Sumsub protocol boundary doing most of the analytical work.
• The transport pieces underneath this stack are external or shared: TRP, CODE, GTR, Sygna Bridge, email fallback, and third-party blockchain-intelligence feeds.
• The meaningful dependency is that Sumsub packages those rails into one dashboard, rules engine, case workflow, verification-level system, and go-live path that customers start treating as the operational truth surface.
• That is why this note belongs in companies/: the sharp question is who controls review thresholds, workflow defaults, fallback behavior, and counterparty-data exchange policy once a customer adopts Sumsub.

Control surface

• Practical leverage sits in dashboard role design, verification-level configuration, rule-bundle activation, protocol-routing and fallback logic, provider composition, case-review workflow, unhosted-wallet verification policy, webhook and reporting truth, and support-mediated feature enablement.

• The important lock-in is operational memory: once a VASP or fintech hardens around Sumsub’s applicant model, transaction states, counterparty-routing path, case queue, and evidence artifacts, the dependency is on a company-run workflow graph rather than on the Travel Rule concept in the abstract.

• Read Sumsub as a compliance-and-decision operator first, and as a Travel Rule product second.

• Last reviewed: 2026-08-08 UTC