Persona: identity verification, screening and configurable review workflows

Persona provides identity infrastructure to financial institutions, fintechs and other businesses. Its financial-services offering covers initial KYC/KYB, further checks before high-risk activity or account recovery, and continued screening. For a broker, the practical role is collecting and evaluating identity evidence while connecting that evidence to its own customer-acceptance process.[1]

The KYB offering connects government and commercial registries in more than 150 countries according to Persona. It supplements registry records with business documents, website credibility, industry data and screening. This breadth is product coverage, not a statement that every country exposes identical ownership or registry information.[3]

Hosted Flow sends the person to a verification link without requiring an embedded application. Embedded Flow uses the web SDK inside the customer’s site; mobile SDKs place the experience in its app. The API can supplement these collection methods with backend records and workflow operations.[5][6]

The current developer default is API version 2026-09-29. Webhooks can use different dated versions, allowing an upgrade to be tested before changing a production listener.[7]

GET /api/v1/rate-limits returns the actual account context’s limits. Requests can count against both an API key’s limit and the environment’s limit; response headers report the constraint nearer exhaustion, or the one that rejected a 429 request. Creating extra keys therefore does not remove the shared environment limit.[9]

The July 2026 platform terms default to USD unless agreed otherwise in writing; taxes are extra. Invoice payment normally falls due 30 days from invoice, with disputes due within 20 days. Order Forms can set different payment terms. Overdue undisputed fees can incur 1.5% monthly, or the lower legal maximum, after ten business days without payment following written notice.[12]

The pricing FAQ describes successful-verification billing and no charge for abandonment caused by user error. It does not equate billable success with the broker’s approval decision. Resale requires a separate reseller plan.[11]

The Essential trial lasts 60 days with up to 50 services and no card required. Sandbox is the default; Production requires additional information and business review. A trial ending without subscription becomes inactive, retaining data access but preventing new changes.[10]

Terms ordinarily renew for 12 months unless an Order Form differs or either party gives 30 days’ written notice before term-end.[12]

Sandbox does not perform real identity verification or document extraction, and product runs do not transfer into Production. It is suited to checking collection screens and integration behaviour. Production performs real checks and counts usage. A successful Sandbox journey therefore establishes a working flow, not the outcome of an actual identity assessment.[13]

Roles distinguish organisation-wide administration from environment-level Product, Data and Development permissions. The option to include all current and new environments automatically extends a role to environments created later. Access to a test environment and access to production customer records should therefore be configured deliberately.[15]

Persona documents AES-256 encryption at rest and TLS 1.2 or later for web transport. Its API configuration can expose selected PII attributes; fields supplied directly by individuals are not exposed by default. This configuration is separate from whether an integration can retrieve the underlying verification object.[16]

The platform terms specify weekdays 09:00–18:00 Pacific Time, excluding US federal holidays, and commercially reasonable efforts to respond within one business day. Free access and beta releases have no support obligation.[12]

For an extraction error or suspected fraud in a production Inquiry, the Dashboard’s Report issue action supplies the relevant context. General integration issues use the support form. Customers with dedicated account management can use their assigned team. End users are directed to the business that configured their flow for decisions and process-specific assistance.[17]

The platform terms prohibit using Persona information for FCRA consumer-report eligibility decisions, including credit, insurance or employment.[12]

Policy Agents explicitly does not certify that a customer’s implementation meets its legal obligations. The business remains responsible for its risk tolerance, requirements and configuration. Identity verification and an automated workflow can support those decisions without transferring the underlying responsibility to Persona.[21]

The processor notice states that personal data, including biometrics, is not used for AI/model training. It primarily identifies US and German data centres while allowing processing elsewhere as described in the policy. Hosting location, subprocessors and a broker’s selected retention configuration remain distinct questions.[18]

Persona Identities, Inc. is the contracting operator.[12]

Persona dates its founding to 2018. Its 30 April 2025 announcement reported a $200 million Series D at a $2 billion valuation, led by Founders Fund and Ribbit Capital with existing investors also participating. That is a dated financing event; it does not make either lead investor the sole owner or establish a current market valuation.[20]

Operator

Persona Identities, Inc.

Service scope

Identity/KYB checks, screening, review and configurable decision workflows.

Customer types

Financial institutions; Fintechs; Other businesses

Delivery

SaaS; API; Hosted

Pricing publication

Public and quoted pricing

Platforms

Persona

Pricing scope

Essential has published usage pricing; Growth and Enterprise are customised.

Implementation

Hosted links, embedded web flow or mobile SDKs, with Sandbox and Production environments.

Support

Plan-dependent support and dedicated account routes; current platform terms define support hours and response efforts.

Permissions and regulatory scope

Verification and workflow technology; customer risk decisions and compliance obligations remain with the business.

Provider metadata checked 20 Oct 2026Source 1Source 18Source 6Source 5Source 10Source 17Source 21

Policy Agents turns policies and other requirements documents into a traceable configuration map. It can flag missing, ambiguous, conflicting or out-of-scope requirements. Persona Assistant can propose and apply resulting workflow, inquiry or case changes, but every proposed change requires human review and approval. The audit trail links the requirement, issue, approved change and resulting configuration.[21]

Data Explorer’s guides conflict: the overview calls access environment-agnostic; the permissions guide says queries use the selected environment with environment-specific grants. The deployed scope needs confirmation.[22][23]

Dashboards roll out separately from the query editor. Only a dashboard’s creator can change it; if that person leaves, it must be recreated rather than reassigned.[23]

Redacting an Account permanently removes its PII and associated inquiry, verification and report data. Child objects are processed asynchronously, so the successful Account response does not establish that all linked objects have finished redaction. The Account remains updatable afterward; continuous erasure needs a retention policy rather than a single delete request.[24]

The Help Centre describes exports through the Dashboard and API and irreversible PII redaction, while a non-PII inquiry record remains. The October 2026 data explanation further distinguishes device signals, which can persist beyond the configured retention window, from customer records and biometric templates. A record’s disappearance is therefore not a single platform-wide erasure clock.[16][25]

If Persona terminates for cause, remaining term payments become immediately due. On expiry or termination, service access ends and the customer must stop using and distributing Persona code and remove or return the specified materials and credentials. The reviewed public terms do not grant a standard post-termination export window.[12]