Question 1

Which IDs and credentials does Stile accept?

Accepted Answer

Government-issued documents from 200+ jurisdictions — passports, driver's licenses, national IDs, residence permits — and ISO/IEC 18013-5 mobile driver's licenses from Apple Wallet and Google Wallet for the US states that issue them. The flow auto-routes to whichever credential the user presents; the merchant configures which credential types are acceptable for their ruleset.

Question 2

What does the eligibility signal contain?

Accepted Answer

A signed webhook with the eligibility decision, the matched age tier (18+, 21+, 25+, or a custom threshold), the jurisdiction Stile resolved against, a session ID, and an audit pointer. The merchant does not receive the document image, biometric template, or date of birth in the default configuration. Configurable retention windows are available for chargeback or fraud-investigation lookback.

Question 3

How is mDL handled differently from a document scan?

Accepted Answer

mDL flows present an in-wallet prompt — the user authenticates with the wallet, the wallet releases only the requested attribute (age tier), and the wallet's signed assertion is verified server-side per ISO/IEC 18013-5. There is no document image transmitted. The signed-webhook shape returned to the merchant is identical to the document path, so a single integration covers both.

Question 4

Where does verification run — client-side or server-side?

Accepted Answer

Capture happens in the user's browser or app via the Stile SDK; the OCR, barcode cross-reference, liveness scoring, face match, and mDL signature verification all run server-side. The client never holds the verification result; the merchant receives it via the signed webhook bound to the session.

Question 5

Does Stile certify the liveness model against PAD standards?

Accepted Answer

Stile uses passive liveness with continuous model retraining against new spoof types. We do not currently claim ISO/IEC 30107-3 PAD certification — that statement requires an independent lab evaluation we have not yet completed. If a presentation-attack-detection certificate is required for your compliance regime, raise it before contracting and we will scope the lab evaluation.

Age verification API

Verify age across documents, biometrics, and digital wallets

Document scan

Liveness + face match

mDL + digital wallets

Three steps from session start to compliant signal

Age verification, the parts buyers ask about

Talk to compliance

Bring age verification to your stack