Fix PDF417_NOT_DECODED for Driver License Images

Diagnose PDF417_NOT_DECODED responses from US driver license backs. Improve framing, focus, glare control, resolution, and retake UX.

What the Failure Means

PDF417_NOT_DECODED means the service could not recover a reliable barcode payload from the submitted image. It is a capture failure, not an invitation to guess the identity fields.

A Reliable Recovery Path

Show a retake screen that keeps the entire barcode in frame, checks focus before upload, avoids glare, and submits the original image rather than a screenshot. Consult the PDF417 error reference for status codes and use the scanner with fictional or authorized samples while tuning capture guidance.

Where This Workflow Fits

  • Full barcode visible: Validate this condition before the image leaves the capture screen.
  • Sharp narrow bars: Include this check in support guidance and quality monitoring.
  • No glare across rows: Include this check in support guidance and quality monitoring.
Need more testing? Create a free account to get 200 free credits (equals 100 Driver License scans).

Handle the Result Explicitly

Treat capture errors as application states. Never substitute guessed identity values when the barcode cannot be validated.

Prerequisite: A server-side API integration and a capture UI that can request a new license-back image

PYTHON EXAMPLE
if response.status_code == 422:
    error = response.json().get("error")
    if error == "PDF417_NOT_DECODED":
        return {
            "action": "retake",
            "message": "Photograph the full back of the license in even light.",
        }

Technical Specs

  • •Endpoint: POST https://api.structocr.com/v1/driver-license-pdf417
  • •Success status: HTTP 200 after barcode and required AAMVA data are usable
  • •Unreadable barcode: HTTP 422 with PDF417_NOT_DECODED
  • •Invalid record: HTTP 422 with AAMVA_NOT_VALID
  • •Processing failures: Refunded according to the endpoint behavior
  • •Safety rule: Never infer missing barcode fields from an unsuccessful response

Key Features

  • •Full barcode visible: Make this condition visible in capture guidance, validation, or review tooling.
  • •Sharp narrow bars: Make this condition visible in capture guidance, validation, or review tooling.
  • •No glare across rows: Make this condition visible in capture guidance, validation, or review tooling.
  • •Original-resolution upload: Make this condition visible in capture guidance, validation, or review tooling.

Example Recoverable Error

This illustrative error contains no personal data. Use the error code, rather than free-form text, to select the next application action.

{
  "success": false,
  "error": "PDF417_NOT_DECODED",
  "message": "Upload a clear image of the complete back of the US driver license or State ID."
}

Frequently Asked Questions

Are failed PDF417 processing attempts charged?

The endpoint charges 2 credits for a successful decode; documented processing failures are refunded.

Can generative OCR fill fields when PDF417 decoding fails?

Do not present inferred values as barcode data. Ask for a retake or use the separate front-side OCR endpoint with a clearly identified source.

What should be logged?

Log request IDs, status, error code, timing, and capture-quality signals. Avoid logging raw images, Base64 payloads, or complete identity responses.

You May Also Like

Related tutorials, platform guides, and comparisons

Country Tutorial

South Dakota Driver License OCR: Extract Fields with Python

Extract visible fields from South Dakota driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.

Python · Driver License
Country Tutorial

Kenya Driver License OCR: Extract Fields with Python

Extract visible fields from Kenya driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.

Python · Driver License
Tutorial

Michigan Driver License PDF417 API

Decode the PDF417 barcode on the back of a Michigan driver license or State ID and return normalized AAMVA fields as structured JSON.

Driver License
Country Tutorial

Ohio Driver License OCR: Extract Fields with Python

Extract visible fields from Ohio driver license images into JSON. Map identifiers, names and dates, with a review workflow for incomplete results.

Python · Driver License
Tutorial

Go Driver License OCR API

Upload an image for a free test! Struggling with manual driver's license data entry? Our Go API delivers structured JSON in seconds, with SOC 2 Type II and AES-256 encryption.

Go · Driver License
Country Tutorial

Canada Driver License OCR with Node.js SDK

Extract structured fields from a Canada provincial driver licence with the StructOCR Node.js SDK and TypeScript + Express.

Node.js · Driver License
Tutorial

Flask PDF417 Driver License API

Build a compact Python service that decodes US driver license PDF417 barcodes and returns normalized AAMVA JSON with safe retake handling.

Driver License
Country Tutorial

Philippines Driver License OCR with Node.js SDK

Extract structured fields from a Philippines LTO driver's license with the StructOCR Node.js SDK and TypeScript + Express.

Node.js · Driver License
Country Tutorial

Canada Driver License OCR with Python SDK

Extract structured fields from a Canada provincial driver licence with the StructOCR Python SDK and FastAPI.

Python · Driver License
Country Tutorial

Philippines Driver License OCR with Python SDK

Extract structured fields from a Philippines LTO driver's license with the StructOCR Python SDK and FastAPI.

Python · Driver License

Technical Comparisons & Integrations

Explore platform integrations and competitive analysis

From tutorial to production in 5 minutes.

You've seen the code. Now get your API key, grab your 200 free credits, and see it work with your own images. No credit card required.

Instant Access Cancel Anytime No Credit Card