Stile vs Persona — Built for regulated commerce, not horizontal KYC
Persona is a workflow builder for KYC and identity. Stile ships pre-configured verification flows for regulated commerce with the eligibility decision already mapped to the rule. Different buyer, different shape of product.
The Stile advantage vs Persona
Three differences that show up in a regulated-commerce evaluation
Vertical product, not platform builder
Stile ships fully-configured flows for regulated commerce — the merchant picks the industry and the jurisdiction, not the building blocks. Persona is workflow-builder-first; the customer composes flows from primitives. Stile's buyer is a compliance owner; Persona's buyer is more often a product engineer.
Eligibility decision is the API output
Stile's signed webhook returns the eligibility decision — pass or fail, age tier, jurisdiction resolved, audit pointer — already mapped to the rule the merchant has to enforce. Persona returns raw verification output; the eligibility logic is your product code's job to write and maintain.
mDL as a first-class credential
Stile treats mobile driver's licenses per ISO/IEC 18013-5 as a peer of document scan — same SDK surface, same signed-webhook shape, same retention semantics. Persona's IDV product is document- and database-first; mDL coverage is limited and not the primary credential path.
Feature comparison
| Feature | Stile | Persona |
|---|---|---|
| Document verification (200+ jurisdictions) | ||
| Passive liveness detection | ||
| Workflow builder for custom flows | ||
| mDL verification per ISO/IEC 18013-5 (Apple Wallet, Google Wallet) | ||
| Webhook returns eligibility decision (not raw verification output) | ||
| Pre-configured flows for regulated commerce (gambling, alcohol DTC, adult content, cannabis) | ||
| US state-specific compliance pages with statute citations |
Where this matters in practice. The difference between Stile and Persona shows up most clearly in who owns the eligibility decision. Persona returns the verification primitives — document fields extracted, biometric match score, database hits — and the merchant's product code maps those to the rule (is this user 21+ in this state on this date?). Stile makes that decision server-side and returns it in the signed webhook. The merchant's product code sees a pass / fail / eligibility tier, not a pile of fields to interpret.
If the verification needs to be tied to a specific industry rule, follow the cluster: identity verification is the capability page; age verification is the variant for age-tier checks; regulated commerce is the family hub for the industries Stile is purpose-built for; US state coverage is the live map of state-specific pages.
Switching considerations
Switching considerations. Stile does not publish a step-by-step Persona migration guide because the products are shaped differently — Persona is a workflow builder, Stile is a pre-configured flow. The integration is rebuilt against Stile's session API, not migrated workflow-for-workflow.
What changes for an engineering team: the embed swaps from Persona's hosted-flow widget or Inquiry SDK to Stile's SDK; the webhook payload swaps from Persona's inquiry / verification objects to Stile's signed-webhook shape (one webhook covers document, mDL, liveness, and the eligibility decision). Session linkage moves to Stile's session ID. See the verification-sessions API reference.
What changes for a compliance team: the eligibility logic that lives in the merchant's product code today (mapping verification fields to the per-state rule) moves server-side at Stile. Audit-trail format changes shape — Stile's signed webhook is the audit pointer. Retention windows are configured at the session level, not the workflow level.
What stays the same: capture UX is broadly similar (camera + document framing in the user's browser or app), and the compliance evidence retained is configurable to match whatever retention contract the merchant has signed.
Talk to compliance
Switch from Persona to Stile
Tell us which industry you're verifying for, which jurisdictions matter, and how the eligibility decision is made today. We'll send back a configuration recommendation and a switching plan the same week.
Switching from Persona?
Email goes to alex@stile.id directly. Engineering and compliance are CC'd on the reply.
Email alex@stile.id