OEM and embedded

The Acupixel document engine, inside your device.

Keep control of your reader and customer experience while Acupixel handles OCR, MRZ, VIZ and barcode extraction inside the device.

Representative forensic analysis and API orchestration interfaces showing document checks and sample code.
Talk to us about integrating

OEM embedded engine at a glance

Review the input, output and delivery options for this Acupixel module.

OEM embedded engine at a glance 01A document imageinside a third party's…02OCR, MRZ, VIZ andbarcode data.03Local SDK
InputA document image inside a third party's own reader.
OutputOCR, MRZ, VIZ and barcode data.
DeliveryLocal SDK
SKUAPX-OEM-EMBED

Why teams use OEM embedded engine

A focused capability that can stand alone or become one step in a broader Acupixel verification workflow.

Why teams use OEM embedded engine ACUPIXELAPIKeep your own deviceexperienceEmbed the document engineReturn structureddocument data

  • Keep your own device experience

    Retain control of the reader, industrial design and customer-facing workflow.

  • Embed the document engine

    Run Acupixel extraction inside the reader rather than sending users into a separate application.

  • Return structured document data

    Provide OCR, MRZ, VIZ and barcode output to the software or service connected to your device.

From request to usable result

The module fits into the product experience your customer already uses.

From request to usable result 01Provide the input02Run the module03Use the result

  1. Provide the input

    A document image inside a third party's own reader.

  2. Run the module

    Use the local SDK inside your application or device where the capture workflow already runs.

  3. Use the result

    OCR, MRZ, VIZ and barcode data.

Related products

Combine focused Acupixel modules to build the verification workflow your product needs.

Related products ACUPIXELAPIOCR data capture