More Than One Kind of Square
Ask most people what the black block on the back of a license is and they will say a barcode, which is true but unhelpfully vague. There are dozens of two dimensional symbologies in circulation, they look broadly similar at arm's length, and they behave very differently once a reader gets hold of them.
Identity documents around the world use at least four of them, sometimes two on the same card. This guide sorts out which codes appear on which cards, why the North American license settled on one in particular, and what a code can and cannot tell a reader about the document carrying it. Looking beyond the familiar block on the back of a license turns out to explain a lot about how modern verification works.
Why Licenses Settled on PDF417
A driver license carries a stacked symbology called PDF417, and the choice was practical rather than fashionable. It is rectangular, which suits the strip of space available on the back of a card, and it scales in one direction, so a longer data set makes the block wider rather than forcing a bigger square.
It also predates the alternatives in mainstream use and was already standardized when jurisdictions needed machine readable licenses. Once one continent's worth of readers existed, switching became almost impossible. The contents of that block are itemized in what is encoded in a license barcode.
QR Codes: Everywhere, Rarely Official
QR codes are the ones everyone recognizes, with the three heavy squares in the corners that let a reader work out orientation instantly. That corner pattern is the reason a phone can read one held sideways or upside down, and it is why the format won the consumer world.
They appear on identity paperwork constantly, but usually on the periphery rather than the document itself: on temporary paper permits, on appointment slips, on the carrier envelope, on verification pages. When one does appear on an official card it is normally a pointer to an online record rather than a container for the record. That distinction matters, because a pointer only works while the service behind it is running.
Aztec and Data Matrix
Two other formats turn up often enough to recognize. Aztec has a bullseye at the center instead of corner squares, needs no quiet zone around its edge, and is common on transport tickets and some European residence documents. Data Matrix is the small dense square with a solid L shaped border, favored where space is tight, which is why it ends up on pharmaceutical packaging and equipment labels.
Both are more compact than QR for short payloads. Neither is widely used for the primary data block on a driver license, but both show up on documents that sit next to one in a wallet.
Signed Codes and Visible Digital Seals
The most interesting development is not a new shape but new contents. A visible digital seal is a two dimensional code that carries a cryptographic signature over the data it holds, so a reader can confirm the payload was issued by a particular authority and has not been altered since.
These appear on newer travel and health documents, and the specifications come from the same standards work that governs passports at the International Civil Aviation Organization. The important property is offline verification: the reader needs the issuer's public key, not a live connection to the issuer.
What an Unsigned Code Proves
Very little on its own, and this is the point most often missed. The block on the back of a standard license is unsigned data. Anyone who can encode can produce a well formed block that any scanner will parse cheerfully, because parsing is not authentication.
What the code does provide is consistency checking. A reader can compare the encoded fields against the text printed on the front, and a mismatch between the two is a far stronger signal than either half alone. That comparison, plus the redundancy explained in PDF417 error correction on licenses, is most of what a door scanner actually contributes.
Where This Is Heading
The signed code idea points at where identity documents are going, which is toward payloads that verify themselves rather than pointing at a database. Chips already do this, and the phone based credentials described in how mobile driver licenses work take it further by letting a holder release single fields rather than the whole record.
Printed codes will not disappear, because a card has to work when the network and the battery do not. The likely outcome is layered: an unsigned block for legacy readers, a signed one for readers that can check it, and a digital credential for everything else. The comparative strengths of each carrier are set out in barcode versus magnetic stripe versus chip on IDs, with more anatomy in the ID security features hub.
Frequently Asked Questions
Is the code on the back of a license a QR code?
It is not. North American licenses use PDF417, a stacked rectangular symbology. QR codes are square with three corner alignment blocks, and they appear on identity paperwork mostly as links rather than as the main data carrier.
Why do documents use different 2D barcodes?
Shape, density, and history. PDF417 fits a wide strip, Data Matrix packs a short payload into a tiny square, Aztec needs no margin around it, and each was adopted by whichever industry needed those properties first.
What is a visible digital seal?
A two dimensional code whose contents carry a cryptographic signature from the issuing authority. A reader holding the issuer's public key can confirm the data is authentic and unmodified without contacting any server.
Can a scanner tell a document is genuine from the barcode alone?
Not from an unsigned one. Parsing a well formed code proves only that the encoding is correct. The useful check is comparing the encoded fields against the printed front of the card and flagging any disagreement.
Do QR codes on ID paperwork ever contain personal data?
Occasionally, on temporary permits and receipts, but most hold a URL or a reference number instead. That keeps the printed item small and moves the record behind a service the issuer controls.
Will licenses ever switch away from PDF417?
Not quickly. Millions of deployed readers expect it, and replacing them is expensive. The realistic path is adding a signed code or a phone credential alongside the existing block rather than replacing it.