AAMVA barcode fields — a field-by-field walkthrough
Good timing, I've been reverse-engineering the PDF417 string format myself and the header/field order trips people up constantly. One thing to watch is checksum validation — get a single character off and scanners will either throw a data parsing error or, worse, compute the wrong DOB and report you scans as under 21 on older IDs. That's usually user error, not a dead barcode. Anyway, curious to compare notes as you go.
0
0
Login to reply
The AAMVA standard for driver's license barcodes defines exactly what data goes in which field and in what format. Most buyers never look at what is actually encoded. Here is what is in a standard US DL barcode and why consistency matters.
The AAMVA format structure
A US driver's license PDF417 barcode contains a header section followed by multiple sub-files. The header identifies the AAMVA version and jurisdiction. Sub-file DL contains the primary driver data. Sub-file ZX contains jurisdiction-specific optional data, where X is a state code.
The primary fields in the DL sub-file include: DAA (full name, last first middle), DBB (date of birth), DBA (expiration date), DBD (issue date), DAG (street address), DAI (city), DAJ (state), DAK (postal code), DAQ (license number), DAR (license class), DBC (sex code), DAU (height), DAY (eye color), DCF (document discriminator), DCG (country code).
What gets checked by venue scanners
Most venue ID apps display a subset of these fields — usually name, DOB, expiration date, and a green/red status indicator based on age threshold. The app does not check all fields; it reads DAA for the name, DBB for date of birth, and DBA for expiration, then applies the age rule. Other fields are decoded and displayed but rarely scrutinized in real-time use.
Why data consistency matters
The fields that get scrutinized most are those visible on the card face: name, DOB, and expiration. If the barcode data for these fields does not match the printed card face, the inconsistency is immediately visible in any app that displays both the scan result and shows the cardholder inspecting the card. Reputable vendors encode all fields consistently with the printed data. Asking vendors whether they test barcode-to-face consistency is a reasonable quality question before ordering.
The DOB and expiration fields use MMDDYYYY format in the AAMVA standard. The license number field format varies by state. Both need to be correct for the card to pass a systematic check.