Freight broker identity verification
Document capture, liveness, face match, and mDL. Signed webhook returns a verified identity assertion.
Capabilities
Identity verification for the people behind the broker authority
Authority-signatory verification
The person signing the broker authority filing or operating under the bond is verified against a government-issued ID. The signed identity assertion includes the credential's issuing state, document-number hash, and DOB hash — the primary key the broker's compliance system uses to link the authority filing to the verified human.
Carrier principal verification at onboarding
Brokers can require a fresh Stile session against the carrier principal at any onboarding milestone their compliance team selects — vendor signup, periodic re-verification, or after an authority-of-record change on the federal filing. The same verification primitive — document capture, liveness, face match — applied at whichever point the broker's compliance program calls for.
Cross-session continuity
Each verification produces a per-identity audit pointer. When the same carrier principal returns for a re-verification, the prior pointer is returned alongside the fresh-session result so the broker's compliance system can link the new session to the original onboarding record under the broker's own re-verification cadence.
How a carrier-principal verification flows
Configurable per broker compliance program. The default trigger is at carrier signup; some brokers add re-verification at periodic intervals or after a federal-filing change.
- Step 01
1. Onboarding trigger
The broker's compliance system invokes Stile when the carrier principal reaches the verification step. The principal receives the verification link via the broker's existing communication channel (SMS, email, or in-product).
- Step 02
2. Capture + verify
Government ID captured in-session, selfie captured for liveness + face match. OCR + barcode cross-reference for physical credentials; ISO/IEC 18013-5 signature verification for mDL where the issuing state has shipped wallet credentials.
- Step 03
3. Signed assertion
Signed webhook fires with the eligibility decision, jurisdiction, and audit pointer. The verification-result API exposes the full identity assertion (legal name, DOB hash, document-number hash, jurisdiction) the broker's compliance system reads.
- Step 04
4. Onboarding decision
The broker's compliance team combines the Stile assertion with its own carrier-data sources (FMCSA registration, insurance status, safety scores) to make the onboarding decision. Stile does not make the onboarding decision — it provides the identity primitive the broker's compliance team consumes.
Verification scenarios brokers commonly use Stile for
When a broker most commonly invokes Stile, what gets verified, and what shape the audit takes. Each scenario is configured independently.
| Scenario | What Stile verifies | Audit-trail shape |
|---|---|---|
| Authority signatory at filing | Government ID + liveness + face match | Per-signatory identity primary key linked to the broker's authority record |
| Carrier principal at vendor onboarding | Government ID + liveness + face match | Per-carrier identity primary key linked to the broker's vendor record |
| Carrier principal at periodic re-verification | Fresh session against the prior identity | Audit pointer chained to the prior verification-result for continuity |
| Carrier principal after federal-filing changes | Fresh session against the newly claimed principal | New audit pointer linked to the prior onboarding record for the same carrier |
| Carrier re-verification after suspension lift | Fresh session against the claimed identity | Audit pointer linked to the suspension record + the new active-vendor record |
| Periodic re-verification (per broker policy) | Fresh session at the configured cadence | Updated assertion + chained audit pointer |
Freight brokers carry significant financial exposure when they take on motor carriers whose principal-of-record was never verified. The identity-verification step is the broker's first compliance layer; the corporate-authority and insurance-filing layers run separately on the broker's own data sources. Stile contributes the human-side identity primitive — who the principal actually is — and produces the audit pointer the broker's compliance system uses to join that identity to its corporate data. Related coverage:
Identity verification — the underlying identity-attribute case for principal verification.
Digital ID verification — mDL deep dive. Most US-issued CDLs are not yet mDL-available; physical-credential capture remains the broker default.
Logistics — sibling verticals (load-board operator verification, vendor identity for carrier-onboarding platforms).
FAQ
Freight broker verification — buyer questions
No. Stile produces the identity-of-record assertion for the carrier principal — that the human signing the federal filing or operating under the carrier's authority is who they claim to be. Carrier vetting (FMCSA registration data, insurance status, safety scores, loss-history filings) runs on separate data sources the broker's compliance team already consumes. Stile contributes the identity primitive; the broker's existing carrier-vetting work continues to run alongside it.
Get started