Carrier and driver identity verification
Document capture, liveness, face match, and mDL. Signed webhook returns a verified identity assertion.
Capabilities
Identity verification at the carrier and driver onboarding boundary
Carrier principal identity at vendor signup
Government-issued ID captured in-session for the motor-carrier principal at the moment they vendor-onboard onto the platform. Selfie capture for liveness + face match against the document portrait. The signed identity assertion is the platform's primary key for the carrier record.
Driver identity at trip assignment
When a driver is assigned to a trip, the platform can require a fresh Stile session against the driver's CDL or other government ID. Liveness + face match against the document portrait defeats the most common driver-substitution pattern: one driver onboarded onto the platform, a different driver actually driving the load — caught at the assignment moment when the verification trigger fires.
Cross-platform continuity via audit pointers
Each verification produces a per-identity audit pointer. When a carrier or driver re-onboards (after suspension, after authority change, after a name change of record), the platform's onboarding system sees the prior pointer alongside the fresh-session result and can make the continuity decision the platform's compliance configuration calls for.
How a vendor-onboarding verification flows
Configurable per platform. Carrier principals are verified at signup; drivers can be verified at signup, at first trip, or per-trip depending on platform policy.
- Step 01
1. Trigger
Platform invokes Stile when the carrier principal or driver completes the onboarding form, accepts a trip, or hits a configured re-verification milestone.
- Step 02
2. Capture
Government ID (driver's license, CDL, state ID, or US-issued mDL) captured in-session. Selfie capture in the same session for liveness + face match. The user explicitly approves attribute release before any data leaves their device.
- Step 03
3. Verify
OCR + barcode cross-reference for physical credentials; ISO/IEC 18013-5 signature verification for mDL. Liveness scoring + face match against the document portrait. Spoof signals weighed into the eligibility decision.
- Step 04
4. Signed assertion
Signed webhook fires with the eligibility decision, jurisdiction, and audit pointer. The platform's compliance system reads the full identity assertion from the verification-result API and persists the audit pointer as the carrier or driver record's identity primary key.
Vendor onboarding scenarios + Stile coverage
The verification scenarios platforms most commonly trigger Stile against. Each scenario is configurable; the rule of thumb is that the higher the financial or safety exposure, the more frequent the re-verification cadence.
| Scenario | What Stile verifies | What's released to the platform |
|---|---|---|
| Carrier principal at vendor signup | Government ID + liveness + face match | Verified identity assertion + jurisdiction + audit pointer |
| Driver at vendor signup | Government ID (often CDL) + liveness + face match | Verified identity + age-tier eligibility + jurisdiction + audit pointer |
| Driver at first-trip assignment | Fresh session against the claimed identity | Trip-level audit pointer linked to the driver record |
| Driver at per-trip assignment (high-risk routes) | Fresh session at platform-policy threshold | Trip-specific audit pointer for the platform's safety log |
| Re-verification after suspension lift | Fresh session against the claimed identity | Audit pointer linked to the suspension record + the new active-vendor record |
| Authority-of-record change for the carrier | Fresh session against the newly claimed principal | Audit pointer chained to the prior verification-result for continuity |
Carrier and driver onboarding is where most logistics platforms first encounter the identity-verification problem. The platform's onboarding system consumes Stile's signed assertion as part of its onboarding decision; the platform's separate sources — federal authority data, insurance status, safety scores — combine with the identity primitive to produce the full vendor record. Stile sits strictly on the identity side of that boundary. Related coverage:
Identity verification — the underlying identity-attribute case for vendor onboarding.
Age verification — the age-tier flow for driver registration. Commercial driving age minimums vary; configurable per platform.
Digital ID verification — mDL deep dive. Most US-issued CDLs are not yet mDL-available; physical-credential capture remains the platform default for driver onboarding.
Logistics — sibling verticals (load-board operator verification, freight broker identity).
FAQ
Carrier and driver identity verification — buyer questions
Same primitive (identity-of-record verification), different buyer. The load-board page describes the matching-platform context where carriers and brokers meet. This page covers any platform that vendor-onboards carriers or drivers as part of its onboarding flow. The capability is the same; the trigger surface and the audit-shape configuration differ.
Get started