Workspace/Sumsub
← All platforms

Sumsub

Verification and ongoing compliance

Sumsub spans individual and business verification, AML and fraud transaction monitoring, case management, workflow orchestration, device intelligence, and Travel Rule tooling. This makes it relevant beyond onboarding. Its products still need separate scope checks, especially for reporting, blockchain data, and merchant underwriting.

Our assessment

A credible broader-suite alternative to test, with merchant underwriting and reporting details still to establish.

Best fit and limitations

A useful cross-domain candidate when onboarding and ongoing monitoring should share customer context. Also relevant where crypto compliance is part of the product, subject to exact coverage.

  • Documented scope spans identity, AML monitoring, and fraud. Check the exact modules and contracts.
  • Travel Rule messaging and blockchain exposure analysis are different controls.
  • Report preparation and AI-assisted configuration do not prove direct regulator submission or independent compliance clearance.

Tools 8

KYC + KYBVerification
+
  • Person and business verification journeys
  • Reusable verification and risk-based follow-up checks
Source 1
Transaction MonitoringFraud and AML
+
  • Configure monitoring rules and sequences
  • Analyze transaction, customer, and behavioral inputs
Source 2
Screening and crypto complianceRisk checks
+
  • AML screening within the verification platform
  • Crypto monitoring and Travel Rule product areas
Source 1
Device IntelligenceEarly fraud signals
+
  • Identify device and behavior risk
  • Feed signals into customer and transaction review
Source 1
Case Management + Workflow OrchestrationOperations
+
  • Review evidence and manage cases
  • Configure follow-up checks and decision flows
Source 1
Summy AI CopilotReview and configuration assistance
+
  • Summarize applicant, alert, and case information
  • Draft rules and verification-flow configuration
  • Retain final review decisions with the human operator
Source 5
Fraud Network DetectionConnected fraud analysis
+
  • Find linked users and suspicious network patterns
  • Use graph neural networks with device and behavior context
  • Configure investigation settings in the dashboard after SDK integration
Source 6
Regulatory report preparationCase-based reporting
+
  • Prepare structured reports from case evidence
  • Apply checklists, access rules, and four-eye approval controls
  • Track case deadlines and investigator assignments
Source 7

AI capabilities

Verification and transaction models + Summy Copilot

Sumsub combines verification and transaction models with graph-based fraud detection. Summy separately summarizes cases and helps prepare workflow and rule settings. Human reviewers retain final judgment.

Analyze verification, transaction, and connected-fraud contextSummarize applicant and case evidenceDraft reviewed rules and verification-flow settings
What to validate

Validate proposed changes before applying them. Keep human judgment over review outcomes and separate report preparation from regulator submission.

Source 5

Implementation

Integration checklist
  • Enable the required monitoring products in sandbox and production.
  • Attach transaction data to the correct applicant and retain stable external IDs.
  • Test rule outcomes, case creation, callbacks, and user re-verification paths.
Commercial scope

Public packages and enterprise quotes differ. Request an itemized quote for KYC, KYB, checks, monitoring, device signals, cases, and crypto tools.

Questions for the demo
  1. Which verification, monitoring, screening, and case functions share the same license?
  2. What data must we supply for each transaction and payment rail?
  3. Can we export the full evidence chain and submit required regulatory reports?

Engineering

Transaction Monitoring quickstartChecked 2026-09-18Transaction rule and integration testingChecked 2026-09-18ML anomaly detectionChecked 2026-09-18Fraud network integrationChecked 2026-09-18Case reporting controlsChecked 2026-09-18
Your systemInputs & context
SumsubChecks & signals
Your controlsDecision & review
Illustrative integration boundary. Confirm the actual interfaces and decision authority.
Inputs
Transaction and applicant data for configured monitoring rules · SDK-collected device, interaction, and identity context
Outputs
Transaction-monitoring results · Anomaly signals against established applicant behavior · Linked-user patterns and fraud-network findings · Structured regulatory-report drafts and investigation records
Webhooks
The test flow validates delivered transaction webhooks and the client's response to approved or held transactions.
Decision timing
No measured latency or contracted response time verified.
Deployment
Deployment options not verified.
Dependencies
Configured monitoring rules and webhook handling · SDK integration and dashboard configuration for Fraud Network Detection · Configured checklists, role rules, deadlines, and four-eye approvals
Verified details 10
  • Inputs

    Transaction and applicant data for configured monitoring rules

    Source Checked 2026-09-18
  • Outputs

    Transaction-monitoring results

    Source Checked 2026-09-18
  • Webhooks

    The test flow validates delivered transaction webhooks and the client's response to approved or held transactions.

    Source Checked 2026-09-18
  • Dependency

    Configured monitoring rules and webhook handling

    Source Checked 2026-09-18
  • Outputs

    Anomaly signals against established applicant behavior

    Source Checked 2026-09-18
  • Inputs

    SDK-collected device, interaction, and identity context

    Source Checked 2026-09-18
  • Outputs

    Linked-user patterns and fraud-network findings

    Source Checked 2026-09-18
  • Dependency

    SDK integration and dashboard configuration for Fraud Network Detection

    Source Checked 2026-09-18
  • Outputs

    Structured regulatory-report drafts and investigation records

    Source Checked 2026-09-18
  • Dependency

    Configured checklists, role rules, deadlines, and four-eye approvals

    Source Checked 2026-09-18
Illustrative contract

An example for your internal adapter. This is not a vendor endpoint, request, or response.

json
{
  "contract": "internal-risk-review/v1",
  "vendorId": "sumsub",
  "internalCorrelationId": "example-001",
  "vendorRecordId": null,
  "control": "Verification",
  "evidence": [],
  "status": "pending",
  "decision": "review",
  "requiresHumanReview": true
}
Integration limits
  • Illustrative internal integration contract. This is not a vendor request, response, endpoint, or SDK example.
  • Empty country, deployment, or provider lists mean not verified in this review. A documented country refers to the specific product noted in its source, not universal platform coverage.
  • Use the release-specific API and applicant model; this page is a workflow introduction, not a complete field contract.
  • Test both rule behavior and downstream webhook handling before relying on a transaction decision.
  • The documentation names Isolation Forest. This evidence supports a statistical model, not independent filing or case-clearance authority.

Sources 7

Product and developer documentationdocs.sumsub.com2026-09-18 · Reviewed
Documentation
Transaction monitoring scopedocs.sumsub.com2026-09-18 · Reviewed
Documentation
Monitoring integration flowdocs.sumsub.com2026-09-18 · Reviewed
Documentation
Platform scopesumsub.com2026-09-18 · Reviewed
Announcement
Summy AI Copilotsumsub.com2026-09-18 · Reviewed
Product
Fraud Network Detectionsumsub.com2026-09-18 · Reviewed
Product
Case management and report preparationsumsub.com2026-09-18 · Reviewed
Product

Source review dates are shown above. Product claims come from public sources. Fit, limits, and evaluation questions are our analysis. This is not a hands-on performance test. Methodology · Changelog