By IDScan.net

IDScan.net DIVE API

Remote document, face-match and liveness evidence with optional checks and a central review portal.

The offering

What IDScan.net DIVE API does

DIVE uses a customer’s camera to collect front/back identity-document images, extract data and compare visible-zone information with barcode content where applicable. The current product describes document-tamper checks, a selfie/video liveness process and face comparison to the ID portrait. Optional external datasets can supply additional risk evidence, and the central portal supports history and manual review.

Specify the exact document authentication rather than assuming that every parsable template supports the same checks. Confirm regional access to DMV, SSA, sanctions and other optional sources. Integrate capture and results into the operator’s workflow, including consent, retries, repeated-document review and evidence retention. Casino-floor scanning, visitor management and exclusion-list administration are adjacent products or workflows, not automatic results of this remote check.

Who should explore it?

Operator teams connecting remote document and biometric evidence to controlled identity review.

  • Request a remote document/selfie identity check
  • Review conflicting document or optional database evidence

Documented capabilities

  • Front/back image capture
  • OCR/barcode crossmatch
  • Tamper-check evidence
  • Selfie/video liveness and face match
  • Optional external checks and portal review

Reported in the linked public sources. We have not independently tested these capabilities.

Product details

Remote identity job
Document and biometric evidence for configured remote verification.Source
Evidence inputs
Front/back document images, OCR/barcode comparison, tamper checks, selfie and randomized video liveness.Source
Review access
Cloud portal history, parsed data, optional check results and manual review.Source
Check geography
Document parsing/authentication scope differs; optional third-party checks are source-specific and described for North American customers.Source
Optional evidence
DMV/SSA/OFAC/private-list checks are optional, and operator admission/withdrawal decisions remain separately implemented.Source

Delivery & commercial details

Delivery & integration
Embed the selected remote capture/API flow or use supported portal requests. Configure optional sources, result mapping, privacy handling and manual review.
Pricing
Request verification-volume, capture/API, optional dataset, portal/review and support terms; the reviewed DIVE page requests a quote rather than publishing a full tariff.

Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.

Buyer questions, answered

Are document parsing and authentication identical coverage?

No. The page describes a broad parsing library while separately discussing expanding authentication coverage. Validate the exact documents and checks the operator needs.

Source
Can we add third-party checks to every verification?

Optional sources can be layered onto the result, subject to their actual region and access conditions. Specify the included data services instead of assuming global availability.

Source