Sift vs Forter
enterprise-custom
·enterprise-custom
Forter wins · 9–18 (20 drawn)
Agentic commerce — stories about agentic commerce in this arenaAgentic commerce
Stories about agentic commerce in this arena
Agent detection
ai-native userThe product distinguishes malicious bots from legitimate AI buying agents, so agent-driven purchases aren't blanket-blocked as fraud
weight 2 · round to ForterSiftnone0/10Evidence covers general fraud scoring, workflows, and decisions but nothing addresses distinguishing AI shopping agents from malicious bots or agentic-commerce specific handling; missing for 10: any mention of AI agent traffic detection, agent-vs-bot classification, or agentic-commerce policy/whitelisting.
Forter's agentic-orders docs show a dedicated orderType=AI_AGENT field that flags agent-driven purchases so Forter's risk engine can treat them distinctly rather than blanket-blocking, which directly targets this story. However, the evidence is entirely first-party documentation with no independent testing or detail on the underlying bot-vs-legitimate-agent classification logic. Missing for 10: independent/hands-on validation of accuracy, technical detail on how malicious bots are distinguished from legitimate agents beyond a merchant-set flag.
- [claimed-docs] “Set orderType to AI_AGENT”
- [claimed-docs] “Set orderType to AI_AGENT ... This additional data improves Forter's risk decisions and provides the merchant better reporting on agentic tr…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.forter.com/llms.txt # docs.forter.com ## Overviews - [Agentic Orders](https://docs.forter.com/age…”
Agent identity
developerPass verified agent identity — agentic-payment protocols, signed agent tokens, delegated spending scopes — into the risk decision as a first-class signal
weight 2 · round to ForterSiftnone0/10No evidence Sift supports ingesting verified agent identity, agentic-payment protocol tokens, signed agent tokens, or delegated spending scopes as risk signals; docs only describe generic user/business event and custom-field ingestion. missing for 10: any mention of agentic-commerce protocols, signed agent tokens, or delegated spending scope support as a risk signal.
Forter's agentic-orders API lets developers set orderType to AI_AGENT so the risk engine treats agent-originated traffic differently and improves decisioning/reporting, which shows agent identity is ingested as a factor. However, the evidence only shows a coarse flag, not verified signed agent tokens, delegated spending scopes, or support for specific agentic-payment protocols (e.g., AP2/Visa/Mastercard agent tokens) as first-class structured signals. missing for 10: schema/fields for signed agent credentials or delegation scopes, explicit protocol support for agentic-payment standards, independent confirmation these fields are cryptographically verified rather than self-declared.
- [claimed-docs] “Set orderType to AI_AGENT”
- [claimed-docs] “Set orderType to AI_AGENT ... This additional data improves Forter's risk decisions and provides the merchant better reporting on agentic tr…”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to ForterSiftnone0/10No evidence of an llms.txt file or agent-oriented documentation format; the docs are standard developer API references with no mention of AI-agent consumption. missing for 10: llms.txt file, agent-readable docs format, any mention of AI-agent-targeted documentation.
Forter has a confirmed live llms.txt at docs.forter.com/llms.txt (HTTP 200, forter-probe-1) listing agent-oriented doc overviews, plus explicit agent-facing docs like the MCP getting-started guide for connecting to Claude Desktop and agentic-orders docs — all markdown-served for agent consumption. Missing for 10: independent third-party confirmation that agents successfully consume the llms.txt in practice beyond the probe check.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.forter.com/llms.txt # docs.forter.com ## Overviews - [Agentic Orders](https://docs.forter.com/age…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnSift is fundamentally API-driven (REST Events/Decisions APIs, SDKs) which is inherently 'headless' and can be called from backend or automated systems, but there is no explicit evidence of a CLI, CI pipeline integration, or documented headless automation workflow. Missing for 10: explicit CI/CD examples, CLI tooling, or automation-specific documentation beyond generic API integration.
- [claimed-docs] “Sift easily integrates into your existing systems using modern REST APIs, Javascript snippet, and SDKs for iOS and Android.”
- [claimed-docs] “What actions your users are taking, usually key user lifecycle events (e.g., creating an account, placing an order, posting content to other…”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Because Sift gets smarter the more data it has about your business, you can jump start your integration by backfilling a few months worth of…”
Forter is a REST/webhook-based fraud API (order submission, status updates, webhooks, sandbox/test environment) which can technically be called from scripts or CI pipelines, and it offers an MCP server for programmatic/agentic access. However, there is no evidence of a CLI tool, CI/CD integration examples, headless testing harness, or automation-focused tooling explicitly designed for CI pipelines. missing for 10: dedicated CLI, CI/CD pipeline examples or GitHub Actions integration, headless test automation docs, explicit 'run in CI' guidance beyond generic sandbox API testing.
- [claimed-docs] “Forter has both a production and a sandbox environment for your development process.”
- [claimed-docs] “The main objective of the TEST site is to allow you to verify the integration prior to its deployment in the production environment.”
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
ai-native userConnect an agent via an official MCP server
weight 3 · round to ForterSiftnone0/10Sift is a fraud-detection SaaS with REST/Decisions APIs and SDKs, but no evidence of an official MCP server for agent connectivity. missing for 10: any mention of MCP, agent integration protocol, or official MCP server endpoint.
- [claimed-docs] “Sift easily integrates into your existing systems using modern REST APIs, Javascript snippet, and SDKs for iOS and Android.”
Forter documents an official MCP server enabling AI agents to review decisions, manage disputes, and update policies via natural language, with a getting-started guide for connecting to Claude Desktop. missing for 10: independent/third-party corroboration of real-world MCP usage and broader client compatibility beyond Claude Desktop.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
ai-native userUse an official CLI
weight 2 · round drawnSiftnone0/10Sift's evidence pack covers REST APIs, SDKs, JS snippet, and Decisions/Workflows APIs, but no official CLI tool is mentioned anywhere in docs or community sources.
Forternone0/10Evidence shows Forter offers REST APIs, webhooks, and an MCP server for conversational AI workflows, but no official CLI tool is documented anywhere in the evidence pack.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
ai-native userDrive the product through a documented public API
weight 3 · round to ForterSift documents REST APIs (Events, Decisions, Score, Workflows) that let developers programmatically drive fraud scoring and decisioning, which supports an AI-native integration story. However, this is a traditional fraud-ops API, not one purpose-built for AI agent orchestration, and there's no evidence of agent-specific tooling like an MCP server, function-calling schemas, or SDKs for LLM agents. missing for 10: agent-oriented API framing (e.g., MCP server, function-calling schema), independent hands-on validation of API usability beyond one user noting confusing docs.
- [claimed-docs] “Sift easily integrates into your existing systems using modern REST APIs, Javascript snippet, and SDKs for iOS and Android.”
- [claimed-docs] “What actions your users are taking, usually key user lifecycle events (e.g., creating an account, placing an order, posting content to other…”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Sift represents this risk with a score between 0 and 100, where risky events have higher scores.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [community] “Early user feedback: 'I have been integrating it for a day or so. The documentation is slightly confusing and they've had a few minor bugs i…”
Forter publishes a documented public REST API (Order v3, Order Status, Evidence API, webhooks) with sandbox/production environments, giving AI-native users a clear path to drive the product programmatically; this is reinforced by an official MCP server enabling natural-language/agentic control of decisions and disputes. Missing for 10: independent/hands-on corroboration beyond vendor docs, and more detail on auth/rate limits or SDK coverage.
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “Inform of updates to the status of an order, including payment authorization, fulfillment, shipping details, and compensation granted.”
- [claimed-docs] “Webhooks provide a way to configure Forter to send real-time notifications to your web store server or another service (ERP/OMS) whenever ce…”
- [claimed-docs] “Forter has both a production and a sandbox environment for your development process.”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.forter.com/llms.txt # docs.forter.com ## Overviews - [Agentic Orders](https://docs.forter.com/age…”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
ai-native userBuild against official SDKs
weight 2 · round to ForterSiftnone0/10Evidence shows Sift has REST APIs, JS snippet, and mobile SDKs for iOS/Android, but there's no mention of SDKs oriented toward AI-native development (e.g., LLM/agent SDKs, official Python/Node/AI framework SDKs). This story concerns AI-native developer tooling, which is not addressed anywhere in the pack. missing for 10: any evidence of AI-agent-oriented SDKs, LLM integration libraries, or agent framework support.
Forter provides extensive REST API references (Order v3, Order Status, Evidence API, webhooks), a sandbox/production environment, and even a documented MCP server for agentic workflows, which together give an AI-native developer solid material to build against. However, none of the evidence explicitly names or links to official client-language SDKs (e.g., Python/Node/Java packages) — only API/reference docs and an MCP integration are shown. Missing for 10: explicit official SDK packages/libraries, versioned SDK release notes, and independent corroboration of SDK usage in production.
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “Inform of updates to the status of an order, including payment authorization, fulfillment, shipping details, and compensation granted.”
- [claimed-docs] “Webhooks provide a way to configure Forter to send real-time notifications to your web store server or another service (ERP/OMS) whenever ce…”
- [claimed-docs] “Forter has both a production and a sandbox environment for your development process.”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
ai-native userSubscribe to events via webhooks
weight 2 · round to ForterSiftnone0/10Sift's documented integration model is inbound REST APIs (Events, Decisions, Score, Workflows) for sending data to Sift, not outbound webhooks for subscribing to events from Sift. No evidence pack item mentions webhook subscriptions or event push notifications to external consumers.
Forter documents a dedicated webhooks system for real-time event notifications (order status, chargeback forwarding, dispute webhooks) that can be configured to notify external services, directly matching the subscribe-to-events story; this is a well-documented first-party capability. missing for 10: independent/hands-on corroboration of webhook reliability, and a comprehensive list of subscribable event types/payload schema beyond the examples shown.
- [claimed-docs] “Webhooks provide a way to configure Forter to send real-time notifications to your web store server or another service (ERP/OMS) whenever ce…”
- [claimed-docs] “Inform of updates to the status of an order, including payment authorization, fulfillment, shipping details, and compensation granted.”
- [claimed-docs] “Webhook-based forwarding enables: - Real-time claim ingestion - Faster transaction matching - Immediate eligibility assessment for dispute h…”
- [claimed-docs] “How to provide Forter access to your Stripe Dispute Webhooks.”
- [claimed-docs] “Webhook-based forwarding enables: Real-time claim ingestion - Faster transaction matching - Immediate eligibility assessment for dispute han…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to ForterSiftnone0/10Sift provides risk scores and rule-based Workflows/Decisions derived from ML models, but there is no evidence of AI-generated natural-language insights or suggestions surfaced to users inside a product UI—everything is API-driven scoring and automation rather than generative/agentic insight delivery. Missing for 10: any documented AI-generated narrative insights, recommendations, or conversational/agentic assistant surfaced in-product, and any independent confirmation of such a feature.
- [claimed-docs] “Sift represents this risk with a score between 0 and 100, where risky events have higher scores.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
Forter provides an AI-driven recommendation engine that suggests additional evidence to bolster dispute win rates and a 'team of Forter Agents' concept, plus MCP-enabled natural language interactions for reviewing decisions and managing disputes. This shows some AI-generated insight/suggestion capability embedded in the product, but evidence is thin on broader analytics/insights (e.g., fraud trend explanations, risk scoring rationale) beyond the dispute-evidence use case. Missing for 10: broader in-product AI insights beyond dispute evidence suggestions, independent/hands-on corroboration of the recommendation engine's quality, and detail on what other 'Forter Agents' actually surface to users.
- [claimed-docs] “our recommendation engine will suggest additional evidence to add to your dispute to bolster your win rate.”
- [claimed-docs] “Once chargebacks are ingested into Forter, our recommendation engine will suggest additional evidence to add to your dispute to bolster your…”
- [claimed-docs] “Meet your new team of Forter Agents, so you can spend more time on what matters most.”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to ForterSift's Workflows feature is described as a 'rules automation platform' that runs risk-based decisions autonomously in real time on incoming events, which fits the general notion of background automations. However, this is traditional rules/ML-based fraud automation, not an AI-native/agentic automation-building experience tailored to an 'AI-native user.' Missing for 10: evidence of AI-native automation authoring (e.g., natural-language or agent-driven workflow creation), broader use-case automations beyond fraud decisioning, and independent confirmation of autonomous operation quality.
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [claimed-docs] “Learn to set up custom Decisions, like Ban Account or Cancel Order, that are connected to real business actions in your backend.”
Forter's fraud automation (webhooks, chargeback forwarding, evidence recommendation, MCP for reviewing decisions/managing disputes) provides background automation of fraud/dispute workflows, and the MCP server lets AI agents trigger actions, but this is not framed as user-configurable 'set up automations that run autonomously' in the sense of scheduled/triggered workflows the AI-native user builds themselves. missing for 10: explicit user-facing automation builder/scheduler, evidence of autonomous background runs initiated by the user rather than reactive webhook/event responses, and independent confirmation of real-world autonomous operation.
- [claimed-docs] “Webhooks provide a way to configure Forter to send real-time notifications to your web store server or another service (ERP/OMS) whenever ce…”
- [claimed-docs] “Webhook-based forwarding enables: - Real-time claim ingestion - Faster transaction matching - Immediate eligibility assessment for dispute h…”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Once chargebacks are ingested into Forter, our recommendation engine will suggest additional evidence to add to your dispute to bolster your…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to ForterSiftnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Forter's marketing mentions a 'team of Forter Agents' suggesting built-in AI-driven automation, but the evidence pack gives no detail on how a user interacts with or delegates tasks to such an assistant inside the product UI. The only detailed AI-interaction evidence (MCP) is about connecting external assistants like Claude Desktop to Forter, not a built-in assistant. Missing for 10: documentation of an in-product conversational assistant UI, examples of task delegation, and how 'Forter Agents' are invoked/configured.
- [claimed-docs] “Meet your new team of Forter Agents, so you can spend more time on what matters most.”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
ai-native userOperate the product with natural-language commands
weight 2 · round to ForterSiftnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Forter documents a first-party MCP server enabling natural-language commands to review decisions, manage disputes, and update policies, with a getting-started guide for connecting to Claude Desktop for conversational workflows. Missing for 10: independent/hands-on corroboration beyond vendor docs, and broader coverage of which actions are NL-operable vs API-only.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.forter.com/llms.txt # docs.forter.com ## Overviews - [Agentic Orders](https://docs.forter.com/age…”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnSiftnone0/10Evidence shows REST/Decisions/Events API docs exist but nothing describes an interactive API reference with runnable examples (e.g., embedded sandbox, try-it console). Missing for 10: interactive API explorer, runnable code examples, sandbox/try-it functionality.
Forternone0/10The evidence pack shows Forter has API reference documentation (order-v3, order-status, webhooks, environments) but nothing indicates the docs are interactive with runnable/try-it examples—no mention of an embedded API console, code sandbox, or 'try it' functionality typical of interactive API references.
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnSiftnone0/10Evidence shows Sift has REST APIs (Events, Decisions, Score, Workflows) with docs, but no mention of a downloadable OpenAPI spec or other machine-readable API schema anywhere in the pack.
- [claimed-docs] “Sift easily integrates into your existing systems using modern REST APIs, Javascript snippet, and SDKs for iOS and Android.”
- [claimed-docs] “What actions your users are taking, usually key user lifecycle events (e.g., creating an account, placing an order, posting content to other…”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
Forternone0/10Forter publishes REST API reference docs (order-v3, order-status, webhooks) but none of the evidence mentions a downloadable OpenAPI/Swagger spec or machine-readable API definition file; the llms.txt probe lists doc pages, not an API spec.
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “Inform of updates to the status of an order, including payment authorization, fulfillment, shipping details, and compensation granted.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.forter.com/llms.txt # docs.forter.com ## Overviews - [Agentic Orders](https://docs.forter.com/age…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to ForterSiftnone0/10No evidence pack item mentions a sandbox environment, test mode, or any way to test Sift integrations without touching production data; all docs reference live Events/Decisions/Score APIs. Missing for 10: sandbox/test environment docs, test API keys or staging mode, any mention of separating test vs production data.
Forter explicitly documents both production and sandbox (TEST) environments, stating the sandbox's purpose is to verify integration before production deployment, allowing testing without touching production data. Missing for 10: no independent/hands-on corroboration of sandbox behavior or details on sandbox data parity/limitations.
- [claimed-docs] “Forter has both a production and a sandbox environment for your development process.”
- [claimed-docs] “The main objective of the TEST site is to allow you to verify the integration prior to its deployment in the production environment.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnSiftnone0/10Evidence shows Sift has REST APIs, SDKs, and docs but no mention of API versioning scheme or a documented deprecation policy anywhere in the pack. Missing for 10: explicit API versioning documentation, deprecation policy or changelog, migration timelines for breaking changes.
Forternone0/10Evidence shows versioned API endpoints (e.g. order-v3) and sandbox/production environments, but there is no documentation of a versioning scheme, version support lifecycle, or a deprecation policy anywhere in the pack.
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “Forter has both a production and a sandbox environment for your development process.”
- [claimed-docs] “The main objective of the TEST site is to allow you to verify the integration prior to its deployment in the production environment.”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to SiftSift documents backfilling months of historical data as a bulk-load capability, but there is no evidence of a dedicated bulk API for batch-scoring, batch-deciding, or bulk-updating many items at once (e.g., no batch endpoint documentation). Missing for 10: explicit bulk/batch API documentation, batch decision or batch scoring examples, and any hands-on evidence of bulk workflows being used successfully.
- [claimed-docs] “Because Sift gets smarter the more data it has about your business, you can jump start your integration by backfilling a few months worth of…”
- [claimed-docs] “What actions your users are taking, usually key user lifecycle events (e.g., creating an account, placing an order, posting content to other…”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
Forternone0/10Forter's docs describe per-order/per-dispute APIs (Order v3, Evidence API, webhooks, MCP natural-language actions) but no evidence of a bulk/batch endpoint or mechanism for acting across many items simultaneously. The axis is applicable (merchants would plausibly want bulk dispute/evidence submission or bulk order review), but no such capability is documented.
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “Save time and effort by using our Evidence API endpoint to automatically send post-order evidence for chargeback disputes.”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to ForterSiftdisputedcontradicted5/10Sift's docs clearly describe a 'Workflows' rules automation platform that triggers real-time Decisions (Ban Account, Cancel Order) based on event risk scores, directly matching the story. However, a Sift co-founder is quoted saying 'we do not have any rules in our product... rules are rather easy for fraudsters to circumvent,' directly contradicting the vendor's later rules-automation framing. missing for 10: reconciliation of this contradiction and independent hands-on confirmation that customer-defined Workflow rules reliably trigger automated actions in production.
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Learn to set up custom Decisions, like Ban Account or Cancel Order, that are connected to real business actions in your backend.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [community] “CEO explains no-rules ML approach: 'we do not have any rules in our product... rules are rather easy for fraudsters to circumvent, and they …”
Forter supports event-driven automation via webhooks (real-time notifications on events like disputes/chargebacks) and configurable decision behaviors (e.g., Auto Invoice triggering capture), and its MCP interface lets an AI agent perform actions like reviewing decisions or updating policies via natural language. However, there is no evidence of a user-facing rule-definition engine (e.g., 'if X then Y' conditions) that AI-native users can author themselves. Missing for 10: explicit rule-builder/conditional logic UI or API, examples of user-defined trigger-action pairs beyond fixed webhook events and preset decision toggles.
- [claimed-docs] “Webhooks provide a way to configure Forter to send real-time notifications to your web store server or another service (ERP/OMS) whenever ce…”
- [claimed-docs] “If the Auto Invoice option is set to YES, then the payment capture amount operation is executed and order is placed”
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Webhook-based forwarding enables: - Real-time claim ingestion - Faster transaction matching - Immediate eligibility assessment for dispute h…”
Chargeback disputes — stories about chargeback disputes in this arenaChargeback disputes
Stories about chargeback disputes in this arena
Guarantee
finance leadShift fraud liability to the vendor — a chargeback guarantee that reimburses approved-then-disputed orders, with clear coverage terms
weight 2 · round drawnSiftnone0/10No evidence anywhere in the pack mentions a chargeback guarantee, liability shift, reimbursement for approved-then-disputed orders, or coverage terms — Sift is documented only as a fraud-scoring/risk-decision API, not an insurance-backed guarantee product.
Forternone0/10The evidence pack details dispute automation, evidence submission, webhook forwarding, and win-rate optimization tools, but none of it documents an actual chargeback guarantee, reimbursement mechanism, or liability-shift terms — the core of this finance-lead story. Missing for 10: explicit guarantee/reimbursement policy language, coverage terms, or liability-shift contract details.
- [claimed-docs] “Webhook-based forwarding enables: - Real-time claim ingestion - Faster transaction matching - Immediate eligibility assessment for dispute h…”
- [claimed-docs] “our recommendation engine will suggest additional evidence to add to your dispute to bolster your win rate.”
- [claimed-docs] “Once chargebacks are ingested into Forter, our recommendation engine will suggest additional evidence to add to your dispute to bolster your…”
- [claimed-docs] “Save time and effort by using our Evidence API endpoint to automatically send post-order evidence for chargeback disputes.”
- [claimed-docs] “Fight fraud, increase approvals, reduce chargebacks”
- [claimed-docs] “Automate disputes, streamline operations, improve win rates”
Outcome reporting
finance leadSee the numbers that matter — dispute rate, false-positive rate, approval-rate lift, review workload — and export them for the board
weight 2 · round drawnSiftnone0/10Evidence covers APIs, scoring, workflows, and general product sentiment, but there is no mention of finance-lead dashboards, dispute-rate/false-positive/approval-lift metrics, review workload reporting, or board-ready export capability. missing for 10: dispute-rate and false-positive-rate metrics reporting, approval-rate lift analytics, review workload/queue metrics, export or reporting functionality for finance/board consumption.
Forternone0/10The evidence pack covers APIs, webhooks, MCP, and dispute automation but contains no mention of a reporting dashboard, board-level metrics (dispute rate, false-positive rate, approval-rate lift, review workload), or any export/reporting feature aimed at finance leads. Only a vague reference to 'better reporting on agentic traffic' exists, which does not address the specific KPIs in the story.
- [claimed-docs] “Set orderType to AI_AGENT ... This additional data improves Forter's risk decisions and provides the merchant better reporting on agentic tr…”
Representment
ops userChargeback responses are automated — evidence compiled from order, delivery, and session data and submitted to the issuer without manual copy-paste
weight 3 · round to ForterSiftnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Forter documents automated evidence workflows: chargebacks are ingested via webhook forwarding, matched to transactions, and a recommendation engine suggests additional evidence, plus an Evidence API to 'automatically send post-order evidence for chargeback disputes' without manual copy-paste of transaction data. However, the evidence is described as 'suggested' by a recommendation engine rather than fully autonomous compilation and submission, and there's no explicit mention of session data being incorporated into evidence packages. Missing for 10: explicit confirmation that session-level data is included in compiled evidence, and independent/hands-on validation that submission is fully automatic without ops review step.
- [claimed-docs] “Webhook-based forwarding enables: - Real-time claim ingestion - Faster transaction matching - Immediate eligibility assessment for dispute h…”
- [claimed-docs] “our recommendation engine will suggest additional evidence to add to your dispute to bolster your win rate.”
- [claimed-docs] “Once chargebacks are ingested into Forter, our recommendation engine will suggest additional evidence to add to your dispute to bolster your…”
- [claimed-docs] “Save time and effort by using our Evidence API endpoint to automatically send post-order evidence for chargeback disputes.”
- [claimed-docs] “Map Stripe's PaymentIntent ID (the value that starts with pi_) to the processorTransactionId field ... This is required to map the dispute b…”
Fraud agent access — stories about fraud agent access in this arenaFraud agent access
Stories about fraud agent access in this arena
Agent operations
ai-native userAn agent can read my fraud posture and manage rules and lists programmatically — propose a velocity rule, update a blocklist — with human approval gates
weight 3 · round to ForterSiftnone0/10Evidence shows REST/Decisions/Workflows APIs for events, scoring, and rules automation, but nothing describes an AI agent reading fraud posture or proposing/updating rules and lists with a human-approval workflow — this is a generic developer API story, not an agent-access pattern. missing for 10: any mention of AI agent integration, agentic rule-proposal workflow, or human-approval gate mechanism tied to programmatic rule/list changes.
- [claimed-docs] “Sift easily integrates into your existing systems using modern REST APIs, Javascript snippet, and SDKs for iOS and Android.”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
Forter documents an official MCP server that lets an AI system 'review decisions, manage disputes, or update policies through natural language commands' and can connect to Claude Desktop for conversational workflows, which supports agentic read/manage access to fraud posture. However, there is no explicit documentation of proposing a velocity rule, updating a blocklist, or any human-in-the-loop approval gate mechanism for these programmatic changes. Missing for 10: explicit velocity-rule/blocklist management examples, documented approval-gate workflow, and independent/hands-on corroboration of MCP write actions.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
Agent triage
ai-native userAn agent can work the review queue — pull flagged cases with their context, summarize the evidence, and recommend a decision for a human to confirm
weight 2 · round to ForterSiftnone0/10Sift has Review Queues and REST/Decisions APIs for humans to review flagged cases (sift-docs-12, sift-docs-3), and community evidence confirms a human-in-the-loop review model (sift-comm-4), but there is no evidence of an AI agent programmatically pulling flagged cases, summarizing evidence, or recommending decisions for human confirmation.
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [community] “Sift Science founder on false positives: 'Most of our customers review each user we flag, and have a human make a final go/no-go decision ab…”
Forter's MCP server explicitly lets an AI agent 'perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural language commands' via Claude Desktop, showing agent access to review/decision workflows. However, there is no explicit documentation of pulling a flagged-case queue, summarizing evidence, or producing a recommendation for human confirmation as a distinct workflow. missing for 10: explicit queue-pulling UI/API for flagged cases, evidence-summarization output, human-confirm approval step.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
Builtin ai
risk analystThe product ships its own AI assistant — natural-language queries over my fraud data, drafted rules, investigation summaries — built into the console
weight 2 · round to ForterSiftnone0/10The evidence pack covers Sift's APIs, scoring, workflows/rules automation, and review queues, but there is no mention of any built-in AI assistant, natural-language query capability, drafted rules generation, or investigation summary generation in the console. Missing for 10: any documentation or mention of a natural-language/AI assistant feature, evidence of NL-to-query capability, evidence of AI-drafted rules or summaries.
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
Forter markets 'Forter Agents' and ships an MCP server letting external AI systems (e.g., Claude Desktop) issue natural-language commands to review decisions, manage disputes, or update policies, which gestures at the AI-assistant theme. However, the evidence never describes a native, embedded console assistant with NL querying over fraud data, rule drafting, or investigation summaries — the MCP approach is an integration layer for external AI clients rather than a first-party in-console assistant. Missing for 10: concrete documentation of a built-in console chat/assistant UI, evidence of drafted-rule generation, and investigation-summary generation features.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Meet your new team of Forter Agents, so you can spend more time on what matters most.”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
Fraud surfaces — stories about fraud surfaces in this arenaFraud surfaces
Stories about fraud surfaces in this arena
Abuse coverage
risk analystProtection extends beyond checkout — account takeover, fake account creation, promo and policy abuse are scored and managed in the same system
weight 2 · round to SiftDocs explicitly cover multiple fraud surfaces beyond checkout — account takeover ('Block unauthorized access in real time'), fake account creation ('Stop fraudulent signups at the door'), and abuse-specific scoring ('fight multiple types of fraud at once... add an abuse-specific risk score'), all managed within the same Workflows/Decisions/Review Queue system. Missing for 10: dedicated documentation or case study specifically on promo/policy abuse handling, and independent hands-on verification of multi-surface scoring in one unified dashboard.
- [claimed-docs] “Block unauthorized access in real time.”
- [claimed-docs] “Stop fraudulent signups at the door.”
- [claimed-docs] “Want to fight multiple types of fraud at once? Learn how to add an abuse-specific risk score so that you can easily do so.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [claimed-docs] “Learn to set up custom Decisions, like Ban Account or Cancel Order, that are connected to real business actions in your backend.”
Forter's marketing copy explicitly claims to 'Stop ATO, block fake accounts, protect account integrity' alongside its checkout/fraud-decision APIs, indicating account-takeover and fake-account protection live in the same platform as order-level fraud scoring. However, there is no documentation of promo abuse or policy abuse detection/management, and no detail on how ATO/fake-account signals are scored or surfaced to analysts beyond a single marketing line. Missing for 10: dedicated docs/API for promo abuse and policy abuse detection, analyst-facing workflow/management details for ATO and fake-account cases beyond marketing claims.
- [claimed-docs] “Stop ATO, block fake accounts, protect account integrity”
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “Fight fraud, increase approvals, reduce chargebacks”
Integrations
ops userThere are maintained integrations for my commerce stack — Shopify, Salesforce Commerce, BigCommerce, and the major PSPs — not just a raw API
weight 2 · round to ForterSiftnone0/10Evidence shows only generic REST API, JS snippet, and mobile SDKs — no mention of maintained Shopify, Salesforce Commerce, BigCommerce, or PSP-specific integrations. Everything points to a raw API/SDK integration model, not prebuilt commerce-platform connectors.
- [claimed-docs] “Sift easily integrates into your existing systems using modern REST APIs, Javascript snippet, and SDKs for iOS and Android.”
- [claimed-docs] “What actions your users are taking, usually key user lifecycle events (e.g., creating an account, placing an order, posting content to other…”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
Evidence confirms a maintained Shopify integration (quickstart-shopify.md) and Stripe dispute webhook support, indicating some pre-built commerce/PSP connectors exist. However, there is no evidence of maintained integrations for Salesforce Commerce, BigCommerce, or other major PSPs (Adyen, Braintise, PayPal, etc.), leaving the breadth of the 'commerce stack' claim largely unsubstantiated. missing for 10: documented Salesforce Commerce Cloud integration, BigCommerce integration, coverage of additional major PSPs beyond Stripe, and any partner/marketplace integration directory confirming maintenance status.
- [claimed-docs] “You implement: Nothing - Forter handles everything”
- [claimed-docs] “How to provide Forter access to your Stripe Dispute Webhooks.”
- [claimed-docs] “Map Stripe's PaymentIntent ID (the value that starts with pi_) to the processorTransactionId field ... This is required to map the dispute b…”
Psp coverage
developerUse the product across whatever payment stack I run — multiple PSPs, gateways, and platforms — rather than being locked to one processor's rails
weight 3 · round drawnSift's architecture (generic REST Events/Decisions API, JS snippet, SDKs) is inherently processor-agnostic — it ingests events from any application regardless of which PSP or gateway processes the payment, rather than being tied to one processor's rails. However, there is no explicit documentation or case evidence naming specific PSPs/gateways/platforms it integrates with or confirming multi-processor deployments in practice. Missing for 10: explicit multi-PSP/gateway integration examples, named partner processors, or customer testimony confirming cross-stack usage.
- [claimed-docs] “Sift easily integrates into your existing systems using modern REST APIs, Javascript snippet, and SDKs for iOS and Android.”
- [claimed-docs] “What actions your users are taking, usually key user lifecycle events (e.g., creating an account, placing an order, posting content to other…”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Custom events and fields describe user actions not captured by the supported events in our Events API.”
Forter is payment-agnostic in principle (works off order/checkout data, not tied to a specific processor's rails), and evidence shows Stripe-specific dispute webhook integration plus a Shopify quickstart, implying multi-platform support. However there is no explicit documentation enumerating support across multiple PSPs/gateways beyond Stripe and Shopify, nor guidance for other major processors (Adyen, Braintree, PayPal, etc.). missing for 10: explicit list/documentation of supported PSPs and gateways beyond Stripe/Shopify, evidence of platform-agnostic integration guides for other processors, independent confirmation of multi-PSP deployments.
- [claimed-docs] “How to provide Forter access to your Stripe Dispute Webhooks.”
- [claimed-docs] “Map Stripe's PaymentIntent ID (the value that starts with pi_) to the processorTransactionId field ... This is required to map the dispute b…”
- [claimed-docs] “You implement: Nothing - Forter handles everything”
- [claimed-docs] “Forter has both a production and a sandbox environment for your development process.”
Model transparency — stories about model transparency in this arenaModel transparency
Stories about model transparency in this arena
Explainability
risk analystEvery score comes with its top risk factors — why this transaction looks risky — not just an opaque number
weight 3 · round drawnSiftnone0/10The evidence pack documents Sift's 0–100 risk score, Workflows, and Decisions APIs, but nowhere mentions score explanations, reason codes, or top contributing risk factors accompanying each score. Missing for 10: any documentation of explainability/reason-code output, feature-importance breakdowns, or examples of a score being paired with human-readable risk drivers.
- [claimed-docs] “Sift represents this risk with a score between 0 and 100, where risky events have higher scores.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
Model evaluation
finance leadMeasure the model itself — precision and recall on my traffic, shadow-mode trials of new models or rules before they take over decisions
weight 2 · round drawnSiftnone0/10Evidence covers scoring, workflows, decisions, and events APIs, but there is no mention of precision/recall metrics on the customer's own traffic, model performance measurement, or shadow-mode trialing of new models/rules before they go live. missing for 10: precision/recall measurement tooling, shadow-mode/challenger model testing, any model transparency reporting for finance/business stakeholders.
Forternone0/10No evidence of model-level metrics (precision/recall), shadow-mode trials, or A/B testing of models/rules before rollout; evidence covers order decisioning, webhooks, disputes, and agentic orders but nothing about model performance measurement or staged rollout tooling for finance leads.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnSift's docs show extensive REST APIs covering events, decisions, scoring, and even a Workflows API for automation, indicating broad programmatic access mirroring core UI functions (sift-docs-1,2,3,5,6,12). However, there's no explicit evidence that Review Queues or full workflow configuration UI actions are fully API-equivalent, and no independent confirmation of complete UI/API parity. missing for 10: explicit parity claim for Review Queues and workflow UI configuration, independent verification of full CRUD API coverage matching every console action.
- [claimed-docs] “Sift easily integrates into your existing systems using modern REST APIs, Javascript snippet, and SDKs for iOS and Android.”
- [claimed-docs] “What actions your users are taking, usually key user lifecycle events (e.g., creating an account, placing an order, posting content to other…”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Sift represents this risk with a score between 0 and 100, where risky events have higher scores.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
Forter exposes core actions via API/webhooks (order decisions, order status, evidence submission, chargeback forwarding) and an MCP server that lets AI agents review decisions, manage disputes, and update policies via natural language, suggesting broad API/agent coverage of UI functions. However, there is no explicit documentation stating full feature parity between the UI dashboard and API/MCP, and some UI-only configuration (e.g., policy setup screens, analytics dashboards) isn't shown as API-accessible. Missing for 10: explicit parity statement, evidence that every UI configuration/reporting feature is also API-exposed, independent confirmation of MCP completeness.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Set orderType to AI_AGENT”
- [claimed-docs] “Save time and effort by using our Evidence API endpoint to automatically send post-order evidence for chargeback disputes.”
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “Inform of updates to the status of an order, including payment authorization, fulfillment, shipping details, and compensation granted.”
- [claimed-docs] “Webhooks provide a way to configure Forter to send real-time notifications to your web store server or another service (ERP/OMS) whenever ce…”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnSiftnone0/10Sift is a fraud-detection API platform; evidence covers sending events/data into Sift via REST API, scoring, workflows, but there is no mention of exporting or bulk-downloading customer data out of Sift in open formats, nor any data-portability/export feature. missing for 10: any documented data export/download capability, open-format export (CSV/JSON dumps), or account data portability tooling.
Forternone0/10Forter is a fraud-detection/risk B2B API platform; no evidence of any end-user data export feature or open-format data portability for merchants or consumers to 'leave' with their data. Missing for 10: any documented data export tool, open format (CSV/JSON) export capability, or account-closure data portability process.
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnSiftnone0/10No evidence in the pack mentions data residency, regional storage options, or geographic control over where Sift stores customer data; one community comment even notes hesitation about sending data to Sift without clarity on compliance handling. Missing for 10: any documentation of region selection, data residency options, or compliance certifications addressing storage location.
- [community] “Potential customer notes hesitation: reservations about sending personal user data to an aggregator that would then require legal review for…”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnSiftnone0/10Sift is a fraud-detection platform whose business model relies on ingesting user behavioral data to train its ML risk models; no evidence pack item mentions any opt-out, data-training-exclusion policy, or AI-training-specific privacy controls for end users. Missing for 10: any documentation of an opt-out mechanism, training-data exclusion policy, or user-facing privacy control preventing model training use.
ai-native userControl data retention and deletion
weight 2 · round drawnSiftnone0/10Sift is a fraud-detection API/platform, and the evidence pack contains no documentation of data retention controls, deletion APIs, or configurable data lifecycle policies for users. One community comment (sift-comm-3) even flags unresolved privacy/legal review concerns about sending personal data to Sift, but this is not concrete evidence of a retention/deletion mechanism either way. missing for 10: any documentation of data retention settings, a deletion/right-to-be-forgotten API, or data lifecycle/export controls.
- [community] “Potential customer notes hesitation: reservations about sending personal user data to an aggregator that would then require legal review for…”
Residency compliance — stories about residency compliance in this arenaResidency compliance
Stories about residency compliance in this arena
Residency
ops userControl where fraud data lives and how long it's kept — regional residency options and retention controls that survive a privacy review
weight 2 · round drawnSiftnone0/10No evidence pack items discuss regional data residency, data hosting locations, retention periods, or compliance/privacy review controls; one comment even notes a prospective customer's hesitation about privacy/legal review with no resolution shown. Missing for 10: any documentation of regional hosting/data residency options, retention/configurable deletion policies, or compliance certifications addressing privacy review.
- [community] “Potential customer notes hesitation: reservations about sending personal user data to an aggregator that would then require legal review for…”
Sca
developerEuropean traffic is routed intelligently through SCA — 3DS triggered when required or risky, exemptions requested when safe — to protect both compliance and conversion
weight 2 · round drawnSiftnone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Review queues — stories about review queues in this arenaReview queues
Stories about review queues in this arena
Case review
risk analystFlagged transactions land in a review queue that shows the full context — customer history, signals, similar cases — so I can decide quickly and consistently
weight 3 · round to SiftSift documents Review Queues as a product feature alongside Workflows, and community evidence confirms human analysts do review flagged users to make final decisions, supporting the general workflow. However, there is no evidence detailing the review queue UI showing customer history, similar cases, or signal context in one view. missing for 10: documentation/screenshots of review queue UI showing customer history and similar cases, evidence of consolidated signal context, independent hands-on confirmation of queue usability.
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [community] “Sift Science founder on false positives: 'Most of our customers review each user we flag, and have a human make a final go/no-go decision ab…”
Feedback loop
risk analystMy review decisions and confirmed fraud outcomes feed back into the model and rules, so the system learns from every case we work
weight 2 · round to SiftSift's Decisions API explicitly captures business actions like 'block due to fraud' or 'cancel due to chargeback' and feeds them back to Sift, and docs state Sift 'gets smarter the more data it has,' supporting a feedback loop from confirmed outcomes into the model. Review Queues and Workflows are documented as connected to decisions, and a founder note confirms customers commonly have analysts make final go/no-go calls that presumably feed Decisions API. Missing for 10: explicit documentation that individual analyst review-queue verdicts (not just automated decisions) are looped back per-case to retrain the model, and any detail on how confirmed fraud outcomes update rules/workflows specifically.
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Because Sift gets smarter the more data it has about your business, you can jump start your integration by backfilling a few months worth of…”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [community] “Sift Science founder on false positives: 'Most of our customers review each user we flag, and have a human make a final go/no-go decision ab…”
Forter's docs show data flowing back to Forter post-decision (order status updates including compensation granted, chargeback/dispute webhook ingestion, Evidence API) which implies outcome data reaches Forter's systems, but there is no explicit documentation that a risk analyst's manual review decisions or confirmed-fraud outcomes are used to retrain models or update rules. Missing for 10: explicit description of a feedback/learning loop tying analyst review outcomes to model or rule updates, and any mention of an analyst review queue at all.
- [claimed-docs] “Inform of updates to the status of an order, including payment authorization, fulfillment, shipping details, and compensation granted.”
- [claimed-docs] “Webhook-based forwarding enables: - Real-time claim ingestion - Faster transaction matching - Immediate eligibility assessment for dispute h…”
- [claimed-docs] “Webhook-based forwarding enables: Real-time claim ingestion - Faster transaction matching - Immediate eligibility assessment for dispute han…”
- [claimed-docs] “How to provide Forter access to your Stripe Dispute Webhooks.”
- [claimed-docs] “Map Stripe's PaymentIntent ID (the value that starts with pi_) to the processorTransactionId field ... This is required to map the dispute b…”
- [claimed-docs] “Save time and effort by using our Evidence API endpoint to automatically send post-order evidence for chargeback disputes.”
Team workflows
ops userReview work is a team workflow — assignment, escalation, SLAs, and a decision audit trail that shows who approved what and why
weight 2 · round to SiftSift documents Review Queues and Workflows for human review, plus a Decisions API that logs business actions like approve/ban/cancel tied to real events, which supports a basic audit trail; a founder comment also confirms a human-in-the-loop review pattern ('have a human make a final go/no-go decision'). However, there's no evidence of explicit team-workflow features like assignment routing, escalation paths, or SLA tracking. missing for 10: assignment/routing mechanics, escalation workflows, SLA timers/tracking, explicit 'who approved what and why' UI/reporting beyond raw decision logs.
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Learn to set up custom Decisions, like Ban Account or Cancel Order, that are connected to real business actions in your backend.”
- [community] “Sift Science founder on false positives: 'Most of our customers review each user we flag, and have a human make a final go/no-go decision ab…”
Forternone0/10The evidence pack covers order decisioning, webhooks, chargeback/dispute automation, and AI-agent/MCP integrations, but contains no mention of a human team review workflow with case assignment, escalation rules, SLAs, or an approval audit trail for ops reviewers. missing for 10: case assignment/queue management, escalation rules, SLA tracking, and a decision audit trail showing reviewer approvals and rationale.
Risk scoring — stories about risk scoring in this arenaRisk scoring
Stories about risk scoring in this arena
Custom signals
developerFeed the model my own signals — device fingerprints, behavioral data, custom metadata — so scoring reflects my business, not just network defaults
weight 2 · round to SiftSift's docs clearly support ingesting custom events, custom fields, session/device signals, and business action data via Events/Decisions APIs, and scoring incorporates this custom data plus historical backfill to tailor risk to the business rather than generic network defaults. Missing for 10: independent hands-on verification of custom-field scoring impact and explicit device-fingerprint API documentation beyond general SDK mentions.
- [claimed-docs] “What actions your users are taking, usually key user lifecycle events (e.g., creating an account, placing an order, posting content to other…”
- [claimed-docs] “What actions your business is taking in response to users (e.g., approve an order, block and event due to fraud, cancel order due to chargeb…”
- [claimed-docs] “Because Sift gets smarter the more data it has about your business, you can jump start your integration by backfilling a few months worth of…”
- [claimed-docs] “Custom events and fields describe user actions not captured by the supported events in our Events API.”
- [claimed-docs] “When users are anonymous for parts or all of their experience on your site, we provide a special `session_id` field in the JS Snippet and Ev…”
- [claimed-docs] “Sift represents this risk with a score between 0 and 100, where risky events have higher scores.”
Forter's Order API accepts order data and metadata at checkout (forter-docs-1) and supports custom decision configuration (forter-docs-18), implying some ability to send custom signals, but there is no documented schema or capability for developers to submit their own device fingerprints, custom behavioral signals, or arbitrary metadata that directly influences scoring weights. missing for 10: explicit API fields/documentation for submitting custom device fingerprint or behavioral data, evidence that custom signals are actually weighted in scoring versus Forter's own network-derived signals, and any tuning/configuration interface for business-specific signal weighting.
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “If the Auto Invoice option is set to YES, then the payment capture amount operation is executed and order is placed”
Network effects
founderScoring benefits from a cross-merchant network — a card or identity seen across thousands of other businesses informs the risk decision on mine
weight 2 · round drawnSiftnone0/10The evidence pack describes Sift's own ML scoring, event/decision APIs, and workflows, but nowhere claims that risk signals (e.g., a card or identity) are shared or aggregated across Sift's merchant customer base to inform another business's score. sift-docs-4 only references a business's own historical data improving its own model, not cross-merchant network effects.
Forternone0/10The evidence pack covers order submission, webhooks, disputes, chargebacks, PCI scope, and agentic/MCP features, but none of it describes a cross-merchant network effect, shared identity/card risk signals, or network-wide fraud intelligence informing decisions. Missing for 10: any documentation or claim about network-level data sharing, identity graph across merchants, or aggregated fraud signals from other businesses.
Score actions
ops userMap score ranges to actions — allow, review, block, step-up 3DS — and tune thresholds to my own risk appetite instead of a fixed cutoff
weight 2 · round to SiftSift's docs describe Workflows as a rules automation platform for real-time risk-based decisions, with custom Decisions (e.g., Ban Account, Cancel Order) tied to score ranges (0-100), and Review Queues for human review — directly supporting configurable score-to-action mapping and threshold tuning. However, no evidence explicitly mentions 3DS step-up as an action type, and an older founder comment (sift-comm-8) claims 'no rules' which is in tension with the current Workflows rules-engine framing, though this appears to reflect product evolution rather than a live contradiction. missing for 10: explicit 3DS/step-up action documentation, independent hands-on confirmation of threshold customization in practice.
- [claimed-docs] “Sift represents this risk with a score between 0 and 100, where risky events have higher scores.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Learn to set up custom Decisions, like Ban Account or Cancel Order, that are connected to real business actions in your backend.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [community] “Sift Science founder on false positives: 'Most of our customers review each user we flag, and have a human make a final go/no-go decision ab…”
- [community] “CEO explains no-rules ML approach: 'we do not have any rules in our product... rules are rather easy for fraudsters to circumvent, and they …”
Forternone0/10The evidence pack covers order decisions, webhooks, disputes, PCI scope, and agentic order tagging, but contains no mention of score-range-to-action mapping, configurable thresholds, or step-up 3DS logic that ops users could tune. Forter's docs reference binary/decision-based order outcomes (fraud/abuse decision) rather than a threshold-tuning console. Missing for 10: any documentation of score bands, adjustable thresholds, or 3DS step-up configuration UI/API.
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “If the Auto Invoice option is set to YES, then the payment capture amount operation is executed and order is placed”
Scoring api
developerGet a machine-learning risk score for a transaction in real time — synchronously, before authorization completes — through a documented API
weight 3 · round drawnSift's documented Score API returns a 0-100 ML risk score via REST, and Workflows enable real-time risk-based decisions during key events, supporting synchronous scoring before a decision. However, the evidence doesn't explicitly confirm the Score API is called synchronously pre-authorization (vs. async/webhook-based scoring), and community feedback notes many customers use human review queues rather than pure real-time automated decisions. Missing for 10: explicit documentation of synchronous call/response latency guarantees for pre-authorization use, and independent confirmation of real-time performance under transaction-blocking scenarios.
- [claimed-docs] “Sift represents this risk with a score between 0 and 100, where risky events have higher scores.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Block unauthorized access in real time.”
- [community] “Sift Science founder on false positives: 'Most of our customers review each user we flag, and have a human make a final go/no-go decision ab…”
Forter's Order API (order-v3) is documented as a synchronous checkout-time call returning a fraud/abuse decision, and order-status/webhooks show authorization events are tracked separately, implying the decision precedes authorization — consistent with real-time pre-auth scoring. However, the docs describe a categorical 'decision' rather than an explicit numeric ML risk score, and there's no independent/hands-on latency or scoring-format confirmation. Missing for 10: explicit documentation of a numeric/probabilistic risk score field, and independent verification of real-time performance.
- [claimed-docs] “Send order information at checkout to receive a fraud or abuse decision.”
- [claimed-docs] “Inform of updates to the status of an order, including payment authorization, fulfillment, shipping details, and compensation granted.”
- [claimed-docs] “Forter has both a production and a sandbox environment for your development process.”
Rules engine — stories about rules engine in this arenaRules engine
Stories about rules engine in this arena
Backtesting
risk analystBacktest a rule against my historical traffic before deploying it, seeing exactly what it would have blocked, flagged, and cost
weight 2 · round drawnSiftnone0/10The evidence describes Workflows as a rules automation platform and mentions real-time decisioning, but nothing in the pack describes a backtest/simulation capability against historical traffic showing what a rule would have blocked/flagged/cost.
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
Lists
ops userMaintain allow and block lists — emails, cards, devices, IPs — and velocity limits, managed through the dashboard and programmatically
weight 2 · round to SiftSiftdisputedcontradicted3/10Docs describe a general 'Workflows' rules automation platform and Review Queues, but there's no explicit mention of dedicated allow/block lists for emails, cards, devices, or IPs, nor velocity limit configuration in the dashboard or API. Compounding this, a Sift co-founder is quoted stating 'we do not have any rules in our product' as a core design philosophy, directly conflicting with the rules-engine framing implied by the Workflows docs. missing for 10: explicit allow/block list management (emails, cards, devices, IPs), velocity limit configuration, dashboard UI evidence, and resolution of the rules-vs-no-rules contradiction.
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [community] “CEO explains no-rules ML approach: 'we do not have any rules in our product... rules are rather easy for fraudsters to circumvent, and they …”
- [community] “Critical take: 'The biggest problem with ML is that it takes time for it to react to new fraud patterns/schemes. While rules engines have li…”
Forternone0/10The evidence pack contains no mention of allow/block lists (emails, cards, devices, IPs) or velocity limit configuration, either via dashboard or API — only order decisioning, webhooks, disputes, and agentic order APIs are documented. This is a fair capability to expect from a fraud-rules platform, but no evidence supports it.
Rule authoring
risk analystAuthor custom rules that combine model scores, velocity counters, list matches, and transaction attributes into allow, block, or review decisions
weight 3 · round to SiftSiftdisputedcontradicted5/10Docs describe Workflows as a 'powerful rules automation platform' for real-time decisioning (allow/block/review) using scores and custom logic (sift-docs-6, sift-docs-7, sift-docs-12), suggesting the requested rule authoring capability. However, a Sift co-founder is on record stating 'we do not have any rules in our product' and that rules are easy to circumvent, directly contradicting the existence of a rules engine (sift-comm-8), and no evidence details velocity counters or list-match integration into rule logic. missing for 10: explicit documentation of velocity counters, list matching, and multi-attribute rule composition within Workflows; independent verification reconciling the rules-vs-no-rules discrepancy.
- [claimed-docs] “Workflows enable you to make risk-based decisions in real time during key events. Follow this guide to create your own custom Workflow.”
- [claimed-docs] “Learn to set up custom Decisions, like Ban Account or Cancel Order, that are connected to real business actions in your backend.”
- [claimed-docs] “Sift offers Workflows, a powerful rules automation platform, and Review Queues.”
- [community] “CEO explains no-rules ML approach: 'we do not have any rules in our product... rules are rather easy for fraudsters to circumvent, and they …”
Forternone0/10The evidence pack covers order submission, webhooks, chargeback/dispute automation, and MCP/agentic order tagging, but contains no mention of a custom rules engine, rule authoring UI/API, velocity counters, list matching, or configurable allow/block/review decision logic controlled by risk analysts.
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableSiftn/aSift is a fraud-detection/risk-scoring platform, not an AI agent or assistant; the story asks whether the product can plug in MCP servers to consume external tools, which is a client-agent capability not applicable to this kind of product.
Fortern/aForter's MCP evidence shows it exposing its own MCP server so external AI agents (e.g., Claude Desktop) can call Forter's fraud/dispute tools, not Forter itself acting as an MCP client that consumes and uses other servers' tools. As a fraud-decisioning SaaS platform, not an agent/orchestrator, the client-side 'plug in MCP servers' story is the wrong axis for this product's role.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · not comparableSiftn/aSift is a fraud-detection/risk-scoring platform, not an agent-facing product issuing scoped API credentials for AI agents; no evidence pack items address credential scoping or agent-specific access control, and this is a category mismatch rather than a gap in an applicable capability.
Forternone0/10Forter has API/webhook docs and even an MCP server for agent-driven actions, but no evidence describes issuing scoped or least-privilege API credentials/tokens for an agent identity. Missing for 10: any mention of API key/token scoping, permission levels, or credential issuance workflow for agents.
- [claimed-docs] “It enables an AI system to perform real actions—such as reviewing decisions, managing disputes, or updating policies through natural languag…”
- [claimed-docs] “Connect Forter MCP to Claude Desktop app for conversational AI workflows.”
- [probe] “official MCP server documented at https://docs.forter.com/mcp”
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableSiftn/aSift is a fraud-detection/risk-scoring platform, not a workflow/job scheduling or automation orchestration tool; scheduling recurring jobs is outside its product category and not addressed by any evidence (Workflows here refer to real-time rules-based decisioning, not recurring job scheduling).
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableSiftn/aSift is a fraud-detection/risk-scoring platform, not an automation/workflow builder with version control for user-created automations; the evidence pack shows Workflows and Decisions APIs but no versioning, review, or rollback of automations. This is a category mismatch rather than a missing feature.
ai-native userRead the product's source under an open license
weight 2 · not comparableSiftn/aSift is a proprietary commercial fraud-detection SaaS product; there is no indication of an open-source license or public source code. This is a category error for the axis — closed commercial SaaS products aren't expected to publish source under open license, so it's inapplicable rather than a failure.
Forternone0/10Forter is a closed, proprietary fraud-prevention SaaS; no evidence of any open-source license or public source code repository for the core product. Missing for 10: any open-source license grant, public source repository, or licensing terms permitting source inspection/modification.
ai-native userSelf-host the core product
weight 3 · not comparableSiftn/aSift is a cloud-based fraud detection SaaS delivered via REST APIs and hosted risk scoring; self-hosting the core product is not a fair axis for this kind of managed service, and no evidence suggests otherwise.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableSiftn/aSift is a backend fraud-detection/risk-scoring API whose core function is ingesting customer/user behavioral data for fraud analysis, not a developer tool or AI agent with its own usage-telemetry settings that an 'AI-native user' would opt out of. The evidence pack contains no mention of telemetry collection about API/dashboard usage, making this axis a category mismatch rather than an unmet capability.