Identity Verification & KYC Arena
Persona vs Plaid Identity Verification
Plaid Identity Verification wins · 8–13 (24 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 PersonaPersona hosts an llms.txt file (confirmed via direct probe returning HTTP 200) with explicit instructions for AI agents on how to fetch clean Markdown docs, and the docs themselves are consistently available in .md form as referenced throughout the evidence pack. missing for 10: no independent/third-party corroboration of agent usage, and no explicit sitemap of all docs within llms.txt shown.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.withpersona.com/llms.txt # Persona ## Instructions for AI Agents - For clean Markdown of any page…”
- [claimed-docs] “The Persona API is a powerful tool that enables you to integrate identity verification, risk assessment, and compliance solutions into your …”
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 PersonaPersona is API-first and provides a sandbox with 'Simulate Actions' explicitly designed for programmatic/CI-style integration testing (persona-docs-9, persona-docs-3), implying headless automation is possible. However, there is no explicit CLI, SDK automation guide, or CI pipeline documentation describing headless operation for AI-native workflows. Missing for 10: dedicated CI/headless automation guide, CLI or agent-facing tooling, explicit statement of non-interactive/headless operation modes.
- [claimed-docs] “the following Simulate Actions can be specified to evoke Inquiry and Verification lifecycle behavior, thereby replicating the necessary cond…”
- [claimed-docs] “Sandbox mode is provided so that you can test your integration without incurring any usage charges. Real verifications are not performed wit…”
- [claimed-docs] “The Persona API is a powerful tool that enables you to integrate identity verification, risk assessment, and compliance solutions into your …”
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 VerificationPersonanone0/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 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 drawnPersonanone0/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 PersonaPersona provides a well-documented public API covering core resources (inquiries, workflows, reports, webhooks), sandbox/simulate testing tools, and an llms.txt for AI-agent consumption, enabling programmatic driving of the product. Missing for 10: independent/hands-on developer corroboration and explicit SDK/language client examples beyond docs claims.
- [claimed-docs] “The Persona API is a powerful tool that enables you to integrate identity verification, risk assessment, and compliance solutions into your …”
- [claimed-docs] “Webhooks can notify your service about events that happen on any Persona resource.”
- [claimed-docs] “Sandbox mode is provided so that you can test your integration without incurring any usage charges. Real verifications are not performed wit…”
- [claimed-docs] “the following Simulate Actions can be specified to evoke Inquiry and Verification lifecycle behavior, thereby replicating the necessary cond…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.withpersona.com/llms.txt # Persona ## Instructions for AI Agents - For clean Markdown of any page…”
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 drawnPersonanone0/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 userBuild against official SDKs
weight 2 · round to Plaid Identity VerificationPersonanone0/10The evidence pack covers Persona's API reference, webhooks, sandbox testing, and inquiry/workflow docs, but nowhere mentions official client SDKs or language-specific libraries for developers to build against. Missing for 10: any mention of published SDKs (e.g., Node, Python, Ruby, Java) or SDK documentation/repos.
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 drawnPersona's docs explicitly confirm webhooks notify subscribers about events on any Persona resource, directly supporting event subscription via webhooks. Missing for 10: details on webhook payload structure, signature verification, event type filtering/configuration UI, and independent/hands-on confirmation of reliability.
- [claimed-docs] “Webhooks can notify your service about events that happen on any Persona resource.”
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 drawnPersonanone0/10Evidence covers identity verification, workflows, webhooks, and testing tools but contains no mention of AI-generated insights or suggestions derived from user data within the product.
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 drawnPersona's Workflows feature explicitly automates repetitive manual decisions and decreases manual review time, and webhooks enable event-driven background reactions, giving a foundation for autonomous background automation within identity verification. However, this is domain-specific (identity/compliance) automation, not general-purpose agentic task automation, and there's no evidence of scheduling, triggers beyond identity events, or broader autonomous agent orchestration. Missing for 10: evidence of general-purpose scheduled/autonomous automation beyond identity workflows, independent confirmation of autonomous background execution, and detail on how workflows run without human intervention.
- [claimed-docs] “Workflows are a flexible, intuitive, and powerful way to streamline your identity processes. You can use them to automate repetitive manual …”
- [claimed-docs] “Webhooks can notify your service about events that happen on any Persona resource.”
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 VerificationPersonanone0/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 drawnPersonanone0/10Evidence shows standard API reference docs, sandbox/testing tools, and llms.txt for AI agents, but no mention of an interactive API reference with runnable/executable code examples (e.g., embedded try-it console).
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 drawnPersonanone0/10Evidence shows extensive API reference docs and an llms.txt file for AI-friendly markdown access, but nothing indicates a downloadable machine-readable spec like an OpenAPI/Swagger file or equivalent schema. missing for 10: OpenAPI/Swagger spec file, any explicit machine-readable schema download link.
- [claimed-docs] “The Persona API is a powerful tool that enables you to integrate identity verification, risk assessment, and compliance solutions into your …”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.withpersona.com/llms.txt # Persona ## Instructions for AI Agents - For clean Markdown of any page…”
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 to PersonaPersona provides explicit sandbox mode where no real verifications or charges occur, plus integration-testing simulate actions to replicate inquiry/verification lifecycle behavior for programmatic testing without touching production data. missing for 10: independent/third-party corroboration of sandbox data isolation and more detail on how sandbox-to-production promotion works.
- [claimed-docs] “Sandbox mode is provided so that you can test your integration without incurring any usage charges. Real verifications are not performed wit…”
- [claimed-docs] “the following Simulate Actions can be specified to evoke Inquiry and Verification lifecycle behavior, thereby replicating the necessary cond…”
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 drawnPersonanone0/10The evidence pack contains no mention of API versioning scheme or a documented deprecation policy anywhere in the docs; only general API/product feature descriptions are present. This is an applicable axis for an API-driven identity platform, so absence of evidence yields 'none'.
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 drawnPersonanone0/10Evidence covers identity verification workflows, inquiries, reports, and testing, but no mention of any bulk/batch operations API (e.g., bulk case creation, bulk report retrieval, batch processing endpoints) for AI-native automation. Absence of evidence for an applicable capability yields none.
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 drawnPersona's Workflows are documented as a way to automate repetitive manual decisions and decrease manual review time, and Webhooks notify external services about events on Persona resources, together enabling rule-based, event-triggered automation. However, the evidence lacks detail on how rules/conditions are authored (e.g., API-driven or only via a GUI workflow builder), and there is no independent or hands-on confirmation of this automation depth. Missing for 10: documentation on programmatic rule creation/API access to Workflows, and independent verification of automation behavior.
- [claimed-docs] “Workflows are a flexible, intuitive, and powerful way to streamline your identity processes. You can use them to automate repetitive manual …”
- [claimed-docs] “Webhooks can notify your service about events that happen on any Persona resource.”
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 drawnPersonanone0/10None of the evidence names specific liveness/deepfake/camera-injection detection capabilities; the pack only covers general API, webhooks, workflows, and testing tools with no mention of anti-spoofing or AI-generated face defenses.
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 drawnPersonanone0/10The evidence describes general Reports, inquiries, and reference-ID linking but never mentions automatic cross-verification duplicate/repeat identity detection (e.g., matching the same face or document under different names). This is a plausible capability for an identity verification platform, so the axis applies, but no evidence supports it here.
- [claimed-docs] “Reports provide additional information about an end user beyond what they submit directly in an inquiry.”
- [claimed-docs] “To link multiple inquiries to the same account, use the same reference ID for each inquiry.”
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 drawnPersonanone0/10The evidence pack covers general Persona API/product features (webhooks, sandbox, workflows, reports, hosted flow) but contains no documentation of selfie/liveness verification mechanics or anti-spoofing defenses against printed photos, screens, or replayed video.
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 VerificationPersonanone0/10The evidence pack only describes generic Persona concepts (API, webhooks, workflows, reports, inquiry templates) but never mentions SSN checks, credit-header/database verification, or document-free flows explicitly. Missing for 10: no docs on SSN/national-registry verification methods, no mention of credit-header data checks, no example of a document-free inquiry template.
- [claimed-docs] “Reports provide additional information about an end user beyond what they submit directly in an inquiry.”
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
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 drawnPersonanone0/10Evidence covers Persona's individual identity verification (inquiries, workflows, reports, sandbox testing) but nothing about business verification, registry lookups, UBO identification, or KYB flows chaining into KYC on owners is mentioned anywhere in the pack.
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 VerificationPersonanone0/10The evidence only mentions generic 'Reports' providing additional info beyond inquiry submissions, but there is no documentation of specific phone, email, device fingerprint, carrier check, or address history check types. missing for 10: phone risk report docs, email risk report docs, device fingerprinting docs, carrier check docs, address history docs.
- [claimed-docs] “Reports provide additional information about an end user beyond what they submit directly in an inquiry.”
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 VerificationPersonanone0/10The evidence pack covers Persona's API, webhooks, sandbox, workflows, inquiry templates, and reports, but none of the cited docs actually publish a supported list of countries or document types (passports, national IDs, driver licenses, residence permits). Absence of this published coverage list means the specific ops-facing claim cannot be verified.
- [claimed-docs] “The Persona API is a powerful tool that enables you to integrate identity verification, risk assessment, and compliance solutions into your …”
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
- [claimed-docs] “Reports provide additional information about an end user beyond what they submit directly in an inquiry.”
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 VerificationPersonanone0/10Persona is an identity verification platform where extracting structured document fields via API is a core plausible capability, but the evidence pack contains no documentation confirming that verified sessions return structured fields (name, DOB, document number, address, expiry) through the API — only generic references to inquiries, reports, and workflows.
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 drawnPersona's API/webhook model exposes inquiries, verifications, reports, and workflow decisioning as structured resources that could be consumed programmatically, and webhooks notify integrators of lifecycle events for branching logic. However the evidence never shows a concrete schema of machine-readable risk signals or enumerated failure/decline reasons an agent could parse. Missing for 10: example API/webhook payloads showing explicit risk-signal fields, structured failure-reason codes, and documentation confirming these are designed for autonomous agent branching rather than human review dashboards.
- [claimed-docs] “Webhooks can notify your service about events that happen on any Persona resource.”
- [claimed-docs] “Workflows are a flexible, intuitive, and powerful way to streamline your identity processes. You can use them to automate repetitive manual …”
- [claimed-docs] “Reports provide additional information about an end user beyond what they submit directly in an inquiry.”
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
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 Plaid Identity VerificationPersonanone0/10Evidence shows a general REST API, webhooks, sandbox, and docs for inquiries/workflows, but nothing about scoped API credentials for agent use, session polling/re-check triggering designed for AI agents, or any MCP surface at all.
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 VerificationPersona documents sandbox mode with no usage charges and no real verifications performed, plus a dedicated integration-testing doc describing 'Simulate Actions' to evoke specific Inquiry/Verification lifecycle behaviors for programmatic testing — this maps to deterministic pass/fail/review triggering. However, the evidence does not spell out concrete magic values or a full documented enumeration of every possible outcome (e.g., specific review-state triggers), so coverage of 'every outcome' is not fully substantiated. missing for 10: explicit list of magic values/test documents mapped to each outcome, independent/hands-on confirmation that simulate actions reliably produce all three outcome types.
- [claimed-docs] “Sandbox mode is provided so that you can test your integration without incurring any usage charges. Real verifications are not performed wit…”
- [claimed-docs] “the following Simulate Actions can be specified to evoke Inquiry and Verification lifecycle behavior, thereby replicating the necessary cond…”
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 drawnDocs confirm a broad API surface (inquiries, workflows, reports, webhooks, sandbox testing) implying session creation and reference-linking, but the evidence never explicitly documents status-check endpoints, retrieving captured media, or cancel/redact operations via API. missing for 10: explicit endpoint docs for get-status, retrieve captured media, cancel inquiry, and redact/delete data.
- [claimed-docs] “The Persona API is a powerful tool that enables you to integrate identity verification, risk assessment, and compliance solutions into your …”
- [claimed-docs] “Reports provide additional information about an end user beyond what they submit directly in an inquiry.”
- [claimed-docs] “the following Simulate Actions can be specified to evoke Inquiry and Verification lifecycle behavior, thereby replicating the necessary cond…”
- [claimed-docs] “To link multiple inquiries to the same account, use the same reference ID for each inquiry.”
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 drawnDocs confirm Persona webhooks notify services about events on any resource, supporting event-driven reaction without polling, but no evidence explicitly lists signed payload verification or the specific lifecycle event names (created, processing, verified, requires-input). missing for 10: documentation of webhook signature verification mechanism, explicit enumeration of inquiry lifecycle event types/names, and example payloads showing event schema.
- [claimed-docs] “Webhooks can notify your service about events that happen on any Persona resource.”
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 PersonaPersona exposes a broad API (inquiries, reports, webhooks, sandbox testing) covering the core verification workflow, but the evidence shows templates and Workflows are configured as visual building blocks (dashboard-defined 'screens, verifications, decisioning, theming') rather than something explicitly created/edited via API calls, so full UI/API parity isn't demonstrated. missing for 10: explicit evidence that inquiry templates and workflow logic can be authored/edited via API (not just triggered), and confirmation there's no dashboard-only configuration step required.
- [claimed-docs] “The Persona API is a powerful tool that enables you to integrate identity verification, risk assessment, and compliance solutions into your …”
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
- [claimed-docs] “Workflows are a flexible, intuitive, and powerful way to streamline your identity processes. You can use them to automate repetitive manual …”
- [claimed-docs] “Dynamic Flow Templates allow for greater flexibility in data collection by allowing custom UIs and collection fields along with dynamic fric…”
- [claimed-docs] “the following Simulate Actions can be specified to evoke Inquiry and Verification lifecycle behavior, thereby replicating the necessary cond…”
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, …”
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 drawnPersonanone0/10No evidence in the pack mentions data residency, regional storage options, or compliance controls letting users choose where data is stored; the docs cover API, webhooks, sandbox, workflows, and inquiries only.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnPersonanone0/10No evidence in the pack addresses AI-model training data usage or opt-out controls for Persona; the docs cover identity verification, workflows, and testing but nothing about AI training data policies.
ai-native userControl data retention and deletion
weight 2 · round drawnPersonanone0/10The evidence pack covers Persona's identity verification API, webhooks, sandbox testing, and workflows, but contains no documentation of data retention policies, deletion controls, or user-facing privacy management APIs. Nothing in the evidence addresses how an AI-native user could control retention windows or trigger deletion of stored PII/verification data.
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 …”
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 drawnPersonanone0/10None of the evidence addresses legal bases for biometric data processing, GDPR compliance, BIPA or other US biometric statutes, or model consent language — the docs pack only covers API mechanics, webhooks, sandbox testing, and inquiry/workflow configuration.
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 drawnPersonanone0/10The evidence pack covers Persona's API, webhooks, sandbox mode, inquiry templates, workflows, and reports, but contains no mention of data retention windows, PII redaction, or a deletion API. Missing for 10: documented retention policy, redaction/deletion API endpoints, evidence of on-demand PII scrubbing.
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 PersonaPersona's docs explicitly describe a Hosted Flow ('Redirect users to a Persona-hosted page... no frontend code required'), inquiry templates that define verification screens/decisioning, webhooks to read results, and sandbox/testing tools — matching the story's server-side session + redirect/embed + read-result pattern. Missing for 10: explicit mention of a 'drop-in' embeddable widget (only hosted flow is named), explicit document+selfie combination flow details, and a concrete server-side session-creation API example.
- [claimed-docs] “Method | What it is | Best for **Hosted Flow** | Redirect users to a Persona-hosted page | Fastest setup, no frontend code required”
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
- [claimed-docs] “Webhooks can notify your service about events that happen on any Persona resource.”
- [claimed-docs] “Sandbox mode is provided so that you can test your integration without incurring any usage charges. Real verifications are not performed wit…”
- [claimed-docs] “the following Simulate Actions can be specified to evoke Inquiry and Verification lifecycle behavior, thereby replicating the necessary cond…”
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 drawnPersonanone0/10Evidence pack contains only high-level docs about API, webhooks, workflows, and hosted flow setup, with no mention of native iOS/Android/web SDKs or guided camera capture features like glare, blur, and edge detection coaching.
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 PersonaDocs confirm a Hosted Flow option that requires no frontend code and can be shared as a link, supporting the no-code link fabric of the story, but there is no explicit evidence of QR code generation or of an ops-lead self-service dashboard flow for sending one-off verification links without engineering involvement. missing for 10: QR code generation, non-engineer/self-service link creation workflow, independent corroboration.
- [claimed-docs] “Method | What it is | Best for **Hosted Flow** | Redirect users to a Persona-hosted page | Fastest setup, no frontend code required”
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
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 to PersonaPersona supports linking multiple inquiries to the same underlying Account via a shared reference ID, which is the documented mechanism for recognizing a previously verified person across sessions/products, but the evidence pack doesn't show explicit re-verification logic that skips a full check re-run or reuses a prior passed verification result. Missing for 10: explicit documentation of automatic reuse/skip-of-full-verification logic, cross-product verification portability, and any 'verified once, reused elsewhere' workflow description.
- [claimed-docs] “To link multiple inquiries to the same account, use the same reference ID for each inquiry.”
- [claimed-docs] “Workflows are a flexible, intuitive, and powerful way to streamline your identity processes. You can use them to automate repetitive manual …”
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 VerificationPersonanone0/10Evidence covers inquiries, workflows, webhooks, sandbox testing, and reports, but nothing describes a dashboard or analytics feature showing pass rates, drop-off points, or completion time broken down by country or document type. Missing for 10: any mention of an analytics/reporting dashboard, funnel metrics, drop-off analysis, or country/document-type breakdowns.
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 to Plaid Identity VerificationPersona docs reference Workflows that automate decisions and 'decrease manual review time' and Reports/Inquiry data that could feed a review process, implying a manual review step exists, but there is no direct evidence of a review queue UI showing document images, extracted fields, and check results together, or of reviewer decisions writing back into the inquiry record. Missing for 10: explicit case-management/review queue documentation, evidence-bundling UI details, and confirmation that reviewer decisions update the verification record.
- [claimed-docs] “Workflows are a flexible, intuitive, and powerful way to streamline your identity processes. You can use them to automate repetitive manual …”
- [claimed-docs] “Reports provide additional information about an end user beyond what they submit directly in an inquiry.”
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
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 VerificationPersona's Workflows and Inquiry/Dynamic Flow Templates support no-code configuration of decisioning, conditional logic, and templating (persona-docs-4,5,7), which are core building blocks for ops-led verification orchestration without engineering deploys. However, the evidence never explicitly confirms a no-code UI for risk-based routing or country-specific requirement configuration, nor does it describe the actual Workflow Builder interface. missing for 10: explicit documentation/screenshots of the drag-and-drop Workflow Builder UI, country-specific rule configuration examples, and independent/hands-on confirmation that ops (non-engineers) can make these changes without any deploy.
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
- [claimed-docs] “Workflows are a flexible, intuitive, and powerful way to streamline your identity processes. You can use them to automate repetitive manual …”
- [claimed-docs] “Dynamic Flow Templates allow for greater flexibility in data collection by allowing custom UIs and collection fields along with dynamic fric…”
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 drawnPersonanone0/10The evidence pack covers Persona's general verification, webhooks, workflows, and reports, but nothing addresses watchlist screening specifically, let alone continuous re-screening of previously verified users against watchlist updates. Webhooks (persona-docs-2) notify on generic resource events but there's no documented watchlist-monitoring feature or recurring screening mechanism tied to it.
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 Plaid Identity VerificationPersonanone0/10The evidence pack describes Persona's general identity verification, workflows, reports, and inquiry templates, but none of the citations specifically mention sanctions, PEP, or adverse-media watchlist screening as part of the reports or verification suite. Without explicit documentation of a watchlist/sanctions screening report or API, this capability cannot be confirmed from the evidence.
- [claimed-docs] “Reports provide additional information about an end user beyond what they submit directly in an inquiry.”
- [claimed-docs] “The Persona API is a powerful tool that enables you to integrate identity verification, risk assessment, and compliance solutions into your …”
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 comparablePersonan/aPersona is an identity verification/compliance API platform, not an AI agent or assistant; MCP server plug-in for tool use is a category mismatch and not a fair axis for this product type.
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 comparablePersonan/aPersona is an identity verification/compliance API platform, not a product with a built-in AI assistant UI for task delegation; this axis is a category error for its product type.
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 comparablePersonan/aPersona is an identity verification/compliance API platform, not a workflow/task scheduling tool; 'workflows' here refer to event-driven decisioning pipelines triggered by identity events, not recurring cron-like job scheduling for AI-native automation. This axis is a category error for this product type.
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 comparablePersonanone0/10Persona's Workflows feature (docs-5) supports automation of decisioning, so the axis of versioning/reviewing/rolling back automations is applicable, but no evidence describes version history, review/approval flows, or rollback capability for Workflows or Inquiry Templates. Missing for 10: workflow version history, change review/approval process, rollback/revert mechanism.
- [claimed-docs] “Workflows are a flexible, intuitive, and powerful way to streamline your identity processes. You can use them to automate repetitive manual …”
- [claimed-docs] “Inquiry templates house the configuration for a single use case by defining the screens, verifications, decisioning, and theming.”
ai-native userExport all of my data in open formats and leave
weight 3 · not comparablePersonan/aPersona is an identity-verification/compliance API platform, not a data-hosting product where an end user accumulates personal content to export and leave with; the 'export all my data and leave' data-portability story is a category error for this product type.
ai-native userRead the product's source under an open license
weight 2 · not comparablePersonan/aPersona is a closed-source identity verification SaaS/API platform; there is no indication its source code is open at all. Source availability is not a relevant axis for a proprietary hosted verification service in the way it would be for an open-source library or framework, and no evidence suggests otherwise.
ai-native userSelf-host the core product
weight 3 · not comparablePersonan/aPersona is a hosted SaaS identity-verification API/service; self-hosting the core product is a category error for this type of product, not an evidenced gap.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparablePersonan/aPersona is an identity verification/compliance API product, not an AI coding tool or agent with telemetry settings relevant to an 'AI-native user' workflow; the evidence pack contains no mention of telemetry or usage tracking opt-out, and this axis is a category mismatch for this kind of product.