ID Verify

Real-time driver's license and identity verification. Sub-three-second flow. Built into Connect and Lite. Available as a standalone feature in the dealer workflow.

What it is.

ID Verify is the real-time identity feature in the SecureMyDealer family. The customer captures their government-issued ID, typically a driver's license, from the same secure session they were already using to upload other documents. ID Verify checks the information against the issuing agency in real time, not a stale database, and the verified result lands in the Customer Relationship Management (CRM) or Dealer Management System (DMS) alongside the document image.

ID Verify runs inside Connect and Lite by default. It also stands on its own as a feature the dealership can use whenever an identity check is part of the workflow, whether that is a test-drive intake, a credit application, or a Finance and Insurance (F&I) document package.

The point is to eliminate the gap between "we have an image of a driver's license" and "we know the driver's license is valid." Before ID Verify, that gap was a human in the F&I office squinting at a screenshot. Now it is a real-time check at the point of capture.

Why this was hard to do before SDT.

Identity verification at a dealership has always been a three-step problem. First, the customer has to send their ID through a channel that is encrypted in transit (the Federal Trade Commission (FTC) Safeguards Rule requirement). Second, the dealership has to verify the ID is legitimate against an authoritative source. Third, the verified record has to land in the CRM or DMS so the F&I office can use it.

The traditional stitch-together used three vendors and a manual hand-off in the middle. The customer sent a photo. Someone in F&I uploaded it to a verification tool. Someone else re-entered the verified data into the CRM. Each step was friction. Each step was a place the deal could slow down or fall apart.

The SDT Engine made it possible to compress all three steps into one flow. The customer's ID capture, the issuing-agency verification, and the CRM or DMS write-back happen inside the same secure session, with the same audit trail. The F&I office stops doing data entry. The deal moves at the pace the customer expects.

What the SDT Engine made possible.

  • Real-time issuing-agency verification: Driver's license and government ID information verified instantly against the issuing agency, not a third-party database that may be days or weeks out of date.
  • Government ID image capture: The customer captures their driver's license or other government-issued ID directly from their phone, through the same secure session they were already using to send other documents.
  • Encrypted in-transit by default: Every ID image and every verification result rides through the patented SDT Engine. No unencrypted hop. No "we used a verification vendor but the image got emailed first."
  • CRM and DMS write-back: The verified ID record lands in the dealership's CRM or DMS automatically. The F&I office stops re-entering data from a screenshot.
  • Audit trail on every check: Every verification is logged with the timestamp, the source, and the outcome. The dealership can produce the compliance record without digging through three vendors' dashboards.
  • Standalone or embedded: Use ID Verify inside the Connect and Lite workflows, or fire it standalone whenever an identity check is the only thing you need.

Inside the verification engine: image capture and document classification.

ID Verify runs on a fully automated proprietary AI engine that performs a series of real-time authenticity and validity checks on every government-issued photo ID. Most customers complete the entire verification flow in under three seconds, from scan to verified result. The on-screen camera coaches the customer in real time to avoid glare, blur, and poor lighting, which is what drives the 94 percent first-attempt success rate.

The first five checks focus on image quality and document classification.

  • Image quality checks. Blur, glare, lighting, and resolution evaluated before the engine accepts the image. The customer is coached to retake if quality fails.
  • Auto-detect and auto-classify. The engine identifies the document type (driver's license, passport, state ID) and the issuing jurisdiction automatically.
  • Screen detection. Flags IDs captured from a phone screen, laptop, or monitor. A common synthetic-fraud vector caught at the first frame.
  • Photocopy detection. Evaluates whether the document is a color or black-and-white photocopy and flags or rejects per dealer policy.
  • Barcode anomaly checks. Full AAMVA barcode analysis catches tampering, fabrication, and inconsistencies a human eye cannot see.

Inside the verification engine: data verification and fraud screening.

The next five checks focus on the document data itself, cross-matching, fraud screening, and configurable risk thresholds.

  • Visual checks. Face photo tampering analysis and static design elements (state seals, micro-print, holograms) compared against the known reference for that document type.
  • Data cross-match. Front-of-document information compared against the machine-readable zone and the barcode data. Any inconsistency is flagged.
  • Data logic and format. Field structure, dependency, and formatting validated against document-specific knowledge.
  • Suspicious data screening. Names, dates, and document numbers checked against fraud-attempt patterns. Continuously updated fraud database.
  • Configurable risk thresholds. Fine-tune sensitivity to balance False Rejection Rate and False Acceptance Rate. High-volume retail flow tunes one way, high-value F&I flow the other.

By the time the customer hands the dealership a verified ID, the engine has already done the work of three vendors and the F&I office manual review combined. The verified result lands in the CRM with the audit log attached.

Compliance posture.

The FTC Safeguards Rule (16 CFR Part 314) puts the dealership on the hook for in-transit encryption of customer financial data, and driver's license images sit squarely inside that requirement alongside credit applications and bank account numbers. The 2023 amendments and the 30-day breach-notification rule that followed have escalated examiner attention to exactly this category of dealership workflow. ID Verify is built so the encryption and the verification happen inside the same SDT Engine flow, with the same audit trail, rather than across two or three separate vendors that each add an unaudited gap.

The transport is the compliance. Every ID image is encrypted in motion through the SDT Engine. Every verification check is logged. No customer credentials in the dealership environment. The compliance review during the next examination is faster because the chain of custody is one system, not three.

Part of the SecureMyDealer family.

ID Verify is one of three production products under the SecureMyDealer umbrella, all built on the same SDT Engine and tuned to different dealership sizes and integration appetites. Connect is the full CRM and DMS-integrated workflow embedded inside CDK Global, Cox Automotive, and Drive Centric. Lite is the on-demand secure messaging layer for smaller dealers and franchise groups. ID Verify ships inside both Connect and Lite and is also available as a standalone capability for dealerships that have other secure transport in place but need just the identity-verification step. The same engine powers all three variants, which lets a dealership group mix variants across rooftops without standing up parallel infrastructure.