Load-board operator verification
Document capture, liveness, face match, and mDL. Signed webhook returns a verified identity assertion.
Capabilities
Identity verification for the principals on each side of a load-board match
Principal identity at signup
Government-issued ID captured in-session for the motor-carrier principal or broker authority signatory at the moment they sign up to the load board. OCR plus barcode cross-reference returns the credential's issuing state and a signed identity assertion the operator's onboarding system uses as a primary key.
Liveness + face match against the document portrait
The portrait on the captured ID is matched against an in-session selfie under passive liveness scoring. Defeats the most common identity-laundering pattern in logistics: someone else's credentials uploaded at signup by a different person, then used under a different identity inside the platform. Sub-second result, no UX detour.
Re-verification on identity-of-record changes
When the federal filing's principal-of-record changes (a new authority owner, a new MC# transfer), the load board can trigger a fresh Stile session against the new claimed identity. The audit pointer ↔ verification-result mapping lets the platform link the new session to the prior one for continuity.
How a principal verification flows on a load board
Configurable per platform. The default is at signup; some operators trigger verification at later onboarding milestones their compliance team selects.
- Step 01
1. Trigger
Platform invokes Stile when the motor-carrier principal or broker authority signatory completes the onboarding form. Trigger can also fire at later onboarding milestones the operator's compliance team selects.
- Step 02
2. Capture
Government ID (driver's license, 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 resolves the credential's issuing state and document number; 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 full identity assertion (legal name, DOB hash, document-number hash, jurisdiction) is reachable via the verification-result API for the operator's onboarding system to consume.
Onboarding scenarios + Stile coverage
The verification scenarios load-board operators most commonly trigger Stile against. Each scenario can be configured independently — different ruleset, different threshold, different release attribute set.
| Onboarding scenario | What Stile verifies | What's released to the operator |
|---|---|---|
| Motor-carrier principal at signup | Government ID + liveness + face match | Verified identity assertion + jurisdiction + audit pointer |
| Broker authority signatory at signup | Government ID + liveness + face match | Verified identity assertion + jurisdiction + audit pointer |
| Driver registration on the platform | Government ID (often CDL) + liveness + face match | Verified identity + age-tier eligibility + jurisdiction + audit pointer |
| Authority-of-record change on the federal filing | Fresh session against the newly claimed principal | New audit pointer linked to the prior verification-result for continuity |
| Re-signup after account suspension | Fresh session against the claimed identity | Audit pointer the operator's onboarding system can compare against its suspension records |
| Periodic re-verification (per operator policy) | Fresh session at the configured cadence | Updated assertion + audit pointer chained to the prior session for the same vendor |
Load-board operators sit at the boundary between motor carriers and brokers. The identity-verification step at signup is the platform's first defence against identity-laundering and ghost-account creation. Stile contributes the verification primitive; downstream decisions about what an onboarded user can do on the platform stay with the operator's onboarding system. Related coverage:
Identity verification — the underlying identity-attribute case for vendor onboarding.
Age verification — the age-tier flow for driver registration on platforms with commercial-driving age minimums.
Digital ID verification — mDL deep dive. Most US-issued CDLs are not yet available as mDL credentials; mDL acceptance for logistics onboarding is per-platform-policy.
Logistics — sibling verticals (broker onboarding, vendor identity for carrier platforms).
FAQ
Load-board operator verification — buyer questions
Operator-side. Stile produces the identity assertion (the human is who they claim to be); the FMCSA data — MC#, DOT#, authority status, insurance filings — is a separate dataset the operator's onboarding system consumes from the federal SAFER / L&I sources directly. Stile does not pull, sync, or distribute FMCSA records. The two are joined platform-side via the verification-result audit pointer keyed against the operator's vendor record.
Get started