Identity Verification & KYC Arena
Veriff vs Plaid Identity Verification
Veriff wins · 14–11 (22 drawn)
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 VeriffVeriff hosts a live llms.txt at devdocs.veriff.com/llms.txt (confirmed HTTP 200 via probe) that indexes structured dev docs, directly enabling an AI agent to be pointed at agent-oriented documentation. Missing for 10: no OpenAPI/machine-readable spec (openapi.json 404s) and no explicit vendor messaging about AI-agent consumption of the docs.
- [probe] “PROBE llms.txt: HTTP 200 at https://devdocs.veriff.com/llms.txt # Veriff Dev Documentation > Knowledge base documentation for Veriff Dev Do…”
- [claimed-docs] “Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
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/”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to VeriffVeriff exposes a REST API (create session, poll decision, webhooks) and dedicated test integrations where decisions can be triggered programmatically without paid usage, which supports scripted/CI-style testing of the integration logic. However, the core verification itself requires an end-user completing an SDK-driven capture flow, so full headless automation of real verifications is not documented. missing for 10: explicit CI/automation guide, example of running full flow with no human/SDK interaction, and any mention of CI pipelines or automation frameworks.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Any verification session done in the test integrations **do not count towards paid usage**.”
- [claimed-docs] “You can trigger decisions for test integration sessions.”
- [claimed-docs] “Batch upload tests are **sometimes** agreed with Veriff onboarding team and are **very use case specific**.”
Plaid Identity Verificationnone0/10Evidence 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, …”
ai-native userConnect an agent via an official MCP server
weight 3 · round to Plaid Identity VerificationVeriffnone0/10Veriff is an identity verification SaaS with a REST API, SDKs, and webhooks, but no evidence of an official MCP server for agent connectivity; this is a fair axis for a SaaS API product, so absence of evidence yields none.
- [claimed-docs] “Pass end-user data via API and check out endpoint behavior”
- [claimed-docs] “Bring the end-user to verification flow using web or native SDKs”
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
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/”
ai-native userUse an official CLI
weight 2 · round drawnVeriffnone0/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.)
ai-native userDrive the product through a documented public API
weight 3 · round to VeriffVeriff exposes a documented REST API (session creation, decision polling, HMAC-signed webhooks, authentication) with dedicated devdocs, matching an AI-native user's need to drive the product programmatically. Missing for 10: a discoverable OpenAPI/Swagger spec (probe found only 404s) and independent third-party confirmation of API usage.
- [claimed-docs] “Pass end-user data via API and check out endpoint behavior”
- [claimed-docs] “the shared secret key, used to create the X-HMAC-SIGNATURE header”
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpo…”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
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/”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnVeriffnone0/10Veriff's API auth model is a single shared-secret HMAC key (X-HMAC-SIGNATURE) plus optional IP allowlisting, not a scoped/least-privilege credential system with per-agent roles or permissions. No evidence of API key scoping, granular roles, or credential issuance tailored to individual agents.
- [claimed-docs] “the shared secret key, used to create the X-HMAC-SIGNATURE header”
- [claimed-docs] “Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpo…”
ai-native userBuild against official SDKs
weight 2 · round to Plaid Identity VerificationVeriff docs reference web and native SDKs plus a REST API with webhooks and HMAC auth, giving developers official building blocks, but there is no OpenAPI/swagger spec (probe found 404s) and no evidence of language-specific SDK repos, versioning, or AI-agent-friendly machine-readable schemas. Missing for 10: OpenAPI/machine-readable spec, list of concrete SDK languages/repos, independent developer corroboration.
- [claimed-docs] “Bring the end-user to verification flow using web or native SDKs”
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpo…”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
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, …”
ai-native userSubscribe to events via webhooks
weight 2 · round to VeriffVeriff has documented webhook support with HMAC-signed payloads for verification decisions, including setup docs and security details (X-HMAC-SIGNATURE, IP allowlisting), which allows event-driven/agentic integration rather than only polling. Missing for 10: no independent/hands-on corroboration of webhook reliability or payload schema details, and no explicit mention of event types beyond decision webhooks.
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “the shared secret key, used to create the X-HMAC-SIGNATURE header”
- [claimed-docs] “Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpo…”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
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.”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round drawnVeriffnone0/10Evidence covers identity verification APIs, webhooks, HMAC auth, manual review portal, and pricing add-ons, but nothing indicates AI-generated insights or suggestions surfaced to users from their data. This is a verification/fraud-check product, not an analytics/insight tool, and no such feature is documented.
Plaid Identity Verificationnone0/10Evidence 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/”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnVeriff's API supports asynchronous background processing via webhooks and decision polling (create a session, then get notified via webhook when a decision is ready), which enables automations that run without direct user interaction. However, there is no evidence of AI-agent-specific orchestration, scheduling, or autonomous multi-step workflow tooling beyond basic webhook/polling patterns. Missing for 10: explicit support for autonomous agent orchestration, scheduled/triggered workflows beyond single verification sessions, and any AI-native automation framework or SDK.
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “You can trigger decisions for test integration sessions.”
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.”
ai-native userOperate the product with natural-language commands
weight 2 · round to Plaid Identity VerificationVeriffnone0/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.)
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”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnVeriffnone0/10Veriff's devdocs describe API endpoints (sessions, webhooks, HMAC auth) but there is no evidence of an interactive reference with runnable/try-it examples; a probe for OpenAPI/Swagger specs at devdocs.veriff.com returned 404s, indicating no machine-readable spec backing an interactive console.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
Plaid Identity Verificationnone0/10No evidence of an interactive API reference with runnable examples; OpenAPI spec probes returned 404s and docs are plain markdown pages, not interactive/runnable explorer.
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnVeriffnone0/10Explicit probe evidence shows all common OpenAPI/Swagger spec paths return 404, and no documented download link for a machine-readable spec exists anywhere in the docs pack.
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
- [probe] “PROBE llms.txt: HTTP 200 at https://devdocs.veriff.com/llms.txt # Veriff Dev Documentation > Knowledge base documentation for Veriff Dev Do…”
Plaid Identity Verificationnone0/10Probes 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.
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnVeriff explicitly documents test integrations where sessions 'do not count towards paid usage' and decisions can be manually triggered without real verification data, effectively serving as a sandbox for API testing. missing for 10: no explicit mention of full data isolation guarantees, no independent/hands-on confirmation of sandbox fidelity, and OpenAPI spec probes returned 404 suggesting limited machine-readable API test tooling.
- [claimed-docs] “Any verification session done in the test integrations **do not count towards paid usage**.”
- [claimed-docs] “You can trigger decisions for test integration sessions.”
- [claimed-docs] “Batch upload tests are **sometimes** agreed with Veriff onboarding team and are **very use case specific**.”
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…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnVeriffnone0/10Evidence shows Veriff's API uses versioned paths (e.g. /v1/sessions) but there is no documentation of a versioning scheme, deprecation policy, changelog, or sunset timeline; OpenAPI spec probes returned 404. Missing for 10: documented API versioning/deprecation policy, changelog or migration guides, and any explicit commitment to backward compatibility.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
Plaid Identity Verificationnone0/10No 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…”
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 VeriffVeriff's API is built around creating and polling individual verification sessions (docs-6, docs-7), with no documented bulk/batch API endpoint for processing many items in one call. The only mention of batch capability is 'Batch upload tests' that are ad-hoc, negotiated with the onboarding team, and 'very use case specific' rather than a standard bulk feature. Missing for 10: a documented bulk/batch API endpoint, SDK support for multi-item submission, and evidence of automated large-scale batch processing.
- [claimed-docs] “Batch upload tests are **sometimes** agreed with Veriff onboarding team and are **very use case specific**.”
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
Plaid Identity Verificationnone0/10No 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.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Plaid Identity VerificationVeriff supports webhooks to notify external systems of verification events, which is a basic building block for event-driven automation, but there is no evidence of a rule-definition system or conditional logic engine that lets users configure custom triggers/actions within Veriff itself. missing for 10: rule engine or conditional automation builder, evidence of user-configurable trigger logic beyond simple webhook delivery, AI-native automation tooling.
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “You can trigger decisions for test integration sessions.”
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”
Biometric liveness — stories about biometric liveness in this arenaBiometric liveness
Stories about biometric liveness in this arena
Deepfake defense
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 drawnVeriffnone0/10The only relevant evidence (veriff-docs-11) is a single generic marketing-style sentence claiming the liveness solution 'ensures biometric data is from a live person' — it names no specific detection capabilities (e.g., anti-spoofing models, deepfake detection, camera-injection detection) as the story requires. Missing for 10: named technical defenses against AI-generated faces, deepfake detection methodology, camera/virtual-camera injection detection, and any independent validation of these claims.
- [claimed-docs] “Veriff Biometric Liveness solution ensures that the biometric data being captured is from a live person, significantly reducing the risk of …”
Plaid Identity Verificationnone0/10The 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.
Duplicate detection
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 drawnVeriffnone0/10Evidence covers session creation, webhooks, HMAC auth, biometric liveness (live-person spoof detection) and manual review in the portal, but nothing describes cross-session duplicate/repeat-identity detection (e.g., flagging the same face or document reappearing under a different name). Biometric liveness [veriff-docs-11] only addresses spoof/liveness, not identity deduplication across verifications.
- [claimed-docs] “Veriff Biometric Liveness solution ensures that the biometric data being captured is from a live person, significantly reducing the risk of …”
- [claimed-docs] “Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [claimed-docs] “Manually: the **Verifications page in the** Veriff Customer Portal”
Plaid Identity Verificationnone0/10The 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…”
Liveness
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 VeriffVeriff's docs confirm a dedicated biometric liveness feature that verifies the captured biometric data comes from a live person, matching the core story of selfie-to-document liveness matching, but there is no detail on specific anti-spoofing defenses (printed photo, screen replay, video injection) or any independent certification/testing evidence. Missing for 10: documented defenses against specific spoof types (print/screen/replay), independent liveness certification (e.g., iBeta/NIST), and hands-on/third-party validation of match accuracy.
- [claimed-docs] “Veriff Biometric Liveness solution ensures that the biometric data being captured is from a live person, significantly reducing the risk of …”
Plaid Identity Verificationnone0/10The 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.
Data checks — stories about data checks in this arenaData checks
Stories about data checks in this arena
Db checks
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 Plaid Identity VerificationVeriffnone0/10All evidence describes Veriff's document- and biometric-based verification flows (session creation, SDKs, webhooks, liveness) plus a PEP/Sanctions add-on, but nothing shows a no-document database-only check against SSN, national registry, or credit-header data. missing for 10: any API/doc showing a no-doc data-only verification mode, evidence of SSN/registry/credit-header lookups.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Veriff Biometric Liveness solution ensures that the biometric data being captured is from a live person, significantly reducing the risk of …”
- [claimed-docs] “PEP & Sanctions check (+$0.64)”
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.”
Kyb
ops leadVerify businesses, not just people — registry lookups, UBO identification, and documented KYB flows that chain into KYC on the owners
weight 2 · round drawnVeriffnone0/10All evidence describes person-level identity verification (KYC) via sessions, SDKs, webhooks, biometric liveness, and PEP/sanctions checks; nothing addresses business registry lookups, UBO identification, or a documented KYB flow chaining into KYC of owners. Missing for 10: business registry/company lookup API, UBO identification workflow, KYB-to-KYC chaining documentation, any KYB product page or endpoint.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “PEP & Sanctions check (+$0.64)”
- [claimed-docs] “Veriff Biometric Liveness solution ensures that the biometric data being captured is from a live person, significantly reducing the risk of …”
Plaid Identity Verificationnone0/10All 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.”
Risk signals
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 VerificationVeriffnone0/10Evidence covers document/biometric verification, webhooks, HMAC auth, and PEP & sanctions checks, but nothing documents phone/email/device risk signals such as carrier checks, address history, or device fingerprinting as check types.
- [claimed-docs] “Veriff Biometric Liveness solution ensures that the biometric data being captured is from a live person, significantly reducing the risk of …”
- [claimed-docs] “PEP & Sanctions check (+$0.64)”
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,…”
Document coverage — stories about document coverage in this arenaDocument coverage
Stories about document coverage in this arena
Doc types
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 VerificationVeriffnone0/10The evidence pack contains only API/SDK/webhook integration docs, HMAC auth, biometric liveness, and pricing add-ons — none of it lists supported countries or document types (passports, national IDs, driver licenses, residence permits) or points to a published coverage list.
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…”
Extraction
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 Plaid Identity VerificationVeriffnone0/10The evidence pack shows session creation, decision polling, and webhook endpoints, but nothing documents that extracted document fields (name, DOB, document number, address, expiry) are returned as structured data via the API — only pass/fail-style 'decision' retrieval is mentioned.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “You can trigger decisions for test integration sessions.”
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.”
Idv agent access — stories about idv agent access in this arenaIdv agent access
Stories about idv agent access in this arena
Agent decisions
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 drawnVeriff's API returns structured decision data via session creation, polling GET /v1/sessions/{id}/decision, and webhooks with HMAC-verified payloads, which an automated flow could branch on; docs also mention risk-related add-ons like PEP & Sanctions checks. However, there's no evidence of a documented schema for risk signals/failure-reason codes, no OpenAPI spec (probe found 404s), and manual review via the Customer Portal is emphasized alongside automation, suggesting outcomes aren't always fully machine-resolved. Missing for 10: published response schema/enum of failure reasons and risk signal fields, OpenAPI spec for structured parsing, and evidence of fully automated (non-manual-review) decisioning suitable for agent branching.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpo…”
- [claimed-docs] “Manually: the **Verifications page in the** Veriff Customer Portal”
- [claimed-docs] “PEP & Sanctions check (+$0.64)”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
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.”
Agent operations
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 VeriffVeriff's API supports the core pipeline pieces an agent would need: creating sessions (veriff-docs-6), polling decision status (veriff-docs-7), webhook-based outcome delivery (veriff-docs-3), and scoped credential auth via HMAC/shared-secret and IP allowlisting (veriff-docs-5, veriff-docs-10). However there is no MCP server or agent-oriented surface, no clear 'retrieve extracted data' endpoint distinct from decision polling, and re-check/decision-triggering is only documented for test integrations (veriff-docs-9), not general production re-checks; a probe for a machine-readable OpenAPI spec also 404'd (veriff-probe-2). missing for 10: MCP surface, documented extracted-data retrieval endpoint, production re-check trigger, discoverable OpenAPI schema.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “the shared secret key, used to create the X-HMAC-SIGNATURE header”
- [claimed-docs] “Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpo…”
- [claimed-docs] “You can trigger decisions for test integration sessions.”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
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/”
Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx
Sandboxes, test modes, webhooks, and how fast a developer gets to a working integration
Sandbox
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 VerificationVeriff docs confirm a test integration mode where sessions don't count toward paid usage and where developers can explicitly trigger decisions for test sessions, supporting a sandbox-like exercise of outcomes. However, there's no documented catalog of specific test documents/personas or magic values that deterministically map to pass/fail/review, and batch/service-quality testing is described as ad hoc and use-case-specific rather than self-serve. Missing for 10: documented magic-value/test-document list per outcome, self-serve deterministic mapping without onboarding-team coordination, independent confirmation of sandbox fidelity.
- [claimed-docs] “Any verification session done in the test integrations **do not count towards paid usage**.”
- [claimed-docs] “You can trigger decisions for test integration sessions.”
- [claimed-docs] “Batch upload tests are **sometimes** agreed with Veriff onboarding team and are **very use case specific**.”
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…”
Session api
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 VeriffDocs clearly cover creating a session, polling for decision/status, webhooks, and passing end-user data (veriff-docs-1, veriff-docs-6, veriff-docs-7, veriff-docs-3), but there's no evidence of API endpoints for retrieving captured media, or for cancelling/redacting a session — review/management is instead shown via the Customer Portal UI (veriff-docs-12, veriff-docs-13), not the API. missing for 10: documented API endpoints for retrieving captured media, and for cancel/redact/delete operations.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Pass end-user data via API and check out endpoint behavior”
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [claimed-docs] “Manually: the **Verifications page in the** Veriff Customer Portal”
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”
Webhooks
developerVerification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling
weight 2 · round to VeriffVeriff docs confirm webhooks are the primary integration path (with polling only as a fallback) and that responses are authenticated via HMAC signature headers, matching the 'signed webhooks instead of polling' pattern. However, the evidence never enumerates the specific lifecycle event types (created, processing, verified, requires-input) or shows a payload schema/event-type list confirming granular status callbacks. Missing for 10: explicit event-type/status enumeration in webhook payloads, sample payload showing verification state transitions, independent/hands-on confirmation of signature verification working in practice.
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “the shared secret key, used to create the X-HMAC-SIGNATURE header”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpo…”
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.”
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 to VeriffVeriff's API covers the core verification lifecycle (session creation, decision retrieval, webhooks, HMAC auth) per veriff-docs-6/7/3/10, but its own docs show manual review and case management are portal-only ('Verifications page in the Veriff Customer Portal', veriff-docs-12/13), and PDF export appears tied to the portal (veriff-docs-14), indicating UI-only functionality not mirrored in the API. No OpenAPI spec is discoverable (veriff-probe-2), limiting confidence that full API parity/documentation exists for programmatic exploration. Missing for 10: evidence of API endpoints for manual review/case management, PDF export via API, and a public OpenAPI spec confirming full endpoint coverage.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpo…”
- [claimed-docs] “Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [claimed-docs] “Manually: the **Verifications page in the** Veriff Customer Portal”
- [claimed-docs] “Export verification session details to PDF”
- [probe] “PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.ve…”
Plaid Identity Verificationnone0/10Evidence 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, …”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnVeriffnone0/10Veriff's docs mention exporting verification session details to PDF for business customers reviewing cases, but there is no evidence of an end-user-facing mechanism to export all personal/identity data in open, machine-readable formats (JSON/CSV) and delete one's account. The axis applies since Veriff stores significant PII/biometric data, but no comprehensive data-portability feature is documented.
- [claimed-docs] “Export verification session details to PDF”
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 drawnVeriffnone0/10No evidence pack items mention data residency, regional storage options, or GDPR-style data localization controls; none of the docs address where verification data is stored or configurable region choice.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnVeriffnone0/10No evidence in the pack addresses AI training data opt-out or any privacy controls related to preventing use of user data for AI model training; the documentation covers verification API/SDK/webhook mechanics only.
ai-native userControl data retention and deletion
weight 2 · round drawnVeriffnone0/10Evidence covers session creation, webhooks, HMAC security, and manual review, but nothing addresses data retention periods, deletion requests, or user-initiated data control/removal APIs.
Plaid Identity Verificationnone0/10The 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 …”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnVeriffnone0/10Veriff is an identity-verification API/service and its evidence pack covers session APIs, webhooks, HMAC security, and biometric liveness, but there is no mention of telemetry/usage tracking or any opt-out mechanism for such tracking.
Privacy retention — stories about privacy retention in this arenaPrivacy retention
Stories about privacy retention in this arena
Consent
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 drawnVeriffnone0/10The evidence pack only covers API/SDK integration mechanics, biometric liveness feature descriptions, and pricing — there is no documentation of GDPR legal bases, BIPA or other US biometric statute compliance, or consent language guidance for legal review.
Plaid Identity Verificationnone0/10The 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.
Redaction
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 drawnVeriffnone0/10Evidence covers session creation, decisions, webhooks, HMAC auth, and manual review in the portal, but nothing documents data retention windows or a redaction/deletion API for scrubbing PII on demand.
Plaid Identity Verificationnone0/10The 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,…”
Verification flows — stories about verification flows in this arenaVerification flows
Stories about verification flows in this arena
Hosted flows
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 VeriffDocs confirm the core flow: create a session server-side via POST /v1/sessions, bring the end-user to verification via hosted or embedded web/native SDKs, and read results via webhook or by polling the decision endpoint — covering document+selfie/liveness capture without building custom capture UI. missing for 10: no independent/hands-on developer corroboration of the end-to-end flow and no explicit confirmation that both document and selfie capture are bundled by default in the hosted flow.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Bring the end-user to verification flow using web or native SDKs”
- [claimed-docs] “Set up webhooks to get responses from Veriff”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Veriff Biometric Liveness solution ensures that the biometric data being captured is from a live person, significantly reducing the risk of …”
- [claimed-docs] “No-code identity verification solution”
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”
Native sdks
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 to VeriffDocs confirm native and web SDKs exist for bringing users into the verification flow, but there is no evidence describing guided capture UX details like glare, blur, or edge detection coaching. missing for 10: SDK feature documentation on real-time image quality checks, glare/blur detection, edge detection guidance, and any independent/hands-on validation of first-try capture success.
- [claimed-docs] “Bring the end-user to verification flow using web or native SDKs”
- [claimed-docs] “Veriff Biometric Liveness solution ensures that the biometric data being captured is from a live person, significantly reducing the risk of …”
Plaid Identity Verificationnone0/10The 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…”
No code
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 VeriffVeriff explicitly advertises a 'No-code identity verification solution' (veriff-docs-4) and a Customer Portal for managing verifications (veriff-docs-12/13), suggesting some no-code capability exists, but the evidence pack never details a shareable link or QR-code workflow, session creation without API/engineering involvement, or a portal UI for generating one-off verification requests. Missing for 10: explicit documentation of link/QR-code generation in the portal, confirmation that ops staff (not engineers) can trigger sessions without API calls, and any UI screenshots or workflow docs for one-off verification requests.
- [claimed-docs] “No-code identity verification solution”
- [claimed-docs] “Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [claimed-docs] “Manually: the **Verifications page in the** Veriff Customer Portal”
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…”
Reuse
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 drawnVeriffnone0/10The evidence pack covers session creation, decisions, webhooks, HMAC auth, and manual review, but nothing documents identity reuse/portability — e.g., a 'reuse prior passed verification' or cross-session/cross-product identity linking feature. Each session creation doc (veriff-docs-6) implies a fresh verification flow rather than recognizing a previously verified person.
- [claimed-docs] “Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
Plaid Identity Verificationnone0/10The 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.
Verification orchestration — stories about verification orchestration in this arenaVerification orchestration
Stories about verification orchestration in this arena
Analytics
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 VerificationVeriffnone0/10Evidence covers session creation, webhooks, HMAC auth, manual review portal, and PDF export, but nothing describes funnel analytics, pass-rate dashboards, drop-off analysis, completion-time metrics, or breakdowns by country/document type.
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,…”
Review
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 drawnDocs confirm a manual review queue exists in the Veriff Customer Portal (Verifications page) where sessions can be reviewed and decisions triggered/exported, and webhooks/API decision endpoints propagate results back into the record. However, the evidence pack does not detail what evidence reviewers see (document images, extracted fields, check results) or explicitly describe how reviewer decisions are written back to the underlying verification record beyond the decision endpoint. Missing for 10: documentation of the reviewer UI's evidence display (images/fields/check results), explicit reviewer-decision-to-record feedback mechanism, and independent/hands-on corroboration.
- [claimed-docs] “Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [claimed-docs] “Manually: the **Verifications page in the** Veriff Customer Portal”
- [claimed-docs] “You can trigger decisions for test integration sessions.”
- [claimed-docs] “Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] “Set up webhooks to get responses from Veriff”
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…”
Workflows
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 VerificationThe devdocs reference a 'No-code identity verification solution' and a Customer Portal for managing verification sessions/decisions, suggesting some no-code configuration exists, but there is no concrete evidence of conditional step logic, risk-based routing, country-specific requirement rules, or template editing without an engineering deploy. missing for 10: documented conditional/branching logic builder, risk-based routing rules, country-specific requirement configuration, and template editing workflow evidence.
- [claimed-docs] “No-code identity verification solution”
- [claimed-docs] “Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [claimed-docs] “Manually: the **Verifications page in the** Veriff Customer Portal”
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.”
Watchlist screening — stories about watchlist screening in this arenaWatchlist screening
Stories about watchlist screening in this arena
Monitoring
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 drawnVeriffnone0/10Evidence only shows a one-time PEP & Sanctions check at verification time and generic webhooks for session decisions; there is no mention of continuous re-screening of previously verified users against updated watchlists or of events triggered by post-verification watchlist changes.
- [claimed-docs] “PEP & Sanctions check (+$0.64)”
- [claimed-docs] “Set up webhooks to get responses from Veriff”
Plaid Identity Verificationnone0/10Plaid 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.”
Screening
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 VeriffVeriff's pricing page confirms a PEP & Sanctions check add-on ($0.64) that integrates into the same verification flow/API, and the Customer Portal already supports manual review of verification sessions, suggesting one vendor/API for both identity and watchlist screening. However, adverse-media screening is not explicitly mentioned, and there's no dedicated documentation showing watchlist hits surfaced in the same review UI as biometric/identity results. Missing for 10: explicit adverse-media watchlist coverage, and documentation showing unified review surface combining identity + watchlist results.
- [claimed-docs] “PEP & Sanctions check (+$0.64)”
- [claimed-docs] “Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [claimed-docs] “Manually: the **Verifications page in the** Veriff Customer Portal”
- [claimed-docs] “Export verification session details to PDF”
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,…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableVeriffn/aVeriff is an identity-verification API/SaaS product, not an AI agent or MCP client; plugging MCP servers into it to extend its own tool use is not a fair axis for this product type, and no evidence suggests otherwise.
Plaid Identity Verificationn/aPlaid Identity Verification is a verification/KYC SaaS API, not an AI agent or assistant that itself consumes external tools via MCP; the evidence shows Plaid offers an MCP server (docs/resources/mcp) exposing its own APIs, which is the reverse (server) role, not the client-side 'plug MCP servers in so it can use their tools' capability this story asks about. This axis is a category error for a non-agentic verification product.
- [probe] “official MCP server documented at https://plaid.com/docs/resources/mcp/”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableVeriffn/aVeriff is an identity verification API/platform, not an agentic assistant product; there is no built-in AI assistant to delegate tasks to, and this axis is a category error for this type of product.
Plaid Identity Verificationn/aPlaid Identity Verification is a backend identity-verification/KYC API and dashboard product, not an AI assistant or agentic interface; delegating tasks to a built-in AI assistant is a category error for this type of product. Evidence shows no-code workflow editor and dashboard tools, not any conversational/agentic assistant.
- [claimed-docs] “No-code editor to create and change verification flows”
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableVeriffn/aVeriff is an identity verification API/service, not a workflow/job scheduling or automation platform; recurring job scheduling is outside its product category.
Plaid Identity Verificationn/aPlaid Identity Verification is a KYC/identity verification API/dashboard product, not an automation or workflow-scheduling platform; scheduling recurring jobs is outside its category (webhooks for event-driven updates exist, but not user-initiated recurring job scheduling).
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableVeriffn/aVeriff is an identity verification API/platform, not an automation/workflow tool with configurable automations that would need versioning, review, or rollback — this axis is a category error for this product type.
ai-native userRead the product's source under an open license
weight 2 · not comparableVeriffnone0/10Veriff is a closed-source identity verification SaaS; evidence shows only API docs, SDKs, and dashboard features, with no source code repository or open license mentioned anywhere.
ai-native userSelf-host the core product
weight 3 · not comparableVeriffn/aVeriff is a cloud-based identity verification SaaS API service; self-hosting the core verification engine is not a category-appropriate axis for this type of product, and no evidence suggests an on-prem/self-host offering.