Persona

Configurable identity platform

Persona is a modular identity platform. Inquiries and Dynamic Flow collect information; Verifications and Reports add evidence; Workflows apply policy; Cases support review; Graph links related identities. Its KYB approach combines company checks with KYC of owners and controllers.

Our assessment

Highly configurable identity operations; add transaction monitoring and merchant underwriting where required.

Best fit and limitations

A strong candidate when onboarding needs a flexible user experience and business/owner workflow. It is especially relevant when exception handling and ongoing identity review matter as much as first-pass conversion.

A configurable KYB workflow is not a full merchant credit or reserve decision model.
Watchlist reports depend on the purchased data products and providers.
No reviewed source establishes a full AML behavior-monitoring and regulatory filing replacement.

Tools 7

Inquiries + Dynamic FlowInformation collection

Configurable user-facing verification flows
Branch checks based on identity and risk context

Source 1

Verifications + ReportsEvidence collection

Person and business verification components
Supplement checks with registry and watchlist reports

Source 2

KYB workflowsBusiness and owner checks

Verify a business and run UBO/controller KYC
Consolidate evidence for automated or manual decisions

Source 2

Workflows + CasesPolicy and review

Configure follow-up actions and review processes
Present business and owner risk in a case

Source 3

GraphConnected investigation

Explore related identities and coordinated fraud
Use relationship evidence during review

Source 3

Policy Agents + Persona AssistantPolicy implementation

Extract requirements and map them to configuration
Propose changes with source links and required human approval

Source 5

Case Review Agents (early access)Configured review pilot

Define agent scope against the customer's review procedures
Backtest and refine a case-review agent in a three-month proof of concept

Source 6

AI capabilities

Identity models + policy assistance

Policy Agents extracts requirements, flags conflicts, and maps them to Persona workflows and templates. Persona Assistant can propose and apply configuration changes after human approval. This is a specific policy task, distinct from automatic case clearance.

Map policy requirementsFind configuration gapsPropose approved configuration changes

What to validate

The published workflow requires human approval before changes. Test conflicting documents, source links, access permissions, and the resulting audit record.

Source 5

Implementation

Integration checklist

Design the company, applicant, owner, inquiry, and case relationship before launch.
Test embedded or hosted capture, webhooks, review queues, and resume flows.
Define retention and redaction rules for identity documents and exported evidence.

Commercial scope

Quote required. Separate verifications, reports, business checks, workflows, cases, graph use, and AI functions.

Questions for the demo

Which KYB records and ownership fields are available in each target country?
Can ownership changes trigger only the necessary re-verification?
How do Graph flags affect policy and manual review without blocking unrelated users?

Engineering

Webhook quickstartChecked 2026-09-18 Inquiry request tutorialChecked 2026-09-18 POST idempotency contractChecked 2026-09-18 Case-review pilot prerequisitesChecked 2026-09-18

Your systemInputs & context

PersonaChecks & signals

Your controlsDecision & review

Illustrative integration boundary. Confirm the actual interfaces and decision authority.

Inputs: Inquiry template identifier and optional name/birthdate fields · Review procedures and historical cases for agent configuration and backtesting
Outputs: Event notifications with timestamped Persona signatures · Inquiry identifier and lifecycle status
Webhooks: Verify persona-signature against the raw request body and timestamp. Persona documents a 5-second success window and up to seven additional attempts with exponential backoff.
Decision timing: No measured latency or contracted response time verified.
Deployment: Deployment options not verified.
Dependencies: Webhook secret and raw-body signature verification · Bearer API key, API version header, and configured inquiry template · Stable Idempotency-Key and unchanged parameters when retrying POST requests · Selective early-access enrollment and a three-month proof of concept · Program fit includes at least 100 historical cases, approximately 50 approved and 50 declined

Verified details 10

Outputs
Event notifications with timestamped Persona signatures
Source Checked 2026-09-18
Webhooks
Verify persona-signature against the raw request body and timestamp. Persona documents a 5-second success window and up to seven additional attempts with exponential backoff.
Source Checked 2026-09-18
Dependency
Webhook secret and raw-body signature verification
Source Checked 2026-09-18
Inputs
Inquiry template identifier and optional name/birthdate fields
Source Checked 2026-09-18
Outputs
Inquiry identifier and lifecycle status
Source Checked 2026-09-18
Dependency
Bearer API key, API version header, and configured inquiry template
Source Checked 2026-09-18
Dependency
Stable Idempotency-Key and unchanged parameters when retrying POST requests
Source Checked 2026-09-18
Inputs
Review procedures and historical cases for agent configuration and backtesting
Source Checked 2026-09-18
Dependency
Selective early-access enrollment and a three-month proof of concept
Source Checked 2026-09-18
Dependency
Program fit includes at least 100 historical cases, approximately 50 approved and 50 declined
Source Checked 2026-09-18

Vendor example

Published vendor example. Confirm the current version and required credentials.

json

{
  "data": {
    "attributes": {
      "inquiry-template-id": "itmpl_YOURTEMPLATEID",
      "fields": {
        "name-first": "Jane",
        "name-last": "Doe",
        "birthdate": "1994-04-12"
      }
    }
  }
}

Example source

Integration limits

Published vendor payload example, linked to its source. It is not a complete integration or a tested production request.
Empty country, deployment, or provider lists mean not verified in this review. A documented country refers to the specific product noted in its source, not universal platform coverage.
Callback acknowledgment timing is not an identity decision latency guarantee. Preserve the raw body for verification before parsing or transforming it.
The vendor example is the published inquiry JSON request body. Replace its template placeholder and use the documented endpoint, authentication, and version header; it was not executed.
A repeated key replays the initial status and body, including an initial 500. Keys can be pruned after at least 24 hours; reuse after pruning creates a new request. This cited guide is versioned 2023-01-05.
A successful pilot is evaluated against agreed metrics. Enrollment and future GA are not automatic.

Sources 6

Identity platform and moduleswithpersona.com2026-09-18 · Reviewed

Product

KYB example and component roleshelp.withpersona.com2026-09-18 · Reviewed

Documentation

Platform workflows, cases, graph, and agentshelp.withpersona.com2026-09-18 · Reviewed

Documentation

Business verification scopehelp.withpersona.com2026-09-18 · Reviewed

Documentation

Policy Agents and required human approvalhelp.withpersona.com2026-09-18 · Reviewed

Documentation

Case Review Agents early-access programhelp.withpersona.com2026-09-18 · Reviewed

Documentation

Source review dates are shown above. Product claims come from public sources. Fit, limits, and evaluation questions are our analysis. This is not a hands-on performance test. Methodology · Changelog