stile

Verification layer to prevent logistics fraud.

Identity verification for high-risk logistics workflows: carrier onboarding, broker handoff, dock pickup. Signed yes/no in ~30 seconds.

  • Document Capture
  • Liveness
  • Face Match
  • mDL
  • Age Tier
  • Signed Webhook
// POST /v1/verification_sessions
{
  "type": "identity",
  "workflow_id": "wf_01HQ9Z2N7K8VRPB",
  "return_url": "https://acme-logistics.com/verified"
}

// Webhook  verification_session.verified
{
  "type": "verification_session.verified",
  "data": {
    "object": {
      "id": "vks_4p9x2m",
      "object": "verification_session",
      "status": "verified",
      "type": "identity",
      "current_method": "document_capture",
      "verification_result": {
        "method": "document_capture",
        "confidence": 0.97,
        "face_match_passed": true,
        "liveness_passed": true
      }
    }
  }
}

The gap

The loss is visible. The identity behind is not.

  1. Dollars lost

    Incident reports and write-offs name the symptom. The identity-of-record behind the carrier stays unverified.

  2. Carrier names on paper

    MC numbers and DOT filings name an entity. They don't bind the human signing the contract or pulling the load.

  3. Patterns after the freight is gone

    Fraud post-mortems surface the pattern after the load has moved. Identity needs to be answered at the boundary, not afterwards.

The product

Built for how fraud works now.

Two shifts at once: synthetic IDs and deepfake selfies are cheap, and mobile driver's licenses are signed and TSA-accepted. The product is built for both.

  • Accepts the new standard

    Native support for mobile driver's licenses — verified by cryptographic signature, not a photo. ISO/IEC 18013-5.

  • AI vs AI

    Models trained to detect deepfake selfies, injection attacks, and synthetic IDs that fool a human or a static checker.

  • Proof, not paperwork

    Every check returns a signed, tamper-proof record. Audit-ready by default — no screenshots, no manual logs.

Driver tap-to-verified in ~30 seconds.

Only the signed yes/no enters your system. No raw PII. No retained images.

  1. Step 01

    Trigger

    A system or mobile device calls the API or surfaces a QR. Stile returns a verification-session URL.

  2. Step 02

    Verify

    Driver opens the link, captures a mobile driver's license (Apple/Google Wallet) or a photo of a government ID, plus a liveness selfie.

  3. Step 03

    Sign

    Stile cryptographically signs the result. No raw PII crosses your wire.

  4. Step 04

    Webhook

    A signed assertion is delivered to your callback URL. Sandbox-replayable and auditable.

  5. Step 05

    Decide

    Your onboarding, dispatch, or gate system gates on the boolean. ~30 seconds end-to-end.

Why Stile

Easy. Cheap. No PII. Effective.

  1. Easy

    Integrates quietly into existing workflows using QR codes, kiosk tablets, or driver phones.

  2. Low cost

    $0.25 per verification at enterprise scale. A fraction of legacy ID-verification costs.

  3. No PII

    No data monetization schemes. A signed yes/no is returned. No images stored, no profiles built, no data resold.

  4. Effective

    Designed to detect liveness attacks, synthetic IDs, and impersonation. Re-trained against emerging tactics to stay ahead of what's next.

Where it fits

Three identity moments. Three points of leverage.

Each row maps to a deeper page below. Carrier onboarding, broker handoff, and pickup at the dock — same primitive, three workflows.

Three identity moments. Three points of leverage.
Identity momentWhat Stile verifiesOutcome
01 Carrier onboardingGovernment ID, liveness, and face match of the principal signing the contracts.Chameleon and shell-carrier admissions filtered before authority issues.
02 Broker / shipper handoffCarrier principal and assigned driver re-verified before sensitive load details are released.Impersonator carriers caught at booking, before a load is ever assigned.
03 Pickup at the dockDriver via QR code or guard-station tablet. Cryptographically matched to driver on the record.Forged IDs and fictitious pickups stopped at the gate, before the load moves.

Proof

Proof for every check, replayable in sandbox.

HMAC-SHA256-signed webhooks plus a verifiable audit chain. Counsel can see what was decided, when, which evidence was checked, and which credential was presented — without you keeping a single screenshot.

Stile audit-log dashboard — signed verification events listed with method, confidence, and replay link.

Replay in sandbox

Counsel and platform engineers open any verification event from the dashboard, walk the signed assertion, and replay the session against a sandbox endpoint. No PII retention; the audit pointer is the receipt.

FAQ

Logistics buyers ask

No. Stile returns a signed yes/no plus the audit pointer. Document images, biometric templates, and PII never leave Stile's verification pipeline.

Get started

Verify the person behind the carrier

Tell us how your platform onboards carriers, brokers, or drivers. Stile maps the workflow to a signed identity check your team can integrate and your compliance leads can review.

Book demoRead the docs
Stile verification session flow — iframe to webhook handoff.