Stripe Identity vs Persona

Agent access

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

   weight 2 · round drawn
   Stripe Identity✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Persona✓fullprobed8/10

   Persona 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 …”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Persona~partialclaimed5/10

   Persona 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 …”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. ai-native userUse an official CLI

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

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

   weight 3 · round drawn
   Stripe Identity✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Persona✓fullprobed8/10

   Persona 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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Identity—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Persona—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

7. ai-native userBuild against official SDKs

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   ⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Stripe Identity✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Persona✓fullclaimed7/10

   Persona'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.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

   ⚑ flag

   Persona—none0/10

   Evidence 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.

   ⚑ flag

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

   weight 2 · round drawn
   Stripe Identity~partialprobed5/10

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

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

   proof ↗⚑ flag

   Persona~partialclaimed5/10

   Persona'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.”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Api quality

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

   Evidence 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…”

   proof ↗⚑ flag

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

   weight 1 · round to Persona
   Stripe Identity—none0/10

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

   ⚑ flag

   Persona✓fullclaimed8/10

   Persona 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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

   Evidence 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.

   ⚑ flag

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

   weight 3 · round to Persona
   Stripe Identity~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Persona~partialclaimed6/10

   Persona'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.”

   proof ↗⚑ flag

Deepfake defense

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

   None 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.

   ⚑ flag

Duplicate detection

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   proof ↗⚑ flag

Liveness

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   ⚑ flag

Db checks

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   proof ↗⚑ flag

Kyb

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

   ⚑ flag

   Persona—none0/10

   Evidence 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.

   ⚑ flag

Risk signals

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

   ⚑ flag

   Persona—none0/10

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

   proof ↗⚑ flag

Doc types

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   proof ↗⚑ flag

Extraction

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

   Persona 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.

   ⚑ flag

Agent decisions

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

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

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

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

   proof ↗⚑ flag

   Persona~partialclaimed6/10

   Persona'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.”

   proof ↗⚑ flag

Agent operations

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

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

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

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

   proof ↗⚑ flag

   Persona—none0/10

   Evidence 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.

   ⚑ flag

Sandbox

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

   weight 3 · round to Persona
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona~partialclaimed6/10

   Persona 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…”

   proof ↗⚑ flag

Session api

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

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

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

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

   proof ↗⚑ flag

   Persona~partialclaimed4/10

   Docs 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.”

   proof ↗⚑ flag

Webhooks

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

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

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

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

   proof ↗⚑ flag

   Persona~partialclaimed5/10

   Docs 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.”

   proof ↗⚑ flag

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

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

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

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

   proof ↗⚑ flag

   Persona~partialclaimed5/10

   Persona 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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

   ⚑ flag

   Persona—none0/10

   No 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.

   ⚑ flag

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

   weight 3 · round drawn
   Stripe Identity—none0/10

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

   ⚑ flag

   Persona—none0/10

   No 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.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   ⚑ flag

Consent

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

   ⚑ flag

   Persona—none0/10

   None 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.

   ⚑ flag

Redaction

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   ⚑ flag

Hosted flows

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

   weight 3 · round drawn
   Stripe Identity✓fullcommunity7/10

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

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

   proof ↗⚑ flag

   Persona✓fullclaimed7/10

   Persona'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…”

   proof ↗⚑ flag

Native sdks

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

   Evidence 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.

   ⚑ flag

No code

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

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

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

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

   proof ↗⚑ flag

   Persona~partialclaimed6/10

   Docs 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.”

   proof ↗⚑ flag

Reuse

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

   weight 2 · round to Persona
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona~partialclaimed5/10

   Persona 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 …”

   proof ↗⚑ flag

Analytics

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

   Evidence 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.

   ⚑ flag

Review

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

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

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

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

   proof ↗⚑ flag

   Persona~partialclaimed4/10

   Persona 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.”

   proof ↗⚑ flag

Workflows

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

   weight 3 · round to Persona
   Stripe Identity~partialcommunity3/10

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

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

   proof ↗⚑ flag

   Persona~partialclaimed6/10

   Persona'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…”

   proof ↗⚑ flag

Monitoring

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

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

   proof ↗⚑ flag

   Persona—none0/10

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

   ⚑ flag

Screening

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

   weight 2 · round drawn
   Stripe Identity—none0/10

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

   ⚑ flag

   Persona—none0/10

   The 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 …”

   proof ↗⚑ flag