Stripe Identity vs Plaid Identity Verification

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Stripe Identity
   Stripe Identity✓fullprobed8/10

   Stripe's docs.stripe.com serves both an llms.txt (200) and .md variants of Identity docs (200), confirmed via direct probes, letting an agent be pointed at machine-readable docs. Missing for 10: no explicit agent-oriented guidance specific to Identity beyond the generic llms.txt, and no independent community confirmation of agents successfully using it this way.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.stripe.com/llms.txt # Stripe Documentation When installing Stripe packages, always check the npm r…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/identity.md # Identity Verify government-issued IDs, match documents to selfies, and val…”
   • [claimed-docs] “Capture government-issued photo IDs with a conversion-optimized verification flow”

   proof ↗⚑ flag

   Plaid Identity Verification~partialprobed5/10

   Plaid does have a confirmed llms.txt at plaid.com/llms.txt and a documented MCP server, showing some agent-oriented infrastructure, but the llms.txt content is generic (not IDV-specific) and the docs-as-markdown probe for the Identity Verification pages returned a 404, meaning agent-friendly docs are not reliably available for this product area. missing for 10: a working IDV-specific llms.txt or markdown docs endpoint, evidence the MCP server exposes IDV-specific docs/tools, and independent confirmation of agent consumption.

   • [probe] “PROBE llms.txt: HTTP 200 at https://plaid.com/llms.txt # Plaid > Plaid helps all companies build fintech solutions by making it easy, safe …”
   • [probe] “PROBE docs-md: HTTP 404 at https://plaid.com/docs/identity-verification/.md”
   • [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Stripe Identity
   Stripe Identity~partialclaimed6/10

   Stripe Identity exposes a full REST API (curl examples for creating verification sessions), webhooks for automated result handling, and programmatic access to results, which supports headless/CI-style automation. However, there's no evidence of a dedicated SDK/test-mode designed for CI pipelines, official CI examples, or automated testing harnesses specific to Identity verification flows. missing for 10: CI-specific tooling/examples, automated test-mode documentation for Identity, independent hands-on confirmation of headless CI usage.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “You can use a flow’s static link to verify any number of your users.”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   Evidence shows Plaid IDV as an API/webhook-driven product with a no-code Dashboard editor and Sandbox testing inputs, but there is no documentation of a CLI, SDK automation, or CI-friendly headless workflow that an AI-native user could run in an automated pipeline. Missing for 10: explicit CI/headless usage docs, CLI or automation SDK evidence, example of scripted/unattended runs.

   • [claimed-docs] “No-code editor to create and change verification flows”
   • [claimed-docs] “In Sandbox mode, Identity Verification accepts the fixed set of inputs below in order to result in successful Data Source and Documentary Ve…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Plaid Identity Verification
   Stripe Identity~partialprobed6/10

   Stripe (the platform Stripe Identity belongs to) has an official documented MCP server that lets AI agents interact with 'the Stripe API,' confirmed by both docs and a probe. However, the evidence never explicitly confirms that Identity-specific verification-session endpoints are exposed as MCP tools, leaving a gap in scope specificity. Missing for 10: explicit documentation or example showing Identity verification-session/session-result operations available as MCP tools, and independent/community confirmation of using the MCP server for Identity use cases.

   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Plaid Identity Verification✓fullprobed6/10

   Plaid is a platform/service (not itself an agent), so the axis applies, and evidence confirms an official MCP server exists at plaid.com/docs/resources/mcp/. However, the pack only shows the existence of the page, not details on what tools/capabilities are exposed via MCP or independent corroboration of its use. Missing for 10: documentation of specific MCP tool/resource definitions, usage examples, and independent/hands-on confirmation of successful agent connection.

   • [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Stripe Identity
   Stripe Identity~partialprobed6/10

   Stripe offers an official Stripe CLI documented at docs.stripe.com/stripe-cli, which applies platform-wide including Identity API interactions, though evidence doesn't show Identity-specific CLI commands or AI-native workflow integration beyond the generic CLI listing. missing for 10: Identity-specific CLI usage examples, independent hands-on confirmation of CLI use with Identity endpoints, agentic/AI-native workflow documentation for the CLI.

   • [probe] “official CLI documented at https://docs.stripe.com/stripe-cli”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   No evidence of an official CLI for Plaid Identity Verification; evidence only covers docs, dashboard, no-code editor, and an MCP server, none of which constitute a CLI tool.

   ⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Stripe Identity
   Stripe Identity✓fullprobed8/10

   Stripe Identity exposes a documented REST API (verification_sessions endpoint with curl examples), webhooks for outcomes, programmatic access to verification results, and review/blocklist actions — all usable to fully drive the product without a UI. There's also an official MCP server for AI agents to interact with the Stripe API. Missing for 10: a public OpenAPI/swagger spec was probed and returned 404s, and no independent hands-on report of an AI agent driving the API end-to-end.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Plaid Identity Verification~partialprobed6/10

   Plaid IDV is documented as a REST API with webhooks, events, and workflow configuration, indicating a documented public API surface (plaid-idv-docs-1,2,3,5), and Plaid also publishes an official MCP server (plaid-idv-probe-4) supporting agentic access. However, an OpenAPI spec could not be located at standard paths and the docs-md probe 404'd, suggesting incomplete machine-readable API discoverability. missing for 10: publicly discoverable OpenAPI/schema spec, confirmation that MCP server covers IDV endpoints specifically, independent developer corroboration of API-driven automation.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “onEvent will fire at certain points throughout the IDV flow with updates on the user's progress at each point.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
   • [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Stripe Identity—none0/10

   The 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.)

   ⚑ flag

   Plaid Identity Verification—none0/10

   The 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.)

   ⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Plaid Identity Verification
   Stripe Identity~partialprobed5/10

   Docs show a well-documented REST API (curl examples, programmatic access to verification results, webhooks) and even an official MCP server for AI agents, implying SDK-friendly integration, but no evidence explicitly documents official client SDKs (e.g., Node/Python/Ruby libraries) or their AI/agentic usage patterns. missing for 10: explicit official SDK documentation, language-specific SDK usage examples, and any AI-native tooling built directly on those SDKs beyond the generic MCP server mention.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Plaid Identity Verification~partialprobed6/10

   Plaid provides official docs, webhooks, and an llms.txt for AI-native discovery, plus a documented official MCP server, but there's no direct evidence of official language-specific SDKs for Identity Verification itself (probes for OpenAPI spec and docs.md all 404). missing for 10: explicit official SDK references/links, independent developer corroboration of SDK usage.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://plaid.com/llms.txt # Plaid > Plaid helps all companies build fintech solutions by making it easy, safe …”
   • [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”
   • [probe] “PROBE docs-md: HTTP 404 at https://plaid.com/docs/identity-verification/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe Identity✓fullclaimed7/10

   Stripe Identity's docs explicitly describe listening for verification results via webhooks/events to trigger automated reactions, and events/webhooks are Stripe's standard integration mechanism supported across products including Identity. Missing for 10: explicit webhook event-type list for Identity, independent hands-on confirmation of webhook reliability/latency, and AI-agent-specific webhook subscription tooling beyond general docs.

   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Access collected images, and extracted data from government-issued ID documents”

   proof ↗⚑ flag

   Plaid Identity Verification✓fullclaimed7/10

   Plaid IDV documents a clear webhook subscription mechanism with defined events (STEP_UPDATED, STATUS_UPDATED, RETRIED) that fire on verification progress, allowing programmatic/agentic subscription to state changes. Missing for 10: no explicit documentation of webhook payload schema, retry/delivery guarantees, or independent/hands-on confirmation that agentic systems actually consume these webhooks in production.

   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “onEvent will fire at certain points throughout the IDV flow with updates on the user's progress at each point.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Stripe Identity—none0/10

   No evidence that Stripe Identity itself generates AI-driven insights or suggestions from verification data; the docs describe verification, review tools, and manual override, not AI-generated analytics or recommendations. The MCP server reference is about external agents calling Stripe's API, not in-product AI insights for the user.

   ⚑ flag

   Plaid Identity Verification—none0/10

   Evidence shows Plaid IDV as a verification/workflow product with risk scores, dashboards, and webhooks, but nothing about AI-generated insights or suggestions surfaced to end users within the product itself; the MCP server reference is about agent connectivity, not in-product AI insights.

   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”
   • [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Stripe Identity~partialprobed5/10

   Stripe Identity supports webhook-driven automation (auto-triggering reactions to verification outcomes, programmatic access, blocklist automation) and Stripe now ships an official MCP server letting AI agents call the API, which together enable background/autonomous workflows. However, evidence doesn't show any AI-native scheduling, agent orchestration, or first-party 'set-and-forget' automation framework specific to Identity beyond webhooks+MCP. Missing for 10: dedicated agent/automation tooling within Identity itself, independent hands-on confirmation of autonomous agent use via MCP for identity verification, and detail on how persistent/background jobs are managed.

   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed5/10

   Plaid IDV supports background automation via webhooks (STEP_UPDATED, STATUS_UPDATED, RETRIED) and a no-code Workflow Management editor that can run conditional verification checks without manual intervention, which enables some autonomous background processing. However, there is no evidence of AI-agent-specific automation setup, natural-language automation configuration, or scheduling/triggering by an AI agent itself. Missing for 10: explicit AI-agent-driven automation setup, natural-language workflow configuration, evidence of autonomous agent-triggered verification chains beyond webhook/workflow primitives.

   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “No-code editor to create and change verification flows”
   • [claimed-docs] “onEvent will fire at certain points throughout the IDV flow with updates on the user's progress at each point.”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Stripe Identity
   Stripe Identity~partialprobed5/10

   Stripe provides an official MCP server that lets AI agents interact with the Stripe API via natural-language-driven tool calls, which would in principle expose Identity operations (create/verify sessions, review) to an AI agent. However, there is no evidence specifically confirming Identity endpoints are exposed through this MCP server, nor any hands-on or community confirmation of natural-language operation of Identity itself. Missing for 10: explicit documentation that Identity API/actions are covered by the MCP server, and independent/hands-on evidence of an AI agent successfully running Identity verification via natural-language commands.

   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Plaid Identity Verification~partialprobed4/10

   Plaid documents a no-code visual workflow editor for configuring Identity Verification, not natural-language command operation, but a probe confirms Plaid has an official MCP server (plaid.com/docs/resources/mcp/) which could allow AI agents to invoke Plaid APIs including IDV via natural language. There is no direct evidence that this MCP server specifically exposes Identity Verification actions or that end-users can operate IDV flows via NL commands. missing for 10: IDV-specific MCP tool documentation, examples of natural-language driven verification commands, independent confirmation of agentic usage.

   • [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”
   • [claimed-docs] “No-code editor to create and change verification flows”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Stripe Identity
   Stripe Identity~partialprobed4/10

   Docs include concrete code samples (e.g., curl requests for verification sessions) and structured API reference pages, but there is no evidence of an interactive, runnable API console (probes show openapi.json/swagger.json 404, and no mention of a 'try it' sandbox or live code execution). missing for 10: evidence of an in-browser runnable/interactive API explorer, discoverable OpenAPI spec, or independent confirmation of interactivity.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/identity.md # Identity Verify government-issued IDs, match documents to selfies, and val…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   No evidence of an interactive API reference with runnable examples; OpenAPI spec probes returned 404s and docs are plain markdown pages, not interactive/runnable explorer.

   • [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://plaid.com/docs/identity-verification/.md”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Stripe Identity—none0/10

   The evidence pack shows an explicit probe for OpenAPI/swagger spec files at standard paths, all returning 404, and no docs page or claim points to a downloadable machine-readable API spec for Identity; only human-readable curl examples and prose docs exist.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”
   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   Probes explicitly show no OpenAPI/swagger spec found at any candidate path and no machine-readable .md/doc spec at the IDV docs endpoint; documentation is prose-based rather than a downloadable API spec.

   • [probe] “PROBE docs-md: HTTP 404 at https://plaid.com/docs/identity-verification/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Plaid Identity Verification
   Stripe Identity—none0/10

   No evidence in the pack mentions a sandbox, test mode, or test API keys specific to Stripe Identity that would let a developer verify documents without touching production data. Missing for 10: any documentation of Identity test-mode verification sessions, sandbox test IDs/selfies, or explicit test/live key separation for this product.

   ⚑ flag

   Plaid Identity Verification✓fullclaimed7/10

   Plaid IDV documents a dedicated Sandbox mode with fixed test inputs to simulate successful/failed verification checks without touching production data, which directly supports safe testing. missing for 10: no independent/hands-on developer confirmation of sandbox fidelity, and no explicit mention of automated/agentic test workflows against the sandbox.

   • [claimed-docs] “In Sandbox mode, Identity Verification accepts the fixed set of inputs below in order to result in successful Data Source and Documentary Ve…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Stripe Identity—none0/10

   Evidence shows API usage (curl examples, secret key access) but no documentation of API versioning scheme or a deprecation policy; the OpenAPI probe returned 404s, and no changelog/versioning docs are cited. Missing for 10: versioning scheme docs, deprecation policy docs, changelog/migration guides.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.stripe.com/openapi.json, https://docs.stripe.com/swagger.json, https://docs.stripe.com/…”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   No evidence of API versioning scheme or documented deprecation policy for Plaid Identity Verification's APIs; docs cover verification features, webhooks, sandbox testing, but nothing on version lifecycle or deprecation commitments. The openapi.json probe also 404s, suggesting no discoverable machine-readable API spec that would typically accompany versioning docs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”
   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “In Sandbox mode, Identity Verification accepts the fixed set of inputs below in order to result in successful Data Source and Documentary Ve…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Stripe Identity—none0/10

   Evidence shows only per-session API calls (create one verification_session at a time) and no batch/bulk endpoint for processing many verifications in a single call; the 'static link' flow (docs-9) supports many users sequentially, not bulk operations in an AI-native automation sense. No documentation of bulk create/list/export or batch-processing APIs is present.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “You can use a flow’s static link to verify any number of your users.”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   No evidence of batch/bulk API operations, bulk session creation, or programmatic multi-item processing for Identity Verification; documentation covers single-session workflows, webhooks, and dashboard-based overrides only, with no mention of bulk endpoints or automation-scale operations across many items.

   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “you can override a failure via the Dashboard by clicking the Override Result button on the verification detail page in the Dashboard.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Plaid Identity Verification
   Stripe Identity~partialclaimed5/10

   Stripe Identity supports event-driven automation via webhooks ('Listen for verification results so your integration can automatically trigger reactions') and has some built-in rule-like actions (auto-blocklisting matched documents, override status), but there's no evidence of a user-facing rules engine where an AI-native user can declaratively define custom conditional rules — automation still requires the developer to write webhook-handling code. Missing for 10: a declarative rules/conditions builder, evidence of AI-agent-configurable triggers beyond generic webhooks, and confirmation the MCP server exposes rule-definition capabilities.

   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed6/10

   Plaid IDV supports webhooks that fire on defined events (STEP_UPDATED, STATUS_UPDATED, RETRIED) and a Workflow Management editor that lets you run certain verification checks conditionally (e.g., only if another check fails or based on country), which together give a rule/event-driven automation capability. However, this is scoped to verification-flow logic and webhook notifications rather than a general-purpose 'define rules that trigger arbitrary actions' engine. missing for 10: evidence of a broader rule/action engine beyond conditional verification checks, and evidence of user-defined custom actions (not just webhook notifications) triggered by events.

   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “onEvent will fire at certain points throughout the IDV flow with updates on the user's progress at each point.”
   • [claimed-docs] “No-code editor to create and change verification flows”

   proof ↗⚑ flag

Deepfake defense

1. risk analystThe vendor documents specific defenses against AI-generated faces, deepfakes, and camera-injection attacks — named detection capabilities, not just a marketing mention of fraud

   weight 2 · round drawn
   Stripe Identity—none0/10

   The evidence pack only shows generic mentions of ID/selfie matching and fraud prevention (e.g., 'match documents to selfies... to prevent fraud') but no named detection capabilities against AI-generated faces, deepfakes, or camera-injection attacks. No documentation specifically addresses liveness detection technology or anti-spoofing mechanisms by name.

   • [claimed-docs] “Match government-issued photo IDs with selfies, and validate Social Security numbers (SSNs)”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/identity.md # Identity Verify government-issued IDs, match documents to selfies, and val…”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   The evidence pack covers document verification, workflow management, webhooks, sandbox testing, risk scoring, and dashboard overrides, but contains no mention of liveness detection, anti-spoofing, deepfake detection, AI-generated face detection, or camera-injection defenses by name. Community items are off-topic (data trust/competition) and irrelevant to biometric liveness. Missing for 10: named liveness/anti-spoofing detection capabilities, deepfake or synthetic-face detection mentions, camera-injection attack defenses.

   ⚑ flag

Duplicate detection

1. risk analystThe platform detects repeat and duplicate identities across verifications — the same face or document resurfacing under different names is flagged automatically

   weight 2 · round to Stripe Identity
   Stripe Identity~partialclaimed3/10

   Docs mention a manual 'add to blocklist' review tool that can block future verifications using the same flagged document, but this requires an analyst to manually add the document rather than the platform automatically detecting and flagging duplicate faces/documents resurfacing under different names. There's no evidence of automatic cross-session biometric or document matching for fraud rings. Missing for 10: automatic duplicate/repeat-identity detection across sessions, face-matching across different names, proactive fraud-ring flagging without manual analyst action.

   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   The evidence covers document/identity verification checks, risk scoring, webhooks, and dashboard overrides, but nothing describes cross-session duplicate or repeat-identity detection (e.g., matching the same face/document under different names). Missing for 10: any documentation of duplicate-identity or repeat-fraud detection across sessions, biometric/face matching against prior submissions, or deduplication reporting.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”
   • [claimed-docs] “The conversion rate is defined as the percentage of sessions begun that were completed, regardless of whether the user passed or failed veri…”

   proof ↗⚑ flag

Liveness

1. risk analystSelfie checks match the live user to the document portrait with liveness detection — documented defenses against printed photos, screens, and replayed video

   weight 3 · round to Stripe Identity
   Stripe Identity~partialprobed4/10

   Docs confirm selfie-to-document matching as part of the verification flow (stripe-identity-docs-3, stripe-identity-probe-2), but there is no documented mention of liveness detection or specific anti-spoofing defenses against printed photos, screens, or replayed video. Missing for 10: explicit liveness detection documentation, anti-spoofing technical details, and independent/hands-on evidence that liveness checks defeat photo/screen/video replay attacks.

   • [claimed-docs] “Match government-issued photo IDs with selfies, and validate Social Security numbers (SSNs)”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.stripe.com/identity.md # Identity Verify government-issued IDs, match documents to selfies, and val…”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   The evidence pack covers document verification, workflows, webhooks, sandbox testing, risk scoring, and dashboard overrides, but never mentions selfie/facial matching or liveness detection defenses against photos, screens, or replayed video. No documentation cites a selfie check or anti-spoofing mechanism at all.

   ⚑ flag

Db checks

1. developerVerify identity against authoritative databases without documents — SSN, national registries, or credit-header data — for lower-friction flows where a doc scan is overkill

   weight 2 · round to Stripe Identity
   Stripe Identity~partialclaimed5/10

   Docs confirm SSN validation as part of document verification flow (stripe-identity-docs-3), but evidence is thin on standalone no-document checks like national registry lookups or credit-header/database-only verification — SSN validation appears bundled with document capture rather than a document-free flow. Missing for 10: explicit documented database-only/no-document verification session type, national registry checks, credit-header data verification, and independent confirmation these work without a doc scan.

   • [claimed-docs] “Match government-issued photo IDs with selfies, and validate Social Security numbers (SSNs)”
   • [claimed-docs] “Capture government-issued photo IDs with a conversion-optimized verification flow”
   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed4/10

   Docs show IDV can check ID numbers, phone, address, name/DOB and combine checks conditionally (skipping some verifications like documents based on risk/country), implying some document-free paths exist, but no evidence explicitly names SSN, national registry, or credit-header-only verification flows as a distinct low-friction option. missing for 10: explicit mention of SSN-only or credit-header verification, explicit 'no-doc' database-only workflow example, independent confirmation of doc-free flows in production.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “Authenticate IDs Verify that global ID documents are authentic and valid.”

   proof ↗⚑ flag

Kyb

1. ops leadVerify businesses, not just people — registry lookups, UBO identification, and documented KYB flows that chain into KYC on the owners

   weight 2 · round drawn
   Stripe Identity—none0/10

   Stripe Identity documentation and community evidence focus entirely on individual identity verification (ID documents, selfie matching, SSN validation) — nothing addresses business registry lookups, UBO identification, or KYB flows chaining into KYC on owners.

   ⚑ flag

   Plaid Identity Verification—none0/10

   All evidence describes Plaid Identity Verification as a personal KYC flow (documents, phone, DOB, ID numbers, risk scoring) with no mention of business registry lookups, UBO identification, or a documented KYB workflow chaining into KYC on owners.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”
   • [claimed-docs] “Monitor also integrates directly with Identity Verification for an end-to-end verification and KYC solution.”

   proof ↗⚑ flag

Risk signals

1. developerEnrich verifications with phone, email, and device risk signals — carrier checks, address history, device fingerprint — as additional documented check types

   weight 2 · round to Plaid Identity Verification
   Stripe Identity—none0/10

   Evidence shows Stripe Identity supports document verification, selfie matching, and SSN validation, but nothing documents carrier/phone risk checks, address history checks, or device fingerprinting as check types.

   ⚑ flag

   Plaid Identity Verification~partialclaimed5/10

   Docs confirm phone and email risk scoring plus granular risk assessments shown per session, and address/name/ID verification is documented as a check type, but there is no explicit documentation of carrier checks, address history checks, or device fingerprinting as distinct check types. missing for 10: explicit carrier check documentation, address history verification, device fingerprint/risk signal documentation.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”

   proof ↗⚑ flag

Doc types

1. ops leadThe platform verifies government IDs from a documented breadth of countries and document types — passports, national IDs, driver licenses, residence permits — with the supported list published

   weight 3 · round to Plaid Identity Verification
   Stripe Identity!disputedcontradicted5/10

   Stripe's docs claim ID verification for 120+ countries and mention passports, national IDs, and other government-issued photo IDs, but there's no published document-type breakdown (passport vs. national ID vs. driver license vs. residence permit) per country, and community reports concretely contradict full breadth: a user notes Polish IDs are unsupported despite smaller countries being covered, and multiple reports describe Chinese passports being rejected as 'invalid' during verification. missing for 10: a published per-country/per-document-type coverage list, and resolution of documented failures for specific document types (e.g., Chinese passports, Polish IDs).

   • [claimed-docs] “Verify the authenticity of government-issued ID documents from more than 120 countries”
   • [claimed-docs] “Capture government-issued photo IDs with a conversion-optimized verification flow”
   • [community] “I'm really surprised they don't support Polish IDs. We've had them in the same format for ages and I've done automatic verification with som…”
   • [community] “We have a problem with validating passports of residents from Asia-Pacific who use the Stripe Identity tool... This situation is similar to …”
   • [community] “Stripe Identity shows 「The document is invalid」 after submitting a Chinese passport.”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed3/10

   Plaid's docs assert it verifies 'identification documents' and 'global ID documents' broadly, but no evidence provides an actual published list of supported countries or document types (passports, national IDs, driver licenses, residence permits) as the story requires. missing for 10: a published country/document-type coverage list, explicit mention of residence permits or other document categories, independent corroboration of coverage breadth.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “Authenticate IDs Verify that global ID documents are authentic and valid.”
   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”

   proof ↗⚑ flag

Extraction

1. developerVerified sessions return the extracted document fields as structured data — name, date of birth, document number, address, expiry — retrievable via the API, not just a pass/fail flag

   weight 2 · round to Stripe Identity
   Stripe Identity✓fullclaimed8/10

   Docs explicitly state you can access collected images and extracted data from ID documents programmatically via secret key, and the API returns structured verification details rather than a simple flag; the verification_sessions API and access-verification-results docs support this. Missing for 10: an explicit enumerated field list (name, DOB, document number, address, expiry) in the evidence pack and independent hands-on confirmation of exact field names.

   • [claimed-docs] “Access collected images, and extracted data from government-issued ID documents”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed5/10

   Docs confirm Plaid extracts and verifies fields like name, DOB, ID numbers, and address from documents, and risk scores/results are viewable in the Dashboard, implying this data exists per session. However, there's no explicit evidence that these individual extracted document fields are retrievable via API as structured data in the response payload (as opposed to just Dashboard viewing or an overall pass/fail status). Missing for 10: explicit API schema/response example showing per-field structured output (name, DOB, document number, address, expiry) retrievable via API call, independent developer confirmation of this data access pattern.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”
   • [claimed-docs] “Authenticate IDs Verify that global ID documents are authentic and valid.”

   proof ↗⚑ flag

Agent decisions

1. ai-native userVerification outcomes come back structured enough for an agent to decide on — machine-readable check results, risk signals, and failure reasons an automated onboarding flow can branch on

   weight 2 · round to Stripe Identity
   Stripe Identity✓fullcommunity7/10

   Stripe Identity's API returns structured verification_sessions objects with programmatic access to results, extracted data, and outcome webhooks that trigger automated reactions, giving an onboarding flow machine-readable data to branch on (docs-5, docs-6, docs-7, docs-4). Failure reasons and status overrides are documented via review tools, but there's no explicit schema showing granular risk-signal taxonomies or agent-specific decision guidance, and community reports (comm-12, comm-13) show ambiguous 'document invalid' failures that complicate automated branching. missing for 10: a documented enumerated list/schema of all risk signals and failure reason codes, independent confirmation that failure reasons are granular/actionable enough for automated branching rather than opaque.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Access collected images, and extracted data from government-issued ID documents”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [community] “We have a problem with validating passports of residents from Asia-Pacific who use the Stripe Identity tool... This situation is similar to …”
   • [community] “Stripe Identity shows 「The document is invalid」 after submitting a Chinese passport.”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed6/10

   Plaid IDV exposes structured webhook events (STEP_UPDATED, STATUS_UPDATED, RETRIED) and per-session risk signals (email/phone risk, overall risk score) that a workflow could branch on, plus conditional check logic in templates. However, evidence doesn't show a documented API response schema with explicit machine-readable failure-reason codes for programmatic branching, and there's no independent/hands-on confirmation of how granular or reliable these signals are for automated agent decisioning. Missing for 10: explicit API/webhook payload schema with structured failure-reason enums, and independent corroboration of agent-usable structured outputs.

   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”
   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “onEvent will fire at certain points throughout the IDV flow with updates on the user's progress at each point.”

   proof ↗⚑ flag

Agent operations

1. ai-native userAn agent can operate the verification pipeline — create sessions, poll outcomes, retrieve extracted data, and trigger re-checks through the API or an MCP surface with scoped credentials

   weight 3 · round to Stripe Identity
   Stripe Identity~partialprobed5/10

   Stripe Identity's API supports creating verification sessions, listening for/polling outcomes via webhooks, and retrieving extracted data programmatically with a scoped secret key, and Stripe has a general MCP server that exposes Stripe API tools to agents. However, there is no evidence the MCP server specifically exposes Identity operations (session creation, outcome polling, data retrieval, re-checks) or documents scoped credentials for Identity use cases, nor any agent-specific workflow example. missing for 10: MCP tool listing/documentation confirming Identity-specific endpoints are exposed, evidence of scoped/restricted API keys for agent use, and confirmation of a re-check/retry trigger via API or MCP.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Plaid Identity Verification~partialprobed4/10

   Plaid IDV has a documented API/webhook model (create sessions, poll status via STEP_UPDATED/STATUS_UPDATED/RETRIED events, retrieve data) and an official MCP server is referenced, suggesting some agent-friendly surface exists. However, there is no evidence describing scoped credentials for agent use, no documentation of MCP tools specifically exposing IDV session creation/polling/data retrieval/re-check triggers, and no confirmation of programmatic re-check triggering beyond dashboard override. missing for 10: MCP server tool documentation specific to IDV endpoints, scoped/least-privilege credential model for agents, programmatic re-check/retry trigger via API, independent confirmation of agent usage.

   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “you can override a failure via the Dashboard by clicking the Override Result button on the verification detail page in the Dashboard.”
   • [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”

   proof ↗⚑ flag

Sandbox

1. developerA sandbox lets me exercise every outcome before going live — documented test documents, personas, or magic values that deterministically produce pass, fail, and review results

   weight 3 · round to Plaid Identity Verification
   Stripe Identity—none0/10

   No evidence of documented test/sandbox mode, magic values, or deterministic test personas for triggering pass/fail/review outcomes in Stripe Identity's docs; evidence only covers live verification flow, review tools, and API access, with community complaints about real-world verification failures (not sandbox testing).

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [community] “We have a problem with validating passports of residents from Asia-Pacific who use the Stripe Identity tool... This situation is similar to …”
   • [community] “Stripe Identity shows 「The document is invalid」 after submitting a Chinese passport.”

   proof ↗⚑ flag

   Plaid Identity Verification✓fullclaimed8/10

   Plaid's docs explicitly document a Sandbox mode with a fixed set of inputs that deterministically produce specific Data Source and Documentary Verification check outcomes, directly matching the story's requirement for documented test values to exercise pass/fail scenarios. Missing for 10: explicit confirmation of a 'review' outcome test value and independent/hands-on developer corroboration beyond first-party docs.

   • [claimed-docs] “In Sandbox mode, Identity Verification accepts the fixed set of inputs below in order to result in successful Data Source and Documentary Ve…”

   proof ↗⚑ flag

Session api

1. developerThe whole verification lifecycle is drivable through the API — create a session, get its status, retrieve results and captured media, and cancel or redact it — with every step documented

   weight 3 · round to Stripe Identity
   Stripe Identity~partialclaimed6/10

   Docs cover creating a session via API (docs-5), listening for status/results (docs-6, docs-7), and accessing captured images/data (docs-4), plus review tools like manual override and blocklisting (docs-10, docs-11). However, no evidence in the pack documents the cancel or redact endpoints for verification sessions, which are explicit parts of the story. missing for 10: documented cancel session endpoint, documented redact endpoint, and independent confirmation of full lifecycle API coverage.

   • [claimed-docs] “Access collected images, and extracted data from government-issued ID documents”
   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed4/10

   Docs confirm session lifecycle events (webhooks for STEP_UPDATED/STATUS_UPDATED/RETRIED) and sandbox testing, implying some API-driven flow, but there is no explicit documentation of endpoints for creating a session, fetching status/results, retrieving captured media, or canceling/redacting a session via API — most control (overrides, flow editing) is shown as Dashboard/no-code actions rather than API calls. missing for 10: explicit API reference for create/get/retrieve-media/cancel/redact endpoints, first-party API examples for each lifecycle step.

   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “In Sandbox mode, Identity Verification accepts the fixed set of inputs below in order to result in successful Data Source and Documentary Ve…”
   • [claimed-docs] “you can override a failure via the Dashboard by clicking the Override Result button on the verification detail page in the Dashboard.”
   • [claimed-docs] “No-code editor to create and change verification flows”

   proof ↗⚑ flag

Webhooks

1. developerVerification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling

   weight 2 · round to Stripe Identity
   Stripe Identity~partialclaimed6/10

   Docs confirm Identity supports webhook-based outcome handling ("Listen for verification results so your integration can automatically trigger reactions") and programmatic access to verification results, satisfying the no-polling reaction pattern. However, the pack never shows signature verification details or explicitly enumerates the created/processing/verified/requires-input event lifecycle. Missing for 10: explicit webhook signing/verification documentation, enumerated event-type list, and independent/hands-on confirmation of the full lifecycle firing correctly.

   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed5/10

   Plaid IDV documents webhook events (STEP_UPDATED, STATUS_UPDATED, RETRIED) that let a developer react to verification lifecycle changes without polling, but the evidence never confirms these webhooks are cryptographically signed nor does it list the specific status values (created, processing, verified, requires-input) named in the story. Missing for 10: explicit documentation of webhook signature verification, and confirmation of the exact lifecycle status enum matching the story's terms.

   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “onEvent will fire at certain points throughout the IDV flow with updates on the user's progress at each point.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Stripe Identity
   Stripe Identity~partialprobed6/10

   Core verification workflow (create sessions, retrieve results, webhooks) is fully documented via REST API (stripe-identity-docs-5,6,7), and even AI agents can invoke it via the official MCP server (stripe-identity-docs-12, stripe-identity-probe-4). However, review-tool actions like manually overriding verification status or blocklisting documents (stripe-identity-docs-10,11) are described in the context of the dashboard review UI with no confirmed API endpoint, and 'Flows' configuration (stripe-identity-docs-8,9) also appears to be a dashboard-centric concept without clear API-driven equivalent. Missing for 10: documented API endpoints for manual status override/blocklist actions, API-based flow configuration, and independent confirmation that all dashboard actions have API parity.

   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [claimed-docs] “Flows provide a way to save and reuse the same configuration across all of your integration interfaces.”
   • [claimed-docs] “The Stripe Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Stripe API”
   • [probe] “official MCP server documented at https://docs.stripe.com/mcp”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   Evidence shows several capabilities are explicitly UI/Dashboard-only — e.g., the no-code Workflow Management editor for creating flows (plaid-idv-docs-8) and overriding failed verifications 'via the Dashboard by clicking the Override Result button' (plaid-idv-docs-7) — with no documented API equivalent for either. There is no evidence of a full API surface mirroring these UI actions, so the story is not shown to be delivered.

   • [claimed-docs] “you can override a failure via the Dashboard by clicking the Override Result button on the verification detail page in the Dashboard.”
   • [claimed-docs] “No-code editor to create and change verification flows”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plaid.com/openapi.json, https://plaid.com/swagger.json, https://plaid.com/api/openapi.json, …”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Stripe Identity—none0/10

   Stripe Identity is a KYC/identity-verification API for businesses, not a personal data platform; end users have no account or export mechanism, and evidence shows only programmatic access by the integrating business (via API/secret key), not data export/portability for the verified individual to leave with their data in open formats. No evidence of any data-export or account-closure/data-portability feature for the AI-native end user persona.

   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Access collected images, and extracted data from government-issued ID documents”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   No evidence of a user-facing data export/portability feature in open formats or account deletion/leave capability for Identity Verification data; evidence covers verification flows, webhooks, dashboard overrides, and risk scoring only.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Stripe Identity—none0/10

   No evidence of any data residency/region-selection controls for Stripe Identity; docs and community discussion focus on verification flows, pricing, and document support, with no mention of choosing storage region or data residency options.

   ⚑ flag

   Plaid Identity Verification—none0/10

   No evidence in the pack addresses data residency, regional storage options, or data localization controls for Identity Verification; the community citation reflects general distrust, not a data-residency dispute.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Stripe Identity—none0/10

   No evidence pack content addresses AI-model-training data usage, opt-out controls, or any privacy policy specific to AI training exclusion for Stripe Identity; the evidence only covers identity verification features, pricing, and integration mechanics.

   ⚑ flag

   Plaid Identity Verification—none0/10

   No evidence of an AI-training opt-out or data-usage control for AI models; docs cover verification workflows, webhooks, and dashboard features only, and community comments express general distrust rather than confirming/denying such a control.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe Identity—none0/10

   The evidence pack covers verification flows, review tools, and access to results, but contains no documentation of data retention policies, deletion controls, or user-initiated data removal/export mechanisms for AI-native or any users. Community commentary raises concern about data security/trust (comm-8) but does not confirm any retention/deletion controls exist. Missing for 10: any documentation of retention periods, deletion APIs/endpoints, data export or right-to-erasure workflows, or AI-agent-specific controls over stored ID data.

   • [community] “Does Stripe intend to make a giant online database of international identity documents? Why should we trust Stripe to secure these? It could…”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   The evidence pack contains no documentation of data retention settings, deletion APIs, or user-facing controls for purging identity verification data — only unrelated docs on verification checks, webhooks, and dashboard workflows. The negative community comment expresses general distrust but is not concrete evidence of a retention/deletion feature failing, so it doesn't support 'disputed'; it simply confirms no capability is evidenced.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”
   • [community] “Wow. I truly hate having to use plaid. This is disappointing. I have zero faith that they hold my data safely or that it won't be stolen or …”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Stripe Identity—none0/10

   No evidence in the pack mentions telemetry opt-out, usage tracking controls, or any privacy settings for AI-native usage; Stripe Identity is an identity verification API and the evidence is entirely about document verification and KYC features, not telemetry controls.

   ⚑ flag

   Plaid Identity Verification—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out controls for Plaid Identity Verification; docs cover verification workflows, webhooks, and reporting but nothing about disabling analytics or usage data collection.

   ⚑ flag

Consent

1. founderThe vendor documents how biometric data is handled lawfully — GDPR bases, US biometric statutes like BIPA, and the consent language my flow needs — so legal review has something to review

   weight 2 · round drawn
   Stripe Identity—none0/10

   None of the docs or community evidence address legal bases for biometric processing (GDPR Art. 9 basis, BIPA compliance, consent language) — evidence covers technical integration, review tools, and pricing/UX feedback only. missing for 10: GDPR legal basis documentation, BIPA/state biometric statute compliance statements, sample consent language, any privacy/legal compliance whitepaper.

   ⚑ flag

   Plaid Identity Verification—none0/10

   The evidence pack contains only general product/API documentation (verification checks, webhooks, sandbox testing, dashboard features) with no mention of GDPR legal bases, BIPA or other biometric statutes, or required consent language for biometric data collection. Community items are off-topic sentiment about data trust, not legal compliance documentation.

   ⚑ flag

Redaction

1. ops leadControl what happens to collected identity data — documented retention windows and a redaction or deletion API that scrubs PII on demand

   weight 2 · round drawn
   Stripe Identity—none0/10

   The evidence pack shows verification, review tools (override/blocklist), and access to collected data, but contains no documentation of retention windows or a redaction/deletion API for scrubbing PII on demand. Community commentary even raises concerns about long-term data storage trust without any documented deletion mechanism countering it.

   • [claimed-docs] “Access collected images, and extracted data from government-issued ID documents”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [community] “Does Stripe intend to make a giant online database of international identity documents? Why should we trust Stripe to secure these? It could…”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   The evidence pack covers verification checks, webhooks, dashboards, and risk scoring, but contains no documentation of data retention windows or a redaction/deletion API for scrubbing PII on demand. The community comments express general distrust about data safety but do not concretely confirm or deny a deletion/retention mechanism, so they cannot be used to dispute the claim either way.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”

   proof ↗⚑ flag

Hosted flows

1. developerLaunch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myself

   weight 3 · round to Stripe Identity
   Stripe Identity✓fullcommunity7/10

   Docs show server-side session creation via API (docs-5), a hosted, conversion-optimized capture flow with no custom UI needed (docs-2, docs-1, docs-3), and mechanisms to read results via webhooks or API (docs-6, docs-7), plus reusable 'Flows' for static links (docs-8, docs-9). Community hands-on reports corroborate the redirect-based hosted UX working well across desktop/mobile with no native app needed (stripe-identity-comm-2, stripe-identity-comm-5). Missing for 10: explicit documentation of an embeddable/drop-in JS element (vs. only hosted redirect) and independent verification of the full create→redirect→read loop end-to-end.

   • [claimed-docs] “Verify the authenticity of government-issued ID documents from more than 120 countries”
   • [claimed-docs] “Capture government-issued photo IDs with a conversion-optimized verification flow”
   • [claimed-docs] “Match government-issued photo IDs with selfies, and validate Social Security numbers (SSNs)”
   • [claimed-docs] “curl https://api.stripe.com/v1/identity/verification_sessions \ -u "<<YOUR_SECRET_KEY>>:" \ -d type=document”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Flows provide a way to save and reuse the same configuration across all of your integration interfaces.”
   • [claimed-docs] “You can use a flow’s static link to verify any number of your users.”
   • [community] “1. Easy transition from desktop to phone to take a picture of your ID or a selfie, then complete verification on desktop. 2. It does all the…”
   • [community] “We've been using this to verify short term rental guests (non-Airbnb) for the past year and it's been extremely positive. Given that our gue…”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed6/10

   Docs show a Link-based embeddable flow (onEvent updates), webhook events to read session status, and document/ID verification checks, indicating Plaid provides the capture UI and hosted/drop-in flow with server-driven session lifecycle. However, evidence never explicitly confirms a selfie/facial biometric step combined with document checks, nor explicitly describes server-side session creation API or a hosted redirect option (only Link embed and no-code editor are mentioned). Missing for 10: explicit selfie/liveness verification documentation, explicit server-side create-session API reference, and confirmation of a hosted (non-Link) redirect flow.

   • [claimed-docs] “Using Identity Verification, you can verify identification documents, phone numbers, name, date of birth, ID numbers, addresses, and more.”
   • [claimed-docs] “onEvent will fire at certain points throughout the IDV flow with updates on the user's progress at each point.”
   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “Authenticate IDs Verify that global ID documents are authentic and valid.”
   • [claimed-docs] “No-code editor to create and change verification flows”

   proof ↗⚑ flag

Native sdks

1. developerI get native iOS, Android, and web SDKs with guided camera capture — glare, blur, and edge detection coaching the user to a usable document photo on the first try

   weight 2 · round drawn
   Stripe Identity—none0/10

   The evidence only references a generic 'conversion-optimized verification flow' and one community comment describing browser-based (not native) image capture across desktop/phone; there is no documentation of native iOS/Android SDKs or of glare, blur, or edge-detection coaching during capture.

   • [claimed-docs] “Capture government-issued photo IDs with a conversion-optimized verification flow”
   • [community] “1. Easy transition from desktop to phone to take a picture of your ID or a selfie, then complete verification on desktop. 2. It does all the…”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   The evidence confirms Plaid IDV supports document verification and has Link SDK flows with event callbacks (onEvent), but nothing describes native iOS/Android/web SDKs offering guided camera capture with glare, blur, or edge-detection coaching. Missing for 10: mention of native mobile SDKs, in-flow camera guidance features, and any glare/blur/edge detection capability documentation.

   • [claimed-docs] “onEvent will fire at certain points throughout the IDV flow with updates on the user's progress at each point.”
   • [claimed-docs] “In Sandbox mode, Identity Verification accepts the fixed set of inputs below in order to result in successful Data Source and Documentary Ve…”

   proof ↗⚑ flag

No code

1. ops leadSend a verification to someone with a no-code link or QR code — no engineering ticket to verify a one-off customer, contractor, or seller

   weight 2 · round to Stripe Identity
   Stripe Identity✓fullcommunity7/10

   Stripe Identity's "Flows" feature explicitly supports a static, shareable link that ops can send to verify any number of users without engineering integration work (stripe-identity-docs-8, stripe-identity-docs-9), fitting the no-code link use case; community evidence confirms the flow is simple enough for non-technical guests to complete via a link on mobile (stripe-identity-comm-2, stripe-identity-comm-5). Missing for 10: explicit mention of QR code generation/sharing, and independent hands-on confirmation of the ops/no-ticket workflow specifically (vs. general link UX).

   • [claimed-docs] “Flows provide a way to save and reuse the same configuration across all of your integration interfaces.”
   • [claimed-docs] “You can use a flow’s static link to verify any number of your users.”
   • [community] “1. Easy transition from desktop to phone to take a picture of your ID or a selfie, then complete verification on desktop. 2. It does all the…”
   • [community] “We've been using this to verify short term rental guests (non-Airbnb) for the past year and it's been extremely positive. Given that our gue…”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed3/10

   Plaid documents a no-code editor for building verification flows and a Dashboard for managing sessions, suggesting some non-engineering control, but there is no explicit evidence of an ops-facing feature to generate a shareable verification link or QR code for a one-off customer/contractor without engineering involvement. Missing for 10: explicit dashboard 'send link/QR code' feature, evidence of ops-only workflow without developer setup, and confirmation that Link integration isn't required for a single verification.

   • [claimed-docs] “No-code editor to create and change verification flows”
   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”

   proof ↗⚑ flag

Reuse

1. developerA person verified once can be recognized and reused across sessions or products — documented re-verification and reuse of a prior passed check instead of forcing a full re-run

   weight 2 · round drawn
   Stripe Identity—none0/10

   Docs describe verification flows, blocklisting bad documents, and manual overrides, but there is no documented mechanism to recognize a previously-verified person and reuse their passed check to skip a new verification session across products/sessions. missing for 10: explicit reuse/verification-caching API, cross-session identity linking, documentation of skipping re-verification for a known verified user.

   • [claimed-docs] “Flows provide a way to save and reuse the same configuration across all of your integration interfaces.”
   • [claimed-docs] “You can use a flow’s static link to verify any number of your users.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   The evidence pack covers verification checks, workflows, webhooks, sandbox testing, and dashboard overrides, but nowhere documents a mechanism to recognize a previously verified user and reuse a passed check across sessions or products instead of re-running verification.

   ⚑ flag

Analytics

1. founderSee verification funnel analytics — pass rates, drop-off points, completion time by country and document type — to know what verification is costing me in signups

   weight 2 · round to Plaid Identity Verification
   Stripe Identity—none0/10

   Evidence covers verification session creation, review tools, and access to individual verification results, but nothing about aggregate funnel analytics (pass rates, drop-off points, completion time breakdowns by country/document type) that a founder could use to quantify signup cost. Missing for 10: dashboard/analytics UI for funnel metrics, aggregated pass-rate or drop-off reporting, completion-time-by-country/doc-type breakdowns.

   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed4/10

   Plaid documents a 'reporting' page defining conversion rate (session completion rate) and a Dashboard showing per-session risk scores, implying some analytics exist, but there is no evidence of drop-off-point analysis, completion-time metrics, or breakdowns by country or document type. missing for 10: drop-off funnel visualization, completion-time-by-country/document-type metrics, independent confirmation of dashboard analytics depth.

   • [claimed-docs] “The conversion rate is defined as the percentage of sessions begun that were completed, regardless of whether the user passed or failed veri…”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”

   proof ↗⚑ flag

Review

1. ops leadBorderline verifications land in a manual review queue with the full evidence — document images, extracted fields, check results — and reviewer decisions feed back into the record

   weight 2 · round drawn
   Stripe Identity~partialclaimed5/10

   Docs confirm access to full evidence (images, extracted fields, check results) via API and review tools that let a human override status or blocklist a document, which supports manual review workflows, but there's no documented dedicated 'manual review queue' UI for borderline cases, no explicit routing/escalation logic for borderline verifications, and no evidence that reviewer decisions are captured as structured feedback beyond a status override. missing for 10: a native queue/dashboard for borderline cases, explicit borderline-detection/escalation criteria, and structured reviewer-decision feedback loop into the verification record.

   • [claimed-docs] “Access collected images, and extracted data from government-issued ID documents”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”

   proof ↗⚑ flag

   Plaid Identity Verification~partialclaimed5/10

   Docs confirm a Dashboard-based review path — failed verifications can be manually overridden and each session shows risk assessments and status updates via webhooks — implying some human-in-the-loop review, but there is no explicit description of a dedicated 'manual review queue' surfacing document images/extracted fields for borderline cases, nor documented mechanics for how reviewer decisions are recorded back into the verification record beyond a simple override click. missing for 10: explicit manual review queue UI, evidence bundling (docs+fields+checks) presented together for review, and documented reviewer-decision audit trail feeding back into the record.

   • [claimed-docs] “you can override a failure via the Dashboard by clicking the Override Result button on the verification detail page in the Dashboard.”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”
   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “The conversion rate is defined as the percentage of sessions begun that were completed, regardless of whether the user passed or failed veri…”

   proof ↗⚑ flag

Workflows

1. ops leadConfigure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploy

   weight 3 · round to Plaid Identity Verification
   Stripe Identity~partialcommunity3/10

   Stripe Identity offers 'Flows' to save and reuse a verification configuration across integration surfaces without redeploying code, and review tools let ops manually override statuses or blocklist documents, but there is no evidence of a no-code UI for conditional branching, risk-based routing, or country-specific rule sets — most configuration (document types, session creation) still happens via API calls in docs examples. missing for 10: no-code conditional-step builder, risk-based routing rules, country-specific requirement configuration, and independent confirmation that Flows support these beyond simple reuse.

   • [claimed-docs] “Flows provide a way to save and reuse the same configuration across all of your integration interfaces.”
   • [claimed-docs] “You can use a flow’s static link to verify any number of your users.”
   • [claimed-docs] “Override status: Manually override the verification status to match your decision on whether or not the customer is verified.”
   • [claimed-docs] “Add to blocklist: Add the document to a blocklist to programmatically block future verifications completed with the same document.”
   • [community] “I like that it lets you specify the types of accepted docs. The biggest issue i have with Stripe identity verification product right now. An…”

   proof ↗⚑ flag

   Plaid Identity Verification✓fullclaimed8/10

   Plaid's docs explicitly describe a no-code Workflow Management editor for building templates, combining conditional checks (run only if another fails or is high-risk), and country-based routing, plus a dashboard for overrides and risk scoring—matching the ops-lead story closely. missing for 10: independent/hands-on validation of the no-code editor's actual usability and confirmation that template changes deploy without any engineering involvement in practice.

   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “No-code editor to create and change verification flows”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”
   • [claimed-docs] “you can override a failure via the Dashboard by clicking the Override Result button on the verification detail page in the Dashboard.”

   proof ↗⚑ flag

Monitoring

1. ops leadScreening is not one-shot — previously verified users are continuously re-screened against watchlist updates, and changes raise events I can act on

   weight 2 · round drawn
   Stripe Identity—none0/10

   Stripe Identity's evidence covers one-time document verification, selfie matching, SSN validation, and webhook-based verification-session outcomes, but there is no mention of watchlist/sanctions screening or continuous re-screening of previously verified users against watchlist updates. This is a plausible axis for an identity-verification product (competitors like Persona/Onfido offer ongoing AML monitoring), so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Match government-issued photo IDs with selfies, and validate Social Security numbers (SSNs)”
   • [claimed-docs] “Listen for verification results so your integration can automatically trigger reactions.”
   • [claimed-docs] “You can access most verification details programmatically... using your secret key.”

   proof ↗⚑ flag

   Plaid Identity Verification—none0/10

   Plaid IDV's webhooks (STEP_UPDATED, STATUS_UPDATED, RETRIED) fire during a verification session's flow, not as ongoing re-screening of already-verified users against new watchlist hits. The docs explicitly point to a separate product, Plaid Monitor, for continuous monitoring/KYC, implying IDV itself does not perform continuous re-screening.

   • [claimed-docs] “For Identity Verification, there are three events: STEP_UPDATED, STATUS_UPDATED, RETRIED”
   • [claimed-docs] “Monitor also integrates directly with Identity Verification for an end-to-end verification and KYC solution.”

   proof ↗⚑ flag

Screening

1. ops leadScreen verified users against sanctions, PEP, and adverse-media watchlists as part of the same verification — one vendor, one API, one review surface

   weight 2 · round to Plaid Identity Verification
   Stripe Identity—none0/10

   Evidence covers ID document verification, selfie matching, SSN validation, and review/override tools, but no mention of sanctions, PEP, or adverse-media watchlist screening anywhere in docs or community reports.

   ⚑ flag

   Plaid Identity Verification~partialclaimed5/10

   Plaid's docs show that its separate Monitor product 'integrates directly with Identity Verification for an end-to-end verification and KYC solution,' implying sanctions/PEP/adverse-media screening is available from the same vendor, but the evidence never describes this as a single unified API call or review surface — it reads as two distinct products stitched together rather than one seamless verification session. Missing for 10: explicit documentation of sanctions/PEP/adverse-media screening as a native check within the IDV template/workflow itself, unified webhook/events covering watchlist results, and independent confirmation of a single review surface across both products.

   • [claimed-docs] “Monitor also integrates directly with Identity Verification for an end-to-end verification and KYC solution.”
   • [claimed-docs] “You can combine multiple verification checks within a single Identity Verification template via the Workflow Management editor, and even run…”
   • [claimed-docs] “Identity Verification will also display a set of granular risk assessments (email risk, phone risk, etc.) in the Dashboard for each session,…”

   proof ↗⚑ flag