Identity verification, built for the rules buyers actually have to follow

What Stile is

Stile is a verification API. The merchant integrates one SDK, configures the rule that applies to their industry and jurisdiction, and Stile returns a signed webhook with the eligibility decision — pass or fail, age tier, jurisdiction resolved, audit pointer. The product covers document verification across 200+ jurisdictions, passive liveness, face match, and mobile driver's license verification per ISO/IEC 18013-5 from Apple Wallet and Google Wallet.

The capability surface is documented in detail at age verification, identity verification, mobile driver's license verification, and liveness detection.

Why we exist

Identity-verification platforms are mostly horizontal — a workflow builder, a primitives library, a pile of APIs the merchant assembles into something compliant. That works when the buyer is an engineering team designing a custom flow. It does not work as well when the buyer is a compliance owner who needs to enforce a specific rule (Texas HB 1181, Louisiana HB 142, gambling-commission KYC, cannabis age tier) and wants the eligibility decision to come back already mapped to that rule.

Stile takes the opposite shape. The product is vertical: pre-configured flows for regulated commerce industries, with jurisdictional rule lookup wired into the verification path. The merchant tells Stile the industry and the jurisdiction, not the building blocks. The result is shipped to compliance owners and procurement teams in the language they already speak — statute citations, retention semantics, audit trails — instead of in the language of an IDV platform.

Who Stile is for

Stile fits best when the verification has to satisfy a specific regulator: a state legislature, a gambling commission, an alcohol-commerce statute, a cannabis age tier, an adult-content age-gate. The regulated commerce family hub covers gambling, alcohol DTC, adult content, and cannabis; logistics covers driver and operator verification for load boards, freight brokers, and motor carriers; automotive covers buyer/seller identity for marketplaces and dealer onboarding.

The US state compliance hub tracks the live map of state-specific pages — Louisiana, California, and Texas in Wave 1, with more states added as enforcement expands.

What stays out of scope by design

Stile is not a workflow builder. The merchant doesn't compose verification primitives — they pick the industry and the jurisdiction, and Stile resolves the rule. Stile is also not a horizontal KYC platform; we don't ship every identity-related capability under one SKU. When a buyer needs a building-block IDV platform or horizontal age estimation across countries, the comparisons hub walks through head-to-head feature matrices versus other identity-verification providers — read it before talking to us.

Where we are today

Stile ships production verification flows today. Type II SOC 2 reporting is not certified and is not claimed; Stile does not publish a public roadmap of forthcoming certifications or capabilities. If a specific certification, jurisdiction, or industry rule matters to your evaluation, raise it before contracting and we will tell you whether it's covered today, in scope, or out of scope.

If the verification you need to ship has to answer to a specific rule — a state law, a commission, a regulator — start there. We will tell you the configuration that maps to it, what's covered today, and what would have to change.