AI capabilities
See what each platform’s AI does, and what to verify.
AlloyFraud models + a native AI Assistant
Alloy separates predictive fraud intelligence from an agentic assistant for procedural work. The assistant uses the context of its decisioning and identity platform.
- Resolve review tasks
- Research business entities
- Explain pending applications
Require source attribution, action approval rules, decision write-back records, and evidence that an assistant cannot change policy outside its role.
ComplyAdvantageRisk intelligence + screening review agents
Mesh documents agents that resolve routine screening alerts under configured thresholds and risk policies. The published scope includes sanctions, PEP, and adverse-media review, with recorded decision reasons.
- Investigate screening matches
- Resolve eligible routine alerts
- Record evidence and decision reasons
Test allowed actions, uncertain matches, policy limits, and escalation. Keep source profile IDs, list versions, risk decisions, and approvals beside each AI output.
CorisMerchant models, visual analysis, assistants, and configured agents
CorShield and payment models produce risk assessments. AI also classifies merchant activity, analyzes site imagery and content, and summarizes review evidence. Assistants support an analyst; separately configured agents can resolve routine alerts, request information, and trigger connected payout controls. Coris MCP exposes both read and write workflows to a connected AI client. Public pages describe these actions, but protected technical docs prevent verification of the full permission and execution contract.
- Assess business impersonation and payment risk
- Classify business activity and inspect website or location evidence
- Summarize cases, resolve permitted alerts, and escalate exceptions
Define each agent's policy, allowed actions, escalation rules, and approval gates. Validate decisions against retained source evidence and test failures before enabling write actions. Confirm MCP scopes, processor permissions, model versions, and logs. Keyword screening is not proof of deterministic entity matching; generated reasoning and customer success figures are not independent accuracy evidence.
Dow JonesXapien-powered due diligence research
Integrity Check combines Dow Jones risk content with Xapien generative AI, language processing, and entity resolution. It prepares research reports. This does not establish a native autonomous AML case or filing agent.
- Research people and companies
- Resolve relevant source records
- Summarize due diligence findings
Confirm licensed content, source-linked output, analyst review, and correction handling. Test report quality separately from screening match quality.
FeedzaiPredictive models + RiskOps Studio guidance
Feedzai combines transaction and behavioral models with RiskOps Studio assistance for documentation, strategies, and investigations. Public guidance features do not establish autonomous case clearance or policy publication.
- Score transaction risk
- Prioritize AML alerts
- Explain documentation and investigation context
Validate model performance separately from generated guidance. Confirm human approval and permissions before using proposed changes.
FinScanPrecision matching + data preparation
FinScan emphasizes data preparation and field-level matching rules. Advanced matching is not evidence of a predictive fraud model or a generative investigation agent.
- Identify hidden party names
- Improve candidate matching
- Reduce duplicate review work
Test raw, deliberately messy source records before and after preparation. Measure missed parties as well as false matches.
FlagrightRule assistance + investigation agents
AI Forensics supports transaction and screening review. Published controls include modes from silent evaluation to more automated handling, with explanation and version information.
- Draft rule logic
- Investigate monitoring alerts
- Prepare screening recommendations
Test silent mode first. Examine the evidence for cleared alerts, reopen behavior, approval rules, and exportable decision history.
FootprintPercy agents with versioned workflow actions
Percy supports evidence gathering and case analysis. A playbook can run a released agent version and pass its structured output to rules and action nodes. Those nodes can set onboarding decisions, request review, or update status, tags, and notes. This documents bounded workflow automation, not unrestricted authority to clear compliance cases, move funds, or file reports.
- Research a business or screening hit
- Return structured findings to a configured playbook
- Support cited investigations and historical testing
Inspect the pinned agent version, allowed inputs, downstream actions, and approval gates. Test conflicting evidence and mandatory review paths. Organizational-memory approval is documented; confirm the separate permissions for case disposition and policy changes. Exact matching and workflow rules do not establish predictive fraud-model performance.
Hawk AIDetection models + AML and screening agents
Hawk's AML Investigative Agent assembles evidence, updates summaries, and recommends or performs permitted routine steps. Customer Screening Agent separately evaluates hits under the institution's policy.
- Assemble AML investigation evidence
- Review screening hits
- Recommend or run permitted investigation steps
Set automated actions and human checkpoints per agent. Confirm source access, model approval, and low-confidence escalation.
JumioIdentity and biometric intelligence
Jumio describes AI for document verification, biometrics, identity connections, and screening. These are specific verification functions, not proof of autonomous compliance investigation.
- Detect altered documents
- Assess liveness and selfie matching
- Link identity risk signals
Test deepfake and injection attacks, low-quality captures, device variation, and the reason given for each failure.
LexisNexisDigital identity models + screening intelligence
ThreatMetrix applies AI models to digital fraud patterns. Screening products use their own matching and decision tools. The AI method and operational authority differ by product.
- Score digital identity risk
- Prioritize screening matches
- Support automated risk decisions
Ask for model and match explanations separately. Confirm any agent product by name, availability, and permitted actions.
LSEG World-CheckScreening and matching intelligence
LSEG combines researched risk data with screening technology. Do not equate a match score with a probability that a person is sanctioned.
- Retrieve candidate matches
- Support identity disambiguation
- Prioritize screening review
Validate aliases, transliteration, missing birth dates, entity types, and repeat-match suppression using a labelled test set.
Moody’sEntity intelligence + Due Diligence Agent
The Due Diligence Agent coordinates research and report drafting using Moody’s data and selected external sources. It produces structured findings with source attribution. Analysts own the final conclusions.
- Retrieve due diligence evidence
- Prepare sourced investigation reports
- Support customer risk review
Test source dates, incomplete ownership chains, contradictory records, and analyst approval. Confirm the licensed data and deployment scope.
NICE ActimizePredictive analytics + ActOne and Xceed agents
ActOne InvestigateAI prepares investigation plans and summaries. NarrateAI drafts SAR narratives. Xceed has separate agent capabilities; permissions and product access must be checked for each deployment.
- Plan and summarize investigations
- Draft SAR narratives
- Support product-specific investigation steps
Confirm role permissions, permitted actions, human checkpoints, and source evidence separately for ActOne and Xceed.
OpenSanctionsTransparent matching, not an AI investigator
The recommended logic-v2 matcher uses deterministic rules, culturally aware name matching, and identifier checks. It returns candidates and similarity scores; it is not an AML investigator or a predictive fraud model.
- Find candidate entities
- Score attribute similarity
- Support source-level investigation
Version datasets and algorithm settings. Validate thresholds and keep analyst decisions independent from raw similarity scores.
OracleModels, simulation + AI Investigator
Compliance Studio supplies ML and graph analytics. Compliance Agent tests monitoring controls in a simulation. AI Investigator separately assists live investigation work. Each function has a different purpose and approval boundary.
- Find connected activity
- Test control blind spots
- Assist investigation review
Separate model approval, synthetic test results, and case decisions. Confirm the AI Investigator release, source evidence, analyst approval, and enabled actions.
OscilarPredictive models + configurable risk agents
Oscilar describes agents for building policies, analyzing performance, and investigating cases, alongside ML models used in risk decisions.
- Build decision workflows
- Analyze policy performance
- Prepare case investigations
Test change approvals, sandbox execution, deterministic replay, external tool permissions, and protection against untrusted document instructions.
PayabliRead-only Insights, scoped enrichment actions, and separate agent roadmap
Amigo Insights supplies analytics. Vendor enrichment has documented automatic and review modes; AI outreach is opt-in beta. The product site also describes risk models. Amigo Risk, Chargebacks, and Onboarding remain labeled Coming Soon. These are different evidence levels and operating permissions.
- Answer payment-data questions and prepare charts
- Research vendor payment methods and fill empty record fields when configured
- Schedule enabled beta outreach to collect payment preferences
Apply organization scope and amigo_read permissions to Insights. Use enrichment review mode when a person must approve changes. Confirm outreach settings and beta access. Do not infer payment, refund, underwriting, or reserve authority from an agent label.
PersonaIdentity models + policy assistance
Policy Agents extracts requirements, flags conflicts, and maps them to Persona workflows and templates. Persona Assistant can propose and apply configuration changes after human approval. This is a specific policy task, distinct from automatic case clearance.
- Map policy requirements
- Find configuration gaps
- Propose approved configuration changes
The published workflow requires human approval before changes. Test conflicting documents, source links, access permissions, and the resulting audit record.
RadarDocumented risk rules and location inference; AI scope unconfirmed
The fraud guide describes configurable strike-based scores and relationships between user and device identifiers. User insights infer recurring locations, with explicit uncertainty. Neither establishes a predictive payment-fraud model, a generative investigator, or an autonomous AI agent. Treat those capabilities as unconfirmed until Radar provides product-specific evidence.
- Return device, network, and location risk indicators
- Aggregate configured user/device risk history
- Supply evidence for an application-owned step-up or access decision
Validate signed results on the backend, enforce expiry, and distinguish missing evidence from a failed check. Review strike weights, linked-account effects, and block settings. Test bypass controls separately. Keep sensitive account and payment actions behind the application's own policy and audit trail.
SardinePredictive fraud + specialized risk agents
Sardine lists agents for rule help, data analysis, due diligence, screening, transaction review, and SAR generation. Each has a different evidence and approval requirement.
- Research businesses
- Investigate fraud networks
- Prepare screening and SAR work
Test each selected agent separately. Require source-linked findings, permission limits, escalation on uncertainty, and approval before high-impact actions.
SASPredictive analytics + model governance
The reviewed product material establishes anomaly detection, ML, explainability, and network analysis. It does not establish a specific autonomous AML agent included in every deployment.
- Detect unusual behavior
- Find hidden relationships
- Explain analytical flags
Ask for feature lineage, model validation, threshold change approval, and performance by customer segment.
SEONFraud models + screening and reporting assistance
SEON combines fraud models with explained screening-hit recommendations and AI-generated regulatory-report drafts. FinCEN transmission is a configured reporting workflow, not evidence that an AI agent may file without review.
- Score fraud using configured signals
- Explain screening-hit recommendations
- Draft report narratives from case evidence
Review screening recommendations and validate reports before submission. FinCEN setup and filing permissions are separate from AI preparation.
SiftEnsemble fraud models + review summaries
Sift applies AI/ML to network and customer events. ActivityIQ in Account Defense provides generative summaries of cross-session behavior. This is review assistance; independent case or filing authority is not established.
- Score payment fraud
- Detect account takeover
- Summarize suspicious sessions
Evaluate chargeback-lag effects, score reasons, policy simulation, and account-recovery outcomes. A low score is not a compliance clearance.
SocureIdentity models + RiskOS assistants and agents
Predictive models assess identity and document risk. Separately, the RiskOS AI Suite provides business research, case recommendations, rule assistance, and explanations. Socure Agent Intelligence identifies AI actors; it is a different product.
- Research businesses
- Recommend case outcomes
- Explain scores and policy changes
Test model performance by population. Confirm human review for case recommendations and approval before assisted rules or workflow changes go live.
Stripe RadarPredictive models, rule assistance, and generated risk explanations
Radar uses predictive models for transaction, merchant, and abuse risk. Radar Assistant uses an LLM to draft transaction rules. Connected-account agentic insights explain risk for investigation, while the preview website signal uses LLM analysis. Model-driven blocking and scheduled reserve actions are operational automation; the reviewed sources do not establish that a generative agent can independently publish policy, reject merchants, or move funds.
- Score payments and identify changes in fraud pressure
- Draft rules for user testing and activation
- Explain connected-account risks and preview website findings
Separate model scores from final rules and user permissions. Test allow-rule precedence, false positives, unknown outcomes, and review capacity. A user must enable an Assistant proposal. Stripe documents use of Assistant chat entries for training. Confirm preview access and retain the evidence needed for model and human decisions.
SumsubVerification 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 context
- Summarize applicant and case evidence
- Draft reviewed rules and verification-flow settings
Validate proposed changes before applying them. Keep human judgment over review outcomes and separate report preparation from regulator submission.
ThetaRayAnomaly detection + RAY investigation assistance
RAY gathers alert and customer data, compares behavior with KYC profiles, and prepares an investigation report. Its assistant summarizes documents and explains case context. Analysts retain control of final decisions.
- Assemble case evidence
- Prepare investigation reports
- Explain alert context
Test the source of each finding, missing-data handling, and analyst approval. Validate anomaly detection separately from the quality of generated reports.
TruliooIdentity intelligence + AI-assisted ownership reconstruction
Trulioo combines identity checks with UBO Discovery, which uses governed sources and LLM-assisted relationship mapping to reconstruct ownership. Unresolved evidence remains a gap for review; the reviewed scope does not establish independent compliance clearance.
- Resolve business entities and ownership relationships
- Reconstruct source-linked ownership chains
- Expose unresolved or conflicting evidence for review
Check citations, missing owners, and conflicting records before relying on a reconstructed chain. Confirm package enablement and country-specific sources.
Unit21Investigation agents + reviewed detection assistance
Unit21 combines evidence collection and narrative drafts with rule generation and backtested tuning proposals. MCP separately provides permitted read access. Analysts approve filings and rule publication.
- Alert and case evidence review
- SAR narrative and filing-package preparation
- Rule Writer drafts
- Insights and Optimization recommendations
Human approval before filing or publishing rules. MCP needs organization enablement and the user's read permissions.
VerafinDetection models + scoped agentic workers
Verafin describes sanctions and EDD review workers, plus AML cash-structuring and ACH fraud skills. Optional disposition depends on workflow and enablement. The public rollout plan does not establish universal availability.
- Review sanctions hits
- Research high-risk customers
- Triage supported AML and fraud alerts
Configure review and disposition per workflow. Confirm release and permissions for each worker and for third-party overlay deployment.
VeriffVerification models + fraud intelligence
Veriff uses AI and fraud analysis across documents, biometrics, devices, and session context. Screening adds separate data and matching functions.
- Find document manipulation
- Detect face and session anomalies
- Link suspicious sessions
Evaluate attack detection and user completion together. Ask for human-review options and clear failure reasons.
Categories are research groupings, not maturity ratings. Matching, predictive models, and agents are different technologies. Only documented product or connected capabilities enter a filtered group. Read each source for the delivery model and licensed product scope.
AI deployment checklist 0/6 reviewed
Use this checklist to collect evidence during a pilot. Checking a box does not validate a vendor. Open the playbook
























